From owner-freebsd-questions@FreeBSD.ORG Mon Nov 29 22:20:20 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 3A3AA16A4CF for ; Mon, 29 Nov 2004 22:20:20 +0000 (GMT) Received: from lex.sublimemail.com (lex.sublimemail.com [66.45.27.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0B1043D48 for ; Mon, 29 Nov 2004 22:20:19 +0000 (GMT) (envelope-from dkelly@hiwaay.net) Received: from dogbark.net (localhost [127.0.0.1]) by lex.sublimemail.com (Postfix) with SMTP id 5BC1518CF3B; Mon, 29 Nov 2004 16:20:19 -0600 (CST) Received: from 207.111.173.106 (SquirrelMail authenticated user n4hhe) by webmail.dogbark.com with HTTP; Mon, 29 Nov 2004 16:20:19 -0600 (CST) Message-ID: <1713.207.111.173.106.1101766819.squirrel@webmail.dogbark.com> Date: Mon, 29 Nov 2004 16:20:19 -0600 (CST) From: "David Kelly" To: In-Reply-To: <41AB94C9.7040901@yahoo.fr> References: <41AB94C9.7040901@yahoo.fr> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-questions@freebsd.org 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: Mon, 29 Nov 2004 22:20:20 -0000 [...] > None of the above work (ie: they both make the default route go through > an0 - wifi - and i suspect this is because the wifi dhcp is slower to > answer than the ethernet one), so i ended up commenting out the wifi > line (an0) and activating it by hand when needed... However this is > quite troublesome as it means killing the dhclient running, before > running another dhclient an0... If anybody has a better suggestion for > me I would be quite grateful! A good place to start surfing in looking for solutions to this sort of thing is /etc/defaults/rc.conf. As you have discovered, the order of items listed in /etc/rc.conf doesn't matter. That is because one literally is setting values of variables there. Its some time later before those variables are actually used. If you wish to continue this direction you might kill your dhclient process which is running on fxp0 then manually start it again "dhclient fxp0". If that results in the route you wish then you might be able to control the start order with this in /etc/rc.conf: network_interfaces="lo0 an0 fxp0" Another thought from /etc/defaults/rc.conf is to set defaultrotuer="1.2.3.4" (change to the real address your ISP provides. But reading "man dhclient.conf" I think dhclient will clobber any static route on lease renewal no matter if you set it by hand or with crafted interface start order. So go read that man page and edit your /etc/dhclient.conf The solution may lie in "man dhcp-options"