Date: Wed, 21 Jun 2017 19:56:44 +0200 From: Guido Falsi <madpilot@FreeBSD.org> To: Renato Botelho <garga@FreeBSD.org>, freebsd-current@freebsd.org Subject: Re: Failover Mode Between Ethernet and Wireless Interfaces broken on >= 11 Message-ID: <b73ee75f-7f39-710e-d378-3172ec57b1e0@FreeBSD.org> In-Reply-To: <1c1e5c6f-35e5-ca14-2e23-5e33d86a5266@FreeBSD.org> References: <1c1e5c6f-35e5-ca14-2e23-5e33d86a5266@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/21/17 19:48, Renato Botelho wrote: > I've already sent it to net, but I suspect this is the appropriate place > to discuss this subject. [...] > > My next attempt was to do the other way round and make lagg to use wlan0 > mac address instead of em0's. but even doing this my wireless interface > ended up not working. Strange enough, this works for me. My laptop has a bge interface. Maybe that's relevant. [...] > > And configured it to use wlan0 mac address on rc.conf: > > ifconfig_em0="ether 60:67:20:c5:2d:48 up" > wlans_iwn0="wlan0" > ifconfig_wlan0="WPA" > cloned_interfaces="lagg0" > ifconfig_lagg0="up laggproto failover laggport em0 laggport wlan0 DHCP" > > and it's now working as expected. I can confirm this is exactly what I've been doing for a while on my laptop. As noted before I did not need to patch the kernel to have this working. > > Other than that, I believe if wlan interfaces cannot have their mac > address changed, ifconfig should return an error when user attempts to > do it, and if_setlladdr() should do the same. > > Thoughts? I agree returning some error code would be nicer on users. -- Guido Falsi <madpilot@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b73ee75f-7f39-710e-d378-3172ec57b1e0>