Date: Mon, 12 May 2008 22:44:46 +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: <g0aa89$q0p$1@ger.gmane.org> In-Reply-To: <6.0.0.22.2.20080512153543.02665c88@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Derek Ragona wrote: > You may want to do traceroutes from the systems that do find the 0.0.0.0 > interface. I would bet you have a default route and/or netmask sending > the traffic. You will get those arp messages if you run two different > interfaces on the same system, on the same subnet (not to be confused > with running multiple IP's on an interface.) Arp tries to tie an IP > address to a machine address, but if the reverse routing isn't correct > you will see these error messages. > A tip from George Davidovich setting the aliases to use netmask to 0xffffffff seems to fix the problem. -- chs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g0aa89$q0p$1>