Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-17 Thread C. Stephen Gunn
On Fri, Apr 07, 2000 at 11:39:09AM -0400, Donn Miller wrote: > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! I was discussing this issue with Robert Watson the other day on IRC. The issue is more complicated than just removing the notification in sys/netinet/if_ether.c. It's

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-10 Thread Stephan van Beerschoten
On Fri, 07 Apr 2000, Donn Miller wrote: > Since I started using a cable modem and dhclient, my system has been > literally overwhelmed with messages like: > > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! I have these same warnings all over my syslog in minute-wise intervals w

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-08 Thread Andrew Gordon
On Fri, 7 Apr 2000, Mike Smith wrote: > > > > However, this isn't really an excuse for issuing ARP with a source address > > of zero: the initial DHCP exchange is done with broadcasts (so doesn't > > need ARP), and after that the address is known. The problem presumably > > arises due to other t

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Trevor Johnson
> I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. The Linux folks stopped doing it: 2.0 supported the net interface 0.0.0.0 IP address convention (meaning the kernel should accept all IP pack

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Mike Smith
> > On Fri, 7 Apr 2000, David Holloway wrote: > > > I say with 99% certainty that assigning 0.0.0.0 to > > the interface is a requirement of dhcp. > > > > You can't stop using it and expect dhcp to work. > > Yes, RFC2131 clause 4.1 says: > >DHCP messages broadcast by a client prior to tha

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Andrew Gordon
On Fri, 7 Apr 2000, David Holloway wrote: > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. Yes, RFC2131 clause 4.1 says: DHCP messages broadcast by a client prior to that client obtaining

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Tony Finch
"Rodney W. Grimes" <[EMAIL PROTECTED]> wrote: >David Holloway <[EMAIL PROTECTED]> wrote: >>>Mathew Kanner wrote: >>>I haven't tried this but how about changing the >>>/sbin/dhclient-script to not use 0.0.0.0 as the address that wakes >>>up the interface. >> >> No... > >Yes... that is just the typ

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
> No... Yes... that is just the type of thing the link local RFC reserved address space is for. > In message <[EMAIL PROTECTED]>, Mathew Kanner writes: > >On Apr 07, Donn Miller wrote: > >> Since I started using a cable modem and dhclient, my system has been > >> literally overwhelmed with mess

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
> > > 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 su

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
> 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

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Alexander N. Kabaev
I have the same impression fom reading dhclient sources. On 07-Apr-00 David Holloway wrote: > I say with 99% certainty that assigning 0.0.0.0 to > the interface is a requirement of dhcp. > > You can't stop using it and expect dhcp to work. > -- E-Mail: Alexander

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread David Holloway
I say with 99% certainty that assigning 0.0.0.0 to the interface is a requirement of dhcp. You can't stop using it and expect dhcp to work. In message <[EMAIL PROTECTED]>, "Alexander N. Kabaev" writes: >FreeBSD dhclient-script assigns 0.0.0.0 address to the interface in PREINIT >in order to brin

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread David Holloway
No... In message <[EMAIL PROTECTED]>, Mathew Kanner writes: >On Apr 07, Donn Miller wrote: >> Since I started using a cable modem and dhclient, my system has been >> literally overwhelmed with messages like: >> >> /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! >> > > I ha

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread David Holloway
I have seen that situation before as well and there may be more slight tolerance-style improvements that could be made but I can't think of any at the moment. In message <[EMAIL PROTECTED]>, Donn Miller writes: >This is a multi-part message in MIME format. >--ABD696746D33D54680111FE2

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Mike Smith
> > 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 w

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Alexander N. Kabaev
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 sha

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Rodney W. Grimes
> 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

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Alexander N. Kabaev
Trivial patch attached :) On 07-Apr-00 John Polstra wrote: > In article <[EMAIL PROTECTED]>, > Alexander N. Kabaev <[EMAIL PROTECTED]> 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 questio

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread John Polstra
In article <[EMAIL PROTECTED]>, Alexander N. Kabaev <[EMAIL PROTECTED]> 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. I agree. John --

Re: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Mathew Kanner
On Apr 07, Donn Miller wrote: > Since I started using a cable modem and dhclient, my system has been > literally overwhelmed with messages like: > > /kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0! > I haven't tried this but how about changing the /sbin/dhclient-script to

RE: Overwhelming messages from /sys/netinet/if_ether.c

2000-04-07 Thread Alexander N. Kabaev
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. On 07-Apr-00 Donn Miller wrote: > Since I started using a cable modem and dhclient, my system has bee