Re: AX210 testing, problems connecting 11ac
- Reply: Peter Miller: "Re: AX210 testing, problems connecting 11ac"
- In reply to: Peter Miller: "Re: AX210 testing, problems connecting 11ac"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 22 Apr 2025 23:28:43 UTC
On Mon, 21 Apr 2025, Peter Miller wrote: > On Mon Apr 21, 2025 at 7:22 PM CDT, Bjoern A. Zeeb wrote: >> On Sun, 20 Apr 2025, Peter Miller wrote: >> >> Hi Peter, >> >>> I saw the call for wifi testing [1], and tested. I thought I was one of the >>> people not connecting to 11ac. Then I forced 11ac in /etc/rc.conf and was >>> able to connect with 11ac, but, I have to restart networking to get it >>> working; sometimes multiple restarts. >> >> Sometimes some repeated >> ifconfig wlan0 scan >> as super user will also do it (you'll notice when it doesn't return >> immediately). Might be less destructive than restarting networking. > > It did hang, but it didn't connect to 11ac. I ended up doing the restart > method again. What was the scan result? Were the networks on 11a included at that moment? You could add multiple entries to wpa_supplicant.conf with bssid also set and order them by priority. Shot in the dark. >>> My wifi is provided by a linksys velop whw03 [2] which has 2.4 and >>> 5ghz enabled. >>> >>> To use 11ac I have the following line in /etc/rc.conf >>> ifconfig_wlan0="mode 11ac WPA DHCP" >>> >>> Once 11ac connects, I was able to get 300+ mbits using ookla-speedtest and >>> iperf3 locally. >>> >>> All the info below is before I forced/added 11ac to rc.conf >> >> Your scan reuslt only shows the 2.4Ghz SSID if that was all. That's >> likely the issue. >> >> Can you at some point also post the sysctl output and the scan result >> when you are connected to 11a[c]? Would be interesting to know. >> > > Here it is on 11ac. > Note: I switched to pkgbase today, so it's a slightly different kernel. The sysctl only has beacon strength which looks okay and it is some list of scan results but I cannot see why it would not have the 11a networks in the scan results if not forced to 11a. Can you try a bit more without setting it to 11ac and then check wlanstat output or enable wlandebug wlan0 +scan if anything becomes noticable. Then the next question is: if your 11a network(s) show up in the scan results will they be picked automatically, which was unclear above. Lots of health, /bz -- Bjoern A. Zeeb r15:7