Bug 281468 - Alder Lake Intel WiFi (iwlwifi) will not associate to Marriott hotel networks
Summary: Alder Lake Intel WiFi (iwlwifi) will not associate to Marriott hotel networks
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: wireless (show other bugs)
Version: 15.0-CURRENT
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-wireless (Nobody)
URL:
Keywords:
Depends on:
Blocks: iwlwifi
  Show dependency treegraph
 
Reported: 2024-09-12 18:49 UTC by rkoberman
Modified: 2024-09-16 02:37 UTC (History)
1 user (show)

See Also:


Attachments
List of APs seen by ifconfig. (8.51 KB, text/plain)
2024-09-12 18:49 UTC, rkoberman
no flags Details
Log of debug output from wpa_supplicant (945 bytes, text/plain)
2024-09-16 02:35 UTC, rkoberman
no flags Details
Log of system boot with broken wpa_suppliment flags (3.73 KB, text/plain)
2024-09-16 02:37 UTC, rkoberman
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description rkoberman 2024-09-12 18:49:29 UTC
Created attachment 253526 [details]
List of APs seen by ifconfig.

I am again at  Marriott property and again forces to use my phone as my WiFi AP. T do even that, I must leave the hotel to get the association with my phone.

One significant issue is the large number of APs (mostly VAPs) I see with a list aps command. I get around 80, mostly VAPs. In the hotel, I never see my phone AP in the list unless I have connected to it from outside the hotel. I connected to my phone last night from across the street and kept the laptop and phone up and running since.

Network is fine on MacOS, Windows, iPhone and Android. My only Linux system is a VM, so I have no way to test that.

I am unsure what data I should collect as well as any appropriate debugging I should turn on. I might also try one of the several wpa_supplicants in ports.

I have limited time to test anything as I am only here through Sunday.

I am attaching the list aps output.
Comment 1 Bjoern A. Zeeb freebsd_committer freebsd_triage 2024-09-12 19:02:49 UTC
Turn wpa_supplicant debugging up and save the logs (possibly beyond the journey).

I assume there is nothing in the kernel message buffer (dmesg)?
Comment 2 rkoberman 2024-09-16 02:23:46 UTC
After many reboots and checking of logs, I'm really baffled. I now can get the interface to associate, but not the way it should.

I am attaching the verbose log of the failure. Not too interesting to me, but I'm far from expert.

I changed the wpa_supplicaant_flags to include '-f' to write the log to a file (as per the man page). Turns out that wpa-supplicant does not seem to recognize '-f'. '-h' does not show it in the list of options. I will also attach the log of that boot. The interface associated and operated normally. dhclient had no problem getting address and defaut route. I did note that the SSID shown by ifconfig was "MVC_GUEST ". My immediate thought was that there was a space appended to the SSID, so I changed my wpa_suplicant.conf file to add a space. Still failed to work.For each case of the SSID, it sill logged "No match".

I'll open a documentation ticket on the man page error.

I then deliberately made wpa_suppliment incorrect (adding
 a '-f file', and either rebooting or 'service netif restart wlan0' resulted in the error message and no running wpa_supplicant.

The also remains the issue of not seeing my phone AP when it is running.
Comment 3 rkoberman 2024-09-16 02:35:00 UTC
Created attachment 253596 [details]
Log of debug output from wpa_supplicant
Comment 4 rkoberman 2024-09-16 02:37:16 UTC
Created attachment 253597 [details]
Log of system boot with broken wpa_suppliment flags

Log of successful boot due to bad '-f' option to wpa_supplicant