From owner-freebsd-questions@FreeBSD.ORG Mon May 12 21:32:55 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 716381065676 for ; Mon, 12 May 2008 21:32:55 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 2410A8FC15 for ; Mon, 12 May 2008 21:32:54 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.14.2/8.14.2) with ESMTP id m4CLWjnI065080; Mon, 12 May 2008 16:32:45 -0500 (CDT) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080512163401.026387f8@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Mon, 12 May 2008 16:34:33 -0500 To: Christer Solskogen , freebsd-questions@freebsd.org From: Derek Ragona In-Reply-To: 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 X-Antivirus: avast! (VPS 080512-0, 05/12/2008), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV 0.93/6806/Wed Apr 16 15:50:16 2008 on betty.computinginnovations.com X-Virus-Status: Clean X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-MailScanner-ID: m4CLWjnI065080 X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: 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 21:32:55 -0000 At 03:44 PM 5/12/2008, Christer Solskogen wrote: >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 Yes aliases should have a netmask of 255.255.255.255 -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.