From owner-freebsd-questions@FreeBSD.ORG Tue Dec 5 18:31:10 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6625B16A4A0 for ; Tue, 5 Dec 2006 18:31:10 +0000 (UTC) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2927143CBA for ; Tue, 5 Dec 2006 18:30:25 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id kB5IV52R039371; Tue, 5 Dec 2006 10:31:05 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-questions@freebsd.org Date: Tue, 5 Dec 2006 13:29:13 -0500 User-Agent: KMail/1.9.4 References: <539c60b90612051021m27722ccam791a72cf7c5e5487@mail.gmail.com> In-Reply-To: <539c60b90612051021m27722ccam791a72cf7c5e5487@mail.gmail.com> X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*.<=?utf-8?q?of=5F4NrS=0A=09P*M/9CpxDo!D6?=)IY1w<9B1jB; tBQf[RU-R<,I)e"$q7N7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612051329.13470.lists@jnielsen.net> X-Virus-Scanned: ClamAV version 0.88.4, clamav-milter version 0.88.4 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Steve Franks Subject: Re: wifi & dhcp X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 18:31:10 -0000 On Tuesday 05 December 2006 13:21, Steve Franks wrote: > Ok, we're losin our minds here. Me and a friend just bought up no less > than 4 boxes (server, 2 laptops, and a net-device) in about 2 weeks on > stable 6.1. My first foray into bsd since '95, and I'm way-pleased. > One little problem: every one of them loses it's connection (aka ip) > when the wifi goes out and comes back, forcing us to 'dhclient xx0' > incessantly. Note we're talking a belkin ath, an ativa ath, a wavelan > wi and a linksys wi, not all the same card or even driver. > > Someone on current said, 'it's probably a problem with the driver's > link-state handling' - whatever. Oh, yeah, we've got one set on a > dlink ap, and the other on a linksys. Both are running wep for legacy > reasons, which I have a sinking feeling may be a contributing factor. I see the same behavior (using an older wi(4) card). I haven't done much experimenting with it though since my house isn't that big and I don't lose my link that often. A couple things I would suggest trying, though: Add a "killall dhclient" somewhere in your boot process. Not ideal for some circumstances, but if you only plan to be on one logical wireless network for a given session then it shouldn't hurt anything. Try using the net/isc-dhcp3-client port instead of the base system's dhclient. E.g.: cd /usr/ports/net/isc-dhcp3-client && make install clean echo 'dhclient_program="/usr/local/sbin/dhclient"' >> /etc/rc.conf If you have/use a dhclient.conf file you'll also need to either move it to /usr/local/etc or add 'dhclient_flags="-c /etc/dhclient.conf"' to /etc/rc.conf. Good luck! JN