From owner-freebsd-questions@FreeBSD.ORG Tue Mar 1 21:17:31 2005 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 C194D16A4CE for ; Tue, 1 Mar 2005 21:17:31 +0000 (GMT) Received: from pimout2-ext.prodigy.net (pimout2-ext.prodigy.net [207.115.63.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3713743D41 for ; Tue, 1 Mar 2005 21:17:31 +0000 (GMT) (envelope-from mark@antsclimbtree.com) Received: from lilbuddy.antsclimbtree.com (adsl-69-232-30-131.dsl.snfc21.pacbell.net [69.232.30.131]) j21LHOaU394868; Tue, 1 Mar 2005 16:17:29 -0500 Received: from adsl-66-122-112-170.dsl.snfc21.pacbell.net ([66.122.112.170] helo=[192.168.1.116]) by lilbuddy.antsclimbtree.com with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.44 (FreeBSD)) id 1D6Ejr-00007n-Oz; Tue, 01 Mar 2005 13:17:23 -0800 In-Reply-To: <441xazulyr.fsf@be-well.ilk.org> References: <44vf8b41fq.fsf@be-well.ilk.org> <81c57d2fd8cc8ed9cf5059593bf3da4a@antsclimbtree.com> <441xazulyr.fsf@be-well.ilk.org> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Mark Edwards Date: Tue, 1 Mar 2005 13:17:08 -0800 To: Lowell Gilbert X-Mailer: Apple Mail (2.619.2) X-Spam-Score: -4.4 (----) cc: "'questions@freebsd.org'" Subject: Re: arplookup 192.168.1.254 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: Tue, 01 Mar 2005 21:17:31 -0000 On Mar 1, 2005, at 12:53 PM, Lowell Gilbert wrote: >>>> Looking on the net, I found the following suggestion, which does >>>> cure >>>> the errors: >>>> >>>> /sbin/route add -net 192.168.1.254 -netmask 255.255.255.0 >>>> -interface 1 >>>> >>>> My question is, is that the proper way to deal with this? >>> >>> It's not bad. I would use -host instead of -net and -netmask, and it >>> will fail if the DHCP server ever changes its address, but what you >>> are doing is is working and fairly likely to stay that way. >> >> How would you phrase the command? I just tried -host and couldn't get >> it to work. > > e.g., > route add -host 172.10.212.2 -interface bge0 I tried that syntax and I get errors like this: Mar 1 13:12:37 lilbuddy /kernel: arp: 00:0d:72:d7:d9:a1 attempts to modify permanent entry for 192.168.1.254 on ep1 If I use the -net -netmask syntax I don't get the errors. -- Mark Edwards mark@antsclimbtree.com