RE: [cobalt-developers] IP conflicts

["Tony Kenny" <tony@xxxxxxxxx>]

Hi,

Thanks for the help.  During my investigations to perform the 'arp' method I
found that on the RAQ2 (the box whose address was changed) I found that it
had the interface  eth0:0 still set to the old address.  I went all through
the admin system I found that this address is NOT used anywhere.  I have
rebooted the system to see if it clears, but it didn't.

Can I simply   'ifdown eth0:0' to fix the problem.

Regards,

Tony

> -----Original Message-----
> From: Chris Johnson [mailto:cjohnson@xxxxxxxxxxxxx]
> Sent: 03 February 2000 23:04
> To: Tony Kenny
> Cc: cobalt-developers@xxxxxxxxxxxxxxx
> Subject: Re: [cobalt-developers] IP conflicts
>
>
>
>     This is the typical behavior you will see when two
>     machines are configured with the same IP address.
>     The intermittent effects are because the ARP entries
>     for the two systems are pushing each other out of
>     your local cache.
>
>     The result is that you connect to one system, work
>     for a while, then get an ARP update that points to
>     the other system. The TCP connection then tries to
>     continue, but the packets are routed to the other
>     system.  That system is unaware of the TCP connection
>     so it sends a TCP reset, which closes the connection.
>
>     The fix is to change the IP address on one of the
>     boxes.
>
>     You should be able to do this from the LCD front panel
>     of the Raq-2. Push the select button, then set the host
>     address just like when you initially set the system.
>
>     Another choice is that you can use the arp command to
>     lock an ARP entry in place.  This will let you connect
>     to the Raq-2 through the admin interface so that you
>     set the IP address from our normal user interface.
>     See the 'arp -s' on the arp man page.  If this seems
>     at all obscure, it is probably best to just use the
>     LCD  front panel.
>
>     After you set the IP address, the box should reboot.
>     If you use the arp trick, be sure to nuke the entry
>     you set, using the 'arp -d' command.
>
>     cj*
>