From owner-freebsd-mobile@FreeBSD.ORG Sat Mar 28 17:05:53 2009 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B66E1065673 for ; Sat, 28 Mar 2009 17:05:53 +0000 (UTC) (envelope-from clarkjp@charter.net) Received: from mail.cluebytwelve.org (clueby12.org [198.186.190.239]) by mx1.freebsd.org (Postfix) with ESMTP id 4CDB28FC12 for ; Sat, 28 Mar 2009 17:05:53 +0000 (UTC) (envelope-from clarkjp@charter.net) Received: from localdomain.local (24-158-157-74.dhcp.jcsn.tn.charter.com [24.158.157.74]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cluebytwelve.org (Postfix) with ESMTPSA id AE3E71B5D0 for ; Sat, 28 Mar 2009 12:05:52 -0500 (CDT) Received: by localdomain.local (Postfix, from userid 1001) id C344E4AC44; Sat, 28 Mar 2009 12:05:51 -0500 (CDT) Date: Sat, 28 Mar 2009 12:05:51 -0500 From: "J. Porter Clark" To: freebsd-mobile@freebsd.org Message-ID: <20090328170551.GA58425@auricle.charter.net> References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <20090328164216.GA68623@citylink.fud.org.nz> <49CE5462.1010105@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <49CE5462.1010105@freebsd.org> Organization: http://www.angelfire.com/ego/porterclark/ User-Agent: Mutt/1.5.19 (2009-01-05) Subject: Re: Switching from wired to wireless getting "network down" X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 28 Mar 2009 17:05:54 -0000 On Sat, Mar 28, 2009 at 09:46:26AM -0700, Sam Leffler wrote: > > Andrew Thompson wrote: > > On Sat, Mar 28, 2009 at 09:35:46AM -0700, Sam Leffler wrote: > > > >> J. Porter Clark wrote: > >>>> > >>> I've been playing around with this sort of setup, too, where I > >>> want a command line to change from wired to wireless (at the > >>> same IP address, even) and back again. I haven't found the > >>> magic solution, particularly one that doesn't have a lot of > >>> hardcoded network config in it. I'm also somewhat ticked that > >>> "route flush" doesn't really flush all routes like the man page > >>> says. 8-) Eventually, I usually arrive at a point where I can't > >>> find my way back and have to reboot to get some work done. > >>> > >>> Some things I've been using are "route delete " > >>> and "route add -ifp default". Might be a good idea > >>> to "arp -a -d", too. > >>> > >> If this is 7.x or later, have you tried using lagg(4) to do automatic > >> failover? The man page says wpa doesn't work but after talking to Andrew > >> we think that's no longer true. I haven't had a chance to try it myself. > > > > This is becuase lagg(4) will set the interface down/up when grabbing it > > and wpa_supplicant does not get restarted. This may work now but looking > > through /etc/devd.conf I dont see a rule to handle it (only ATTACH and > > LINK_UP events). A new devd event may need to be added to handle this > > situation. Patches welcome. > > I believe LINK_UP should be sufficient but we need to check. FreeBSD-STABLE (says 7.2-PRERELEASE at the moment). I haven't tried lagg(4), because I didn't know it existed, but I will look into it--it sounds like just what I need, if it works! In fact, I am only doing WEP on this network. The laptop that I'm using is an employer-issued Dell Latitude E6500, which has the dreaded Intel 5100AGN among its faults. To get wireless working, I'm ignoring that and using an old Agere Orinoco Gold card (wi), which AFAIK doesn't know how to do WPA--I could be wrong. The reason I'm having to switch between it and the wired interface is that I can get no better than about 3 Mbps through the wireless card, and I actually have 10 Mbps downlink service here. So I do wired when I need performance and wireless when I need mobility, at least until support for the 5100 arrives. -- J. Porter Clark