From owner-freebsd-questions@FreeBSD.ORG Wed Jun 16 16:44:21 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F211C16A4CE for ; Wed, 16 Jun 2004 16:44:21 +0000 (GMT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9405343D5D for ; Wed, 16 Jun 2004 16:44:21 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] ([68.161.84.3]) by out002.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20040616164412.ZTYB9273.out002.verizon.net@[192.168.1.3]>; Wed, 16 Jun 2004 11:44:12 -0500 Message-ID: <40D078D4.5020904@mac.com> Date: Wed, 16 Jun 2004 12:44:04 -0400 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040608 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Fuchs References: <40CFC386.3000005@davidfuchs.ca> In-Reply-To: <40CFC386.3000005@davidfuchs.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [68.161.84.3] at Wed, 16 Jun 2004 11:44:11 -0500 cc: freebsd-questions@freebsd.org Subject: Re: arplookup WWW.XXX.YYY.ZZZ failed: host is not on local network X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2004 16:44:22 -0000 David Fuchs wrote: > Ok, riddle me this: > > /kernel: arplookup WWW.XXX.YYY.10 failed: host is not on local network > [ ... ] Static routes have been added to > force all communication *between* these two hosts to use the secondary > interfaces: > > WWW.XXX.YYY.25's static route: > route add WWW.XXX.YYY.10 172.16.1.10 > > WWW.XXX.YYY.10's static route: > route add WWW.XXX.YYY.25 172.16.1.25 You've identified the cause of the problem yourself. One solution would be to stop trying to route IPs which are on a directly connected subnet via your secondary interface. If you want the machines to talk to each other using your 172 network, have whatever services connect to or listen on those IPs rather than on your WWW.XXX.YYY network addresses. -- -Chuck