Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 14 May 2008 13:22:30 +0200
From:      Christer Solskogen <solskogen@carebears.mine.nu>
To:        freebsd-questions@freebsd.org
Subject:   Re: arplookup 0.0.0.0 failed: host is not on local network
Message-ID:  <g0ei1m$r0a$1@ger.gmane.org>
In-Reply-To: <6.0.0.22.2.20080512163401.026387f8@mail.computinginnovations.com>
References:  <g07lip$736$1@ger.gmane.org>	<6.0.0.22.2.20080511190114.0264af00@mail.computinginnovations.com>	<g09t4u$ads$1@ger.gmane.org> <g0a0aa$lip$1@ger.gmane.org>	<6.0.0.22.2.20080512153543.02665c88@mail.computinginnovations.com>	<g0aa89$q0p$1@ger.gmane.org> <6.0.0.22.2.20080512163401.026387f8@mail.computinginnovations.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Derek Ragona wrote:

> Yes aliases should have a netmask of 255.255.255.255
> 
>

Still no go.
192.168.0.255 is showing up in "arp -a" and netstat -rn. (and the 
"arplookup 0.0.0.0 failed: host is not on local network" in 
/var/log/messages)

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 0xffffffff broadcast 192.168.0.4
         inet 192.168.0.5 netmask 0xffffffff broadcast 192.168.0.5
         media: Ethernet autoselect (1000baseTX <full-duplex,flag0,flag1>)
         status: active

Anything else that might explain this kind of behavior?

-- 
chs




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g0ei1m$r0a$1>