From owner-freebsd-stable Sun Dec 16 18:35:32 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by hub.freebsd.org (Postfix) with ESMTP id 32C7037B419 for ; Sun, 16 Dec 2001 18:35:30 -0800 (PST) Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (8.10.1/8.10.1) with ESMTP id fBH2Y7d04093; Sun, 16 Dec 2001 18:34:07 -0800 (PST) Message-Id: <200112170234.fBH2Y7d04093@ptavv.es.net> To: Steve Feldman Cc: Jonathan Lemon , smkelly@zombie.org, stable@FreeBSD.ORG Subject: Re: Networking Question In-reply-to: Your message of "Fri, 14 Dec 2001 16:40:33 PST." <20011214164033.A13456@twincreeks.net> Date: Sun, 16 Dec 2001 18:34:07 -0800 From: "Kevin Oberman" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Fri, 14 Dec 2001 16:40:33 -0800 > From: Steve Feldman > Sender: owner-freebsd-stable@FreeBSD.ORG > > Ahh, this sounds like the beginning of something I'd like > to see: the ability to shut off DHCP when an interface goes > down and reenable it when it comes back up. > > That would let me move easily between a wired (on the built-in fxp) > and wireless (pc-card) interface without having to manually kill > and restart dhclient like I do now. > > That's probably the only Windows feature I miss on FreeBSD. :) If you use pccard_ether, it does kill dhclient. And, it starts it again when another card is inserted. It's far from ideal, but it works for me. I just need to pull the wireless card before suspending my laptop (or the other way around). R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message