From owner-freebsd-mobile@FreeBSD.ORG Sat Mar 28 22:55:17 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 136DA1065673; Sat, 28 Mar 2009 22:55:17 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id C945F8FC12; Sat, 28 Mar 2009 22:55:16 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n2SMtE9n071799 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 28 Mar 2009 15:55:14 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <49CEAAD2.7050203@freebsd.org> Date: Sat, 28 Mar 2009 15:55:14 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Daniel Eischen References: <1238217783.00093348.1238205603@10.7.7.3> <20090328160858.GA57695@auricle.charter.net> <49CE51E2.4000807@freebsd.org> <49CE5B95.1010502@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-x.dcc-servers-Metrics: ebb.errno.com; whitelist Cc: "J. Porter Clark" , freebsd-mobile@freebsd.org 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 22:55:17 -0000 Daniel Eischen wrote: > On Sat, 28 Mar 2009, Sam Leffler wrote: > >> Daniel Eischen wrote: >>> On Sat, 28 Mar 2009, 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. >>> >>> Yeah, but as far as I can recall, lagg isn't able to change the >>> MAC address on the cloned wlanX interface. lagg with wireless >>> and wired interfaces used to work before wlan cloning was added. >>> I haven't tested it in a while, though. Has this been fixed? >>> >> You can change the mac address of a wlan ifnet (just verified); the >> problem is that it needs to be propagated to the physical ifnet as >> well for it to matter (the right thing happens if you do it when you >> clone the ifnet but not > > Right, that's what I meant above - the MAC gets set on wlan0, > but not on ath0, for instance. > >> if you force it after, and I'm not sure you can make it work). I'm >> starting to remember now about this. Was there a PR filed? I >> completely forgot about this issue and it's likely to happen again >> w/o one. > > No, there's no PR as far as I can tell. I'll try and set up a > test system to duplicate it again, so I have proper information > for a PR. > > I seem to recall that if wlanX is your primary/first lagg > interface, then it uses the MAC address from the underlying > interface as lagg's MAC address. In this case it works, > but that's not the usual case 'cause you'd rather use a > faster wired interface first if it exists. > > So this works: > > ifconfig lagg0 laggproto failover laggport wlan0 laggport bge0 > > but this doesn't: > > ifconfig lagg0 laggproto failover laggport bge0 laggport wlan0 > > In the latter case, lagg only works when bge0 is up. > I'm fixing various issues in handling the mac address (in head). I can now use lagg w/o wpa so long as you force the mac address manually. If there had been a PR this problem would not have been lost. Sam