Date: Mon, 01 May 2023 22:53:22 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 271188] iwlwifi with lagg added to bridge will not associate to AP Message-ID: <bug-271188-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271188 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 aft= er restarting network. This was not a problem in 13.1-STABLE from late Decemb= er 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 aga= in, or it may result in a kernel panic. Relevant rc.conf entries: kld_list=3D"if_iwlwifi i915kms" ifconfig_re0=3D"ether c4:75:ab:f3:f9:6c" wlans_iwlwifi0=3D"wlan0" ifconfig_wlan0=3D"WPA" cloned_interfaces=3D"lagg0 bridge0 tap0" ifconfig_lagg0=3D"laggproto failover laggport re0 laggport wlan0 DHCP" ifconfig_bridge0=3D"addm lagg0 addm tap0" --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271188-21060>