Date: Fri, 31 Aug 2012 04:29:53 -0700 From: Adrian Chadd <adrian@freebsd.org> To: kaltheat@googlemail.com Cc: net@freebsd.org Subject: Re: lagg failover issue Message-ID: <CAJ-VmoneEMvCpNotru%2Bws9NdcyExnkGfxnx2W=z7e-Myb1RWRQ@mail.gmail.com> In-Reply-To: <20120831104532.GA1758@-> References: <20120830215147.GA2383@-> <20120831104532.GA1758@->
next in thread | previous in thread | raw e-mail | index | archive | help
guys, You can't override set the outbound MAC address of a wireless station. It associates with the MAC address of the card/vap/device. The AP _will_ store that MAC address in its node table. When sending frames from a STA, the only available details are: * source address - STA MAC * destination BSS - the destination BSS MAC address, ie which AP to send to * destination address - the destnation MAC only in WDS (4-address) setups is there a fourth address, which is the "actual original source MAC address". In this instance, the STA is actually tunnelling traffic from other source MACs. I don't know who started that lagg hack, but let me just be really really clear - if you try sending the source frames out a wifi interface with a source MAC that isn't the STA mac, it won't work. By design. If it does work - it's a fluke and it's not portable. What you really want is for the same IP to exist but only both interfaces and have the source interface/MAC seamlessly change. There've been proposals in the past for the STA side code to "proxy STA" a bunch of other MACs behind it - using 3 address frames( ie, not WDS) but keeping state as to which IP traffic is going to which MAC address. No, net80211 in our tree doesn't have that support. I hope that puts this all to rest. Adrian On 31 August 2012 03:45, <kaltheat@googlemail.com> wrote: > On Thu, Aug 30, 2012 at 11:51:47PM +0200, kaltheat@googlemail.com wrote: >> Hi, >> >> I'm using following devices: >> >> bge0 - NetLink BCM57780 Gigabit Ethernet PCIe >> ndis0 - BCM43225 802.11b/g/n >> >> As far as I've tested it, each of them work fine for itself. >> >> I want to aggregate them using lagg in failover mode as explained here[1][2]. >> But when I remove the wire (wireless connection is established), I can't put >> any traffic through lagg0. >> >> What might be the problem? Can you give me some hints on how to debug this >> lagg-issue further? >> >> Regards, >> kaltheat >> >> [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-aggregation.html >> Example 32-3. Failover Mode Between Wired and Wireless Interfaces >> [2] http://www.freebsd.org/cgi/man.cgi?query=lagg#EXAMPLES >> Second example >> >> > > Hi, > > I can provide some additional informations: > > I read somewhere that it might be a problem to change the ethernet address of a > ndis-interface. On the accesspoint I saw that although I changed the ethernet > address of the wireless nic to that one of the wired nic (checked with ifconfig) > connection was tried to be established with the native mac of the wireless nic. > Now I'm using the native mac of the wireless nic on the wired nic to avoid this > problem. > This didn't solve the lagg issue. > > While I was pinging a client reachable through wired and wireless lan I observed > traffic on the three interfaces (bge0, wlan0, lagg0). With cable connected I saw > ping traffic (in & out) on lagg0 and bge0. When removing cable after a small > break I only saw outgoing packages on lagg0. IP and ethernet addresses of outgoing > packages were the same in each case. > > > Regards, > kaltheat > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmoneEMvCpNotru%2Bws9NdcyExnkGfxnx2W=z7e-Myb1RWRQ>