LS, Distribution: SuSE 7.1 Kernel: k_deflt-2.2.19-11 (is compiled with CONFIG_IP_ALIAS=y) Problem: One machine has IP address x.10 and IP alias x.11 (ifconfig eth0:0 x.11). Other machine has IP address x.2 and can ping x.10 and x.11 (same network segment). Other machines can ping x.10, but not x.11. It looks like x.11 is never broadcasted. The IP aliases on x.2 works immediatly. What am I forgetting? Regards, Cees.
On Mon, Jun 04, 2001 at 05:17:38PM +0200, Cees van de Griend wrote:
Distribution: SuSE 7.1 Kernel: k_deflt-2.2.19-11 (is compiled with CONFIG_IP_ALIAS=y)
Problem: One machine has IP address x.10 and IP alias x.11 (ifconfig eth0:0 x.11). Other machine has IP address x.2 and can ping x.10 and x.11 (same network segment).
Other machines can ping x.10, but not x.11.
It looks like x.11 is never broadcasted.
The IP aliases on x.2 works immediatly.
What do ifconfig and route look like? Check to make sure that the IP aliases have the correct broadcast address and that the routing table lists each IP alias as a host entry (I think you need to do this). Check the default gateway also. Hope that helps, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
On Wed, Jun 06, 2001 at 10:34:25AM +0100, Chris Reeves wrote:
On Mon, Jun 04, 2001 at 05:17:38PM +0200, Cees van de Griend wrote:
Distribution: SuSE 7.1 Kernel: k_deflt-2.2.19-11 (is compiled with CONFIG_IP_ALIAS=y)
Problem: One machine has IP address x.10 and IP alias x.11 (ifconfig eth0:0 x.11). Other machine has IP address x.2 and can ping x.10 and x.11 (same network segment).
Other machines can ping x.10, but not x.11.
It looks like x.11 is never broadcasted.
The IP aliases on x.2 works immediatly.
What do ifconfig and route look like? Check to make sure that the IP aliases have the correct broadcast address and that the routing table lists each IP alias as a host entry (I think you need to do this). Check the default gateway also.
Tnx, but I already found the source of my problem: a router outside my control. This piece of equipment never did refresh it's ARP-cache. (I believe the standards say it has to timeout after 5 minutes.) A 'main' IP-address was forced updated when a packet originated from this number and the router didn't recognize the source. The IP-alias can't be updated this way, so the router always tried to send the information to the (old) MAC-address. After more than 40 hours, I found this out by accident by using traceroute. When I know the source of the problem, the fix was easy: - bring down network - install IP-alias as 'main' IP-number and give a ping to the router i.e. force the router to update the ARP-cache - install main IP as 'main' and give a ping to the router - install IP-alias
Hope that helps, Chris
Regards, Cees.
participants (2)
-
Cees van de Griend
-
Chris Reeves