Re: Overwhelming messages from /sys/netinet/if_ether.c
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 a fundamental problem with the way in_arpinput() seems to process packets, and checking the receive interface versus several interefaces that may or may-not have IPV4 addresses. If I remember Robert's remark in particular, it was related to ARP processing on IPV6 only interfaces that might be plugged into the same wire as IPV4 interfaces on the same machine. This physical configuration yields "host is on int1 but received arp on int2" errors to be logged as well. Robert's suggestion, that I started researching, was to not perform ARP processing on interfaces that don't have IPV4 addresses assigned. This soultion should also address the problems for logging 0.0.0.0 addresses. If anybody is seriously interested, I'll bump the priority on generating a diff, and posting it here. - Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 when my ADSL modem de-syncs with its headend. I can force these messages by powercycling my ADSL modem, or by removing and re-inserting my dataplug into the modem. I have found this kinda annoying, but not that irritating. It has helped me to discover the arp adress of my ADSL modem :) (Now what else can I do with that thing .. *ponders*). Is this worth mentioning to my ADSL provider? .. is it really a misconfiguration of some sort? -- Stephan van Beerschoten[EMAIL PROTECTED] PGP fingerprint: 4557 9761 B212 FB4C 778D 3529 C42A 2D27 XoiP: 0208773826 In god we trust.. all others we verify with PGP fingerprints To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 packets). 2.[12] don't, hence things like many bootp/dhcp configurations which used this feature break. The proper fix is to modify bootp/dhcp clients to accomplish the same thing using raw sockets instead. I think dhcpcd (URL:http://www.phystech.com/download/dhcpcd.html) already works this way, but bootpc hasn't been updated yet. --message from David Wragg ([EMAIL PROTECTED]) at http://www.tux.org/hypermail/linux-kernel/1999week05/0601.html __ Trevor Johnson To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Overwhelming messages from /sys/netinet/if_ether.c
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!
Man, these messages were pouring out of syslogd like mad, and my
/var/log/messages* files had to be deleted, because they were growing
so huge. There were literally hundreds of these messages pouring out
via syslogd per second, and they were coming non-stop. There were so
many messages coming out, my hard drive was overwhelmed until dhclient
finally obtain/ed a lease. That said, I suggest we make the following
patch to /sys/netinet/if_ether.c:
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea-arp_sha, ":", inet_ntoa(isaddr));
+ ea-arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
- Donn
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea-arp_sha, ":", inet_ntoa(isaddr));
+ ea-arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
RE: Overwhelming messages from /sys/netinet/if_ether.c
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 been
literally overwhelmed with messages like:
/kernel: arp: xx:xx:xx:xx:xx:xx is using my IP address 0.0.0.0!
Man, these messages were pouring out of syslogd like mad, and my
/var/log/messages* files had to be deleted, because they were growing
so huge. There were literally hundreds of these messages pouring out
via syslogd per second, and they were coming non-stop. There were so
many messages coming out, my hard drive was overwhelmed until dhclient
finally obtain/ed a lease. That said, I suggest we make the following
patch to /sys/netinet/if_ether.c:
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea-arp_sha, ":", inet_ntoa(isaddr));
+ ea-arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
- Donn
--
E-Mail: Alexander N. Kabaev [EMAIL PROTECTED]
Date: 07-Apr-00
Time: 11:49:33
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 not use 0.0.0.0 as the address that wakes up the interface. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 question to ignore clashes over 0.0.0.0 address only. I agree. John -- John Polstra [EMAIL PROTECTED] John D. Polstra Co., Inc.Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa if_ether.diff
Re: Overwhelming messages from /sys/netinet/if_ether.c
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...
On 07-Apr-00 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!
Man, these messages were pouring out of syslogd like mad, and my
/var/log/messages* files had to be deleted, because they were growing
so huge. There were literally hundreds of these messages pouring out
via syslogd per second, and they were coming non-stop. There were so
many messages coming out, my hard drive was overwhelmed until dhclient
finally obtain/ed a lease. That said, I suggest we make the following
patch to /sys/netinet/if_ether.c:
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea-arp_sha, ":", inet_ntoa(isaddr));
+ ea-arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
- Donn
--
E-Mail: Alexander N. Kabaev [EMAIL PROTECTED]
Date: 07-Apr-00
Time: 11:49:33
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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. 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 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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! Then use a tool designed for the job. You'll only get this message on a system that's a DHCP client and currently trying to get a lease. I don't think that you would ever get any utility from the code as it stands, so the change is not going to affect you. (Note that if you were to configure a system to listen on 0.0.0.0 in order to use this message, you would then be arping for 0.0.0.0, which would appear to defeat your purpose.) Can I kindly suggest that you go find a bridge or a dam or some gun-control law to go oppose for a few months? This random sniper activity is pretty irritating. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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!
Man, these messages were pouring out of syslogd like mad, and my
/var/log/messages* files had to be deleted, because they were growing
so huge. There were literally hundreds of these messages pouring out
via syslogd per second, and they were coming non-stop. There were so
many messages coming out, my hard drive was overwhelmed until dhclient
finally obtain/ed a lease. That said, I suggest we make the following
patch to /sys/netinet/if_ether.c:
--- if_ether.c.orig Wed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea-arp_sha, ":", inet_ntoa(isaddr));
+ ea-arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
- Donn
--ABD696746D33D54680111FE2
Content-Type: text/plain; charset=us-ascii;
name="if_ether.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
filename="if_ether.diff"
--- if_ether.c.origWed Mar 29 02:50:39 2000
+++ if_ether.c Fri Apr 7 11:24:54 2000
@@ -554,9 +554,9 @@
return;
}
if (isaddr.s_addr == myaddr.s_addr) {
- log(LOG_ERR,
+ /* log(LOG_ERR,
"arp: %6D is using my IP address %s!\n",
- ea-arp_sha, ":", inet_ntoa(isaddr));
+ ea-arp_sha, ":", inet_ntoa(isaddr)); */
itaddr = myaddr;
goto reply;
}
--ABD696746D33D54680111FE2--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 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. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 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 sam e time. 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 t o 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 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 N. Kabaev [EMAIL PROTECTED] Date: 07-Apr-00 Time: 15:44:39 -- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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
Re: Overwhelming messages from /sys/netinet/if_ether.c
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! Then use a tool designed for the job. You'll only get this message on a system that's a DHCP client and currently trying to get a lease. I don't think that you would ever get any utility from the code as it stands, so the change is not going to affect you. I get plenty of utility from it as it stands. Any time I see one of these in a syslog I go track it down and shoot the cause. (Note that if you were to configure a system to listen on 0.0.0.0 in order to use this message, you would then be arping for 0.0.0.0, which would appear to defeat your purpose.) My use of the message has nothing to do with wanting to use 0.0.0.0, it's another part of the diagnostics used in maintaining networks for people. Knowing that someone is arping 0.0.0.0 lets me know someone has jacked into one of the networks and trying to either use DHCP or has mis-configured thier box, or is trying to hack. I won't object to the change if a sysctl knob is put around it, that defaults to the way things are now, if someone doesn't care to see these messages due to being on borked networks, fine, let them turn it off. Can I kindly suggest that you go find a bridge or a dam or some gun-control law to go oppose for a few months? This random sniper activity is pretty irritating. 8( It is not random sniper activity. I've been on this list since it was created. I respond when I have something to say and am silent when I have nothing to say. Also that comment is un-called for, it's on the edge of policy violation, and I expect to be respected, no matter how much you may dislike me. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 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 not use 0.0.0.0 as the address that wakes up the interface. --Mat To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
"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 type of thing the link local RFC reserved address space is for. No... IP address 0 is reserved for "me" so its use in DHCP makes sense. Tony. -- f.a.n.finch[EMAIL PROTECTED][EMAIL PROTECTED] 393 dirt clods in your fuel rods To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Overwhelming messages from /sys/netinet/if_ether.c
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 its IP address must have the source address field in the IP header set to 0. RFC951 clause 7.1 says the same thing for BOOTP (though BOOTP and DHCP are really the same protocol). 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 traffic trying to go out while DHCP is still configuring the interface. If you look at the original error message, you'll note that it's actually due to seeing another packet which claims the same Ip address. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
