From owner-freebsd-questions@FreeBSD.ORG Tue Nov 30 09:53:16 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 C01BE16A4CE for ; Tue, 30 Nov 2004 09:53:16 +0000 (GMT) Received: from infres.enst.fr (infres-192.enst.fr [137.194.192.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C1EE43D31 for ; Tue, 30 Nov 2004 09:53:16 +0000 (GMT) (envelope-from yannick_bre@yahoo.fr) Received: from [137.194.164.241] (dhcp164-241.enst.fr [137.194.164.241]) by infres.enst.fr (Postfix) with ESMTP id ABD852F7B; Tue, 30 Nov 2004 10:53:14 +0100 (MET) Message-ID: <41AC42F1.5010202@yahoo.fr> Date: Tue, 30 Nov 2004 10:52:49 +0100 From: Yannack User-Agent: Mozilla Thunderbird 0.9 (X11/20041124) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Kelly References: <41AB94C9.7040901@yahoo.fr> <1713.207.111.173.106.1101766819.squirrel@webmail.dogbark.com> <41ABAAC1.6030901@yahoo.fr> <20041129180602.5b4622a0.wmoran@potentialtech.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: FreeBSD_Questions FreeBSD_Questions cc: Bill Moran Subject: Re: Multiple NICs 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, 30 Nov 2004 09:53:16 -0000 > Now for a 3rd bird to kill in one reply I need to remind Yannack > that apparently the *last* dhclient to run sets the default route. > Next time dhclient renews the lease on an0 your default route will > go the wrong way again until the ISP-issued lease renews on fxp0. > > I think it would be easiest to statically set the wireless IP > address. After all it is *your* network, right? So you ought to be > able to lay down your own law. With a static address you'll always > know how to reach your FreeBSD box from the wireless side. Yes and no: given I use this laptop at two locations, the wireless IP changes. At home, I can set it as it is indeed my own network, but not at work.... :( > Otherwise > you ought to dig into dhclient's docs in order to prevent an0 from > setting a default route. Just because it seems to be working now > doesn't mean its time to stop, else you will end up with a typical > PC-grade network. Actually you are right, I will have to do that as this morning at work, the setup didn't work :( I have wifi and ethernet both at work and at home, and though my tests seemed to work at home with my personal DHCP they stopped at work for some reason. I will therefore try and find some dhclient option preventing the setting of a default route for an0. However when my ethernet is down (which does happen), I have to have a default route available through an0... Gee, this is tough... :( Why is it so easy with Windows ? > Am guessing based on the contents of man pages for dhcp-options and > dhclient.conf but you need to put something like the following on > the tail of /etc/dhclient.conf. Am thinking here that these are the > only things you want from the wireless router. That if you don't ask > for a router then you won't be given one. Undefined interfaces in > /etc/dhclient.conf will continue to use the default values. > > interface "an0" { > require ip-address, subnet-mask, broadcast-address; > } > I will do some testing...