[Bug 271188] iwlwifi with lagg added to bridge will not associate to AP

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

            Bug ID: 271188
           Summary: iwlwifi with lagg added to bridge will not associate
                    to AP
           Product: Base System
           Version: 13.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: wireless
          Assignee: wireless@FreeBSD.org
          Reporter: js@jschneider.com

As described in bug #271182 one can add iwlwifi to lagg but must restart
network after boot in order to associate to an AP.  However, if you also add
your lagg device to a bridge, you can no longer associate to an AP even after
restarting network.  This was not a problem in 13.1-STABLE from late December
2022 but is now a problem with 13.2-STABLE. Furthermore, multiple network
restarts result in a kernel panic.

ifconfig wlan0 scan results in valid AP list zero or more times, but at no
point does wlan0 associate with AP.  As soon as scan shows no AP's, it will not
show AP's again. 'service netif restart' may result in scanning working again,
or it may result in a kernel panic.

Relevant rc.conf entries:

kld_list="if_iwlwifi i915kms"
ifconfig_re0="ether c4:75:ab:f3:f9:6c"
wlans_iwlwifi0="wlan0"
ifconfig_wlan0="WPA"
cloned_interfaces="lagg0 bridge0 tap0"
ifconfig_lagg0="laggproto failover laggport re0 laggport wlan0 DHCP"
ifconfig_bridge0="addm lagg0 addm tap0"

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