From owner-freebsd-current@FreeBSD.ORG Thu Aug 4 00:23:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 816F416A41F for ; Thu, 4 Aug 2005 00:23:16 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from vomit.ugcs.caltech.edu (vomit.ugcs.caltech.edu [131.215.176.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3671E43D48 for ; Thu, 4 Aug 2005 00:23:16 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by vomit.ugcs.caltech.edu (Postfix, from userid 3640) id 8D168E816; Wed, 3 Aug 2005 17:23:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by vomit.ugcs.caltech.edu (Postfix) with ESMTP id 71601E815; Wed, 3 Aug 2005 17:23:15 -0700 (PDT) Date: Wed, 3 Aug 2005 17:23:15 -0700 (PDT) From: Jon Dama To: Brooks Davis In-Reply-To: <20050726182754.GA27038@odin.ac.hmc.edu> Message-ID: References: <42E583F9.3070703@rogers.com> <200507261403.01515.imachine@toya.net.pl> <200507261104.35752.peter@wemm.org> <20050726182754.GA27038@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org, Mateusz J??drasik Subject: Re: dhclient sucks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2005 00:23:16 -0000 Isn't the problem here actually the handling of default routes generally that results from having the routing table support arp? -Jon On Tue, 26 Jul 2005, Brooks Davis wrote: > On Tue, Jul 26, 2005 at 11:04:35AM -0700, Peter Wemm wrote: > > On Tuesday 26 July 2005 05:03 am, Mateusz J??drasik wrote: > > > Dnia wtorek 26 lipca 2005 02:29, Mike Jakubik napisa??: > > > > xl0: link state changed to UP > > > > DHCPREQUEST on xl0 to 255.255.255.255 port 67 > > > > DHCPREQUEST on xl0 to 255.255.255.255 port 67 > > > > DHCPACK from x.x.x.1 > > > > bound to x.x.x.195 -- renewal in 43200 seconds. > > > > xl0: flags=8843 mtu 1500 > > > > options=9 > > > > inet x.x.x.195 netmask 0xffffff80 broadcast x.x.x.255 > > > > ether 00:01:03:d4:4c:07 > > > > media: Ethernet autoselect (100baseTX ) > > > > status: active > > > > Creating and/or trimming log files:. > > > > Starting syslogd. > > > > Additional routing options: IP gateway=YES. > > > > Starting devd. > > > > dhclient xl0: already running? > > > > Mounting NFS file systems:. > > > > > > > > --- > > > > > > > > Why is dhclient being run again? Can someone tell me why this > > > > openbsd version was brought in anyways? The old one worked just > > > > fine, this seems like yet another reinvention of a wheel, and a > > > > broken one at that. > > > > > > I have a very similar issue on 6.0-BETA, it starts once, then again > > > during the boot process similarly at the same place You mentioned, > > > with ifconfig_fxp0="DHCP" in rc.conf. > > > > > > Eh. ;-) > > > > > > Btw, is it possible to have two interfaces? I have w wi0 and fxp0 > > > card, the wi0 being dynamically switchable on or off with a switch on > > > the laptop's side. I would ideally like both of them to do DHCP, > > > however, first trying the currently working/available interface - > > > that is, fxp0 - then, if the fxp0 link goes down, and nothing is up, > > > cancelling the DHCP request, later, when the wi0 gets switched ON, > > > FreeBSD automatically picking up DHCP from the associated wireless > > > network - is that possible, without manually needing to start DHCP > > > every time? > > > > Oh, how I wish dhclient could handle two interfaces! The old one > > allowed two interfaces, but was rather stupid about it. There was no > > way to specify which interface had priority, so the last one usually > > won with its default routes. > > > > My gateway box at home has two ethernet interfaces that need dhcp. It > > seems I'm going to have to hack dhclient-script or something to get it > > to do something sensible. It shouldn't be that painful. > > > > Linux (gentoo in this case) has dhcpcd, which take switches to allow you > > to tell it to not mess with resolv.conf or the default route. No > > hacking or pain required. Unlike ours dhclient. > > I think the largest issue here is the default route support, probably > followed by doing something more sane about situations where people want > to use two different interfaces to access the same network (I don't > think you can win here, but we can probably do better). I just > found one typo that may be the cause of some default route issues. > > -- Brooks > > -- > Any statement of the form "X is the one, true Y" is FALSE. > PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 >