On Thu, 28 Aug 2008, Andrew Thompson wrote: > On Thu, Aug 28, 2008 at 04:32:02PM -0400, Daniel Eischen wrote: >> On Thu, 28 Aug 2008, Andrew Thompson wrote: >> >>> On Tue, Aug 26, 2008 at 11:41:20AM -0400, Daniel Eischen wrote: >>>> I'm trying to get a lagg interface with failover to work with bfe0 >>>> and wlan0. The master port is bfe0, with failover to wlan0. The >>>> wlan0 interface is ath0. >>>> >>>> I can get both wlan0 and bfe0 to work independently without being >>>> lagg devices, but only bfe0 works when wlan0 and bfe0 are in a >>>> lagg interface. In other words, when I pull the plug on bfe0, it >>>> does not failover to wlan0. >>>> >>>> $ ifconfig -a >>>> ath0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 2290 >>>> ether 00:11:f5:9d:54:f5 >>> ^^^^^^^^^^^^^^^^^^^^^^^ >>>> media: IEEE 802.11 Wireless Ethernet autoselect mode 11g >>>> status: associated >>>> bfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 >>>> options=8<VLAN_MTU> >>>> ether 00:14:22:ae:bc:98 >>>> media: Ethernet autoselect (100baseTX <full-duplex>) >>>> status: active >>>> lagg: laggdev lagg0 >>>> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 >>>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 >>>> inet6 ::1 prefixlen 128 >>>> inet 127.0.0.1 netmask 0xff000000 >>>> lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 >>>> ether 00:14:22:ae:bc:98 >>> ^^^^^^^^^^^^^^^^^^^^^^^ >>>> inet 10.0.0.7 netmask 0xffffff00 broadcast 10.0.0.255 >>>> media: Ethernet autoselect >>>> status: active >>>> laggproto failover >>>> laggport: wlan0 flags=0<> >>>> laggport: bfe0 flags=5<MASTER,ACTIVE> >>>> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 >>>> ether 00:14:22:ae:bc:98 >>> ^^^^^^^^^^^^^^^^^^^^^^^ >>> >>> I wonder if it becuase the lagg driver sets the mac address of all its >>> interfaces to the same value, this has not been propagated back up to >>> the ath0 interface. >> >> Ahh, I didn't notice this. >> >>> I wonder if this is the right way to do things. >> >> Well, it stops complaints on routers, and perhaps switches, >> when an IP's MAC address changes. >> >> Or perhaps wlan (or any cloned device?) should relay the >> MAC address change down to the lower level device? > > To verify this you could set the mac to the wireless interaces value, > > ifconfig lagg0 ether 00:11:f5:9d:54:f5 > ifconfig lagg0 down/up Yup, that worked. wlan0 now associates just fine and will failover if bfe goes down. What should the proper fix be? Should lagg propagate the MAC address changes all the way down to the low-level driver? -- DEReceived on Thu Aug 28 2008 - 23:29:29 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:34 UTC