Interesting. Looks like a scan is hung.When I start a superuser scan, I log
exactly two lines:
May  5 22:45:22 ptavv kernel: wlan0: ieee80211_scanreq: vap
0xfffffe0167a47010 iv_state 0x5 (RUN) flags 0x1b duration 0x7fffffff
mindwell 0 maxdwell 0 nssid 0
May  5 22:45:22 ptavv kernel: wlan0: ieee80211_swscan_start_scan_locked:
active scan already in progress


On Mon, May 5, 2025 at 10:14 PM Adrian Chadd <adr...@freebsd.org> wrote:

> hi,
>
> it should start logging stuff to the kernel log! Try looking at the dmesg
> output :)
>
>
> We don't have a useful tracing mechanism besides that right now.
>
>
>
> -adrian
>
>
> On Mon, 5 May 2025 at 21:59, Kevin Oberman <rkober...@gmail.com> wrote:
>
>> On Sun, May 4, 2025 at 1:29 PM Adrian Chadd <adr...@freebsd.org> wrote:
>>
>>>
>>>
>>> On Sun, 4 May 2025 at 10:41, Bjoern A. Zeeb <b...@freebsd.org> wrote:
>>>
>>>> On Sun, 4 May 2025, Kevin Oberman wrote:
>>>>
>>>> Hi,
>>>>
>>>> > I have now located and am now running on an ASUS RT-ARCH13 router
>>>> connected
>>>> > to Comcast. This device claims WiFi5 compliance with 11ac and CCMP.
>>>> >
>>>> > Still stuck at 11ng and only connects at 2.4G.
>>>> >
>>>> >> ifconfig wlan0
>>>> > wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0
>>>> mtu 1500
>>>> > options=0
>>>> > ether 70:a8:d3:df:3c:de
>>>> > inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
>>>> > groups: wlan
>>>> > ssid babcom channel 11 (2462 MHz 11g ht/20) bssid 4c:ed:fb:37:b0:20
>>>> > regdomain FCC country US authmode WPA2/802.11i privacy ON
>>>> > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60
>>>> > protmode CTS -ampdu ampdulimit 64k -amsdutx amsdurx shortgi
>>>> > -ldpctx ldpcrx -uapsd wme roaming MANUAL
>>>> > parent interface: iwlwifi0
>>>> > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
>>>> > status: associated
>>>> > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>>> >
>>>> > My AP shows up as: 11   54M  -51:-96   100 EP   HTCAP VHTCAP
>>>> VHTOPMODE WME
>>>> > ATH RSN
>>>> > The 5G SSID does not show up at all, though my phone shows it and
>>>> connects
>>>> > successfully. Attempts to manually scan return instantly and list scan
>>>> > always list the exact same data including S/N, so it does not seem to
>>>> > actually scan.
>>>>
>>>
>>> Is there still that scan bug where an interrupted scan never finishes,
>>> and thus "ifconfig wlan0 scan" always returns cached scan results?
>>> I thought that was fixed years ago. :/
>>>
>>> Also, Kevin, is this on iwlwifi? That should be doing offloaded
>>> scanning, right bz? So as long as we send a well crafted firmware
>>> message with a useful dwell time, it should be seeing the beacons?
>>>
>>> What dwell time is being configured when doing scanning on iwlwifi?
>>>
>>>
>>>
>>> -adrian
>>>
>>>
>>>>
>>>> You are #5 reporting this lately of either not seeing the SSID or it
>>>> taking ages to show up.  I initially started with 1 then 3 people.
>>>> Some say another AP n their mesh further away does show up in scan
>>>> results but the one next to them does not.
>>>>
>>>> There is also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286493
>>>> (for the "takes ages" to assoc).
>>>>
>>>>
>>>> If you run `ifconifg wlan0 scan` as super user; sometimes you have to
>>>> try
>>>> 10-15 times; eventually it hangs;  then give it some time and if it
>>>> doens't return after 30-60s ^c and do a list scan manually.
>>>>
>>>> There's something really fishy going on somewhere but we don't know yet.
>>>>
>>>>
>>> Hm, can you re-do the scan with scan debugging enabled?
>>>
>>> wlandebug -i wlan0 +scan
>>>
>>> let's see what the scan engine sees, in case it's tossing out frames for
>>> some reason.
>>>
>>>
>>>
>>> -adrian
>>>
>>> --
>>>> Bjoern A. Zeeb                                                     r15:7
>>>>
>>>>
>> I'm afraid that I am baffled as to running wlandebug. The man page didn't
>> help much.
>>
>> When I run the command, it prints out a single line and exits. Is there
>> something I need to do to collect data when I start a scan?
>> --
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkober...@gmail.com
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>>
>

-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683

Reply via email to