On Wed, Sep 14, 2005 at 05:59:52PM -0400, Bill wrote: > On Wed, 14 Sep 2005 23:15:07 +0200 > Claudio Jeker <[EMAIL PROTECTED]> wrote: > > > On Wed, Sep 14, 2005 at 02:59:14PM -0400, Bill wrote: > > > Heya, > > > > > > On a 3.7 / i386 box (running dhcp/named) with multiple nic cards: > > > > > > arplookup: unable to enter address for 0.0.0.0 > > > > > > I have been seeing these messages in my logs for a few days. > > > > > > Usually followed by a "last message repeated x times" > > > > > > The arp(4) man page says > > > "An IP received on the interface does not match the network/netmask of > > > the interface. This indicates a netmask problem." > > > > > > Does this mean my default route is somehow bad? I checked the netmask > > > and it all seems good there - and more importantly it works fine. > > > > > > Now, I suspect it is a wifi node that someone misconfigured to the > > > wrong network, and they have just not gotten out there to fix it yet. > > > But what could I to track this down if I did have a prime suspect. I > > > looked through arp -a, but it would not be in there anyway right. How > > > can I tell which nic this is coming in on? > > > > > > > That issue is fixed in 3.8. > > The problem was a "ifconfig $if 0.0.0.0 up" in dhclient-script that was > > causing a gratious arp for the IP 0.0.0.0. > > > > -- > > :wq Claudio > > > > Thanks for the info... but this machine is not a dhcp client at all... > its running a dhcp server. > > So far it seems harmless though... >
The problem is an other box on your LAN that is doing a gratious arp with 0.0.0.0. OpenBSD does not like this and logs it. -- :wq Claudio
