arplookup 0.0.0.0 failed: host is not on local network

Christer Solskogen solskogen at carebears.mine.nu
Mon May 12 17:55:30 UTC 2008


Christer Solskogen wrote:
> Derek Ragona wrote:
> 
>> Sounds like you have 0.0.0.0 configured on an ethernet  interface.  I 
>> would check all your systems, and be sure it isn't used.
>>
> 
> I checked, and there is no interface with that ip address. But thanks 
> for the advice.
> 
> OpenBSD box - where 0.0.0.0 is resolving to.
> rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         lladdr 00:01:c0:03:7c:09
>         media: Ethernet autoselect (100baseTX full-duplex)
>         status: active
>         inet6 fe80::201:c0ff:fe03:7c09%rl0 prefixlen 64 scopeid 0x1
>         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
> 
> nfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
>         options=18b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWCSUM,TSO4>
>         ether 00:18:f3:29:d8:15
>         inet 192.168.0.3 netmask 0xffffff00 broadcast 192.168.0.255
>         inet 192.168.0.4 netmask 0xffffff00 broadcast 192.168.0.255
>         inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255
>         media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
>         status: active
> 
> 
> (I also have a Mac OX 10.5 which also resolves 0.0.0.0 to 192.168.0.1. 
> But a windows machine do not resolve 0.0.0.0)
> 


Gah, my bad.
the nfe0 interface are not on OpenBSD, but on my FreeBSD box (where this 
arp-messages shows up)

-- 
chs



More information about the freebsd-questions mailing list