[591] in testers
Re: netconfig (RT 6.4R)
daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Wed Jan 3 15:34:57 1990
From: probe@ATHENA.MIT.EDU
Date: Wed, 3 Jan 90 15:34:37 -0500
To: jfc@ATHENA.MIT.EDU
Cc: testers@ATHENA.MIT.EDU
In-Reply-To: John Carr's message of Wed, 03 Jan 90 04:08:51 EST,
Reply-To: Richard Basch <probe@ATHENA.MIT.EDU>
Date: Wed, 03 Jan 90 04:08:51 EST
From: John Carr <jfc@ATHENA.MIT.EDU>
My workstation and another rebooted at relative times such that they
both tried to run "netconfig" at the same time. Each machine claimed
that the other was on its address:
duplicate IP address!! sent from ethernet address: 00:dd:00:85:2b:00
After a few seconds of this (6 messages), each chose the correct
address. The other machine is "soup", running a netconfig dated Dec
13. I am running the version now on the packs.
Hypothesis: one machine used the NIP response destined for the other.
That bug has already been noted. The cause is that the network is up
but the address has not yet been configured while another NIP request
was going out. Your address at the time was 0.0.0.0, as was another
machine that was just coming up. Thus the other machiene's request is
on the same IP address.
The fix is to change the kernel so that it ignores messages from 0.0.0.0.
-Richard
