> FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT
> in order to bring interface up. Windows seems to do that as well or
> there is no sane explanation for the relatively big number of these nasty
> messages I am getting every time MediaOne network goes down and several PCs
> sharing the same cable network segment attempt to renew their lease at the same
> time.
Ahhh... then perhaps a better fix is to change the gratitious arp routine
to _not_ emit the bogus arp who-has arp-i-am when an interface is ifconfig'ed
to 0.0.0.0 rather than cause the error logging code to be disabled?
>
>
> On 07-Apr-00 Rodney W. Grimes wrote:
> >> The message in question can be extremely useful in case there is IP address
> >> clash on the local network. I suggest we just change the code in question to
> >> ignore clashes over 0.0.0.0 address only.
> >
> > No, don't do that, anyone arping 0.0.0.0 on any network around here
> > I sure as heck want to know about it asap! Someone someplace on
> > that stupid telco's DSL bridged network is mis-configured and
> > sending out arp messages for the 0 addresses. Easy enough to
> > cause though:
> >
> > ifconfig xx0 0.0.0.0 up
> >
> > should do the trick...
> >
> ----------------------------------
> E-Mail: Alexander N. Kabaev <[EMAIL PROTECTED]>
> Date: 07-Apr-00
> Time: 14:35:14
> ----------------------------------
>
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
