On Wed, Oct 17, 2001 at 10:55:25PM -0800, Beech Rintoul wrote: > On Wed, 17 Oct 2001, Jose M. Alcaide wrote: > > After rebuilding the kernel two days ago (Oct 15), I am getting lots of > > messages like these: > > > > arp: 00:30:65:de:99:32 is using my IP address 0.0.0.0! > > arp: 00:0a:27:b0:a7:06 is using my IP address 0.0.0.0! > > arp: 00:30:65:d1:2f:cc is using my IP address 0.0.0.0! > > arp: 00:30:65:e9:57:5e is using my IP address 0.0.0.0! > > > > and so on. > > > > Neither ifconfig(8) nor arp(8) show anything unusual. > > > > I'm having the exact same problem. I connect to a large subnet /12 and I'm > getting flooded with these. This just started about a week ago. I'm also not > using DHCP. Any way of blocking this short of turning off all kernel messages?
I found something interesting: these messages are caused by ARP requests carrying 0.0.0.0 as the sender IP address. All of them come from Apple Macintosh (over 40 different machines). I am not sure whether 0.0.0.0 is a legal sender IP address in an ARP request; 0.0.0.0 means "this" host, so that I think that it is a valid address when the machine doing the ARP request does not know its IP address yet (though this sounds stupid). Anyway, the fact is that -CURRENT can flood the console and /var/log/messages if there are many Macintosh sending these ARP requests in a LAN (as it is our case). I think that there is no reason to printf these messages, since 0.0.0.0 is a valid IP address meaning "this" host. -- ****** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message