From owner-freebsd-questions@FreeBSD.ORG Tue Mar 1 10:31:55 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 98EEA16A4CE for ; Tue, 1 Mar 2005 10:31:55 +0000 (GMT) Received: from pimout4-ext.prodigy.net (pimout4-ext.prodigy.net [207.115.63.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id E138443D5C for ; Tue, 1 Mar 2005 10:31:54 +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]) j21AVnHb171958 for ; Tue, 1 Mar 2005 05:31:53 -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 1D64fK-0000aP-JD for questions@FreeBSD.ORG; Tue, 01 Mar 2005 02:31:49 -0800 Mime-Version: 1.0 (Apple Message framework v619.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; format=flowed To: "'questions@freebsd.org'" From: Mark Edwards Date: Tue, 1 Mar 2005 02:31:46 -0800 X-Mailer: Apple Mail (2.619.2) X-Spam-Score: -5.8 (-----) Subject: 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 10:31:55 -0000 I've just put my server on a new connection that requires DHCP, even for a fixed IP. Anyway, the DHCP server gives a fixed public internet IP to my server, but it communicates on 192.168.1.254, which angers FreeBSD (4.11). I get a lot of the following: arplookup 192.168.1.254 failed: host is not on local network Which makes sense, because as far as FreeBSD is concerned, interface ep1 is on the internet not on a LAN. 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? I have to issue this statement whenever the dhclient is restarted. I've currently placed it in my firewall script, but is there a proper or more elegant way to achieve this? Thanks! -- Mark Edwards mark@antsclimbtree.com