[Bug 211436] Link aggregation setting wlan mac changed in 11

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211436

Jason Bacon <bacon4000 at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bacon4000 at gmail.com

--- Comment #3 from Jason Bacon <bacon4000 at gmail.com> ---
Neither the prescribed method for 11.x nor using the MAC of the wireless
interface is working for me with 11.0-RELEASE.

The Ethernet interface works, but wireless failover does not connect:

Oct 17 08:59:09 oyster kernel: wlan0: link state changed to UP
Oct 17 08:59:09 oyster kernel: lagg0: link state changed to UP
Oct 17 08:59:09 oyster wpa_supplicant[21944]: wlan0: Associated with
b0:7f:b9:01:aa:3b
Oct 17 08:59:09 oyster dhclient[22096]: send_packet: No buffer space available
Oct 17 08:59:14 oyster last message repeated 2 times
Oct 17 08:59:17 oyster wpa_supplicant[21944]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=b0:7f:b9:01:aa:3b reason=0
Oct 17 08:59:17 oyster kernel: wlan0: link state changed to DOWN
Oct 17 08:59:17 oyster kernel: lagg0: link state changed to DOWN
Oct 17 08:59:17 oyster wpa_supplicant[21944]: wlan0:
CTRL-EVENT-SSID-TEMP-DISABLED id=1 ssid="MARITIME" auth_failures=2 duration=20
reason=CONN_FAILED
Oct 17 08:59:26 oyster dhclient[22096]: send_packet: Network is down

Both interfaces work fine without lagg, with the following config:

ifconfig_re0="DHCP"
wlans_urtwn0="wlan0"
ifconfig_wlan0="WPA DHCP"

This lagg config was working fine on 10.1:

ifconfig_re0="up"
ifconfig_urtwn0="ether e8:9a:8f:21:67:d3"
wlans_urtwn0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP"

I've tried this config, tried switching to

create_args_wlan0="wlanaddr e8:9a:8f:21:67:d3"

and tried 

ifconfig_re0="ether 80:1f:02:b6:a8:3e up"

instead of

ifconfig_urtwn0="ether e8:9a:8f:21:67:d3"

Any other suggestions?

Thanks,

   Jason

-- 
You are receiving this mail because:
You are the assignee for the bug.