From owner-freebsd-questions@FreeBSD.ORG Mon May 12 20:45:12 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFF9E1065682 for ; Mon, 12 May 2008 20:45:12 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 7C3728FC1F for ; Mon, 12 May 2008 20:45:07 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JvetM-0005ie-C4 for freebsd-questions@freebsd.org; Mon, 12 May 2008 20:45:04 +0000 Received: from 151.85-200-10.bkkb.no ([85.200.10.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 May 2008 20:45:04 +0000 Received: from solskogen by 151.85-200-10.bkkb.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 12 May 2008 20:45:04 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Christer Solskogen Date: Mon, 12 May 2008 22:44:46 +0200 Lines: 16 Message-ID: References: <6.0.0.22.2.20080511190114.0264af00@mail.computinginnovations.com> <6.0.0.22.2.20080512153543.02665c88@mail.computinginnovations.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 151.85-200-10.bkkb.no User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) In-Reply-To: <6.0.0.22.2.20080512153543.02665c88@mail.computinginnovations.com> Sender: news Subject: Re: arplookup 0.0.0.0 failed: host is not on local network X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2008 20:45:12 -0000 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