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
