[Bug]: Unable to Connect to Passswordless WPA/WPA2 AP's

[tsull360]

Code of Conduct

• I agree to follow this project's Code of Conduct.

Issue reporting checklist

• I have read and understand the issue reporting policy.
• I have read and followed the common sense checklist.
• I observed this bug on a clean install of a supported OS.
• I have followed the project prerequisites.
• I have searched this repository for existing issues.
• I checked the FAQ and official documentation.
• I am using an external wireless adapter.
• I have generated a RaspAP debug log and performed a self-diagnosis.

Operating System

Raspberry Pi OS Lite 64-bit Debian 13 (trixie)

Installation method

Pre-built image

Onboard wireless chipset or external adapter?

Onboard wireless chipset

Hardware

Raspberry Pi 5

RaspAP version

Latest

Other software or services running with RaspAP?

No other software

Contact details (optional)

tsull360@outlook.com

Bug description

Marriott hotel chains use a captive portal setup. Connecting to the network itself does not require a password, however RaspAP will not connect to the network as it expects a password as the network is using WPA2.

Steps to reproduce

1. Be in range of 'MarriottBonvoy_Guest' network.
2. Attempt to Add network via RaspAP, do not provide a password.
3. Observe error of 'WPA passphrase must be between 8 and 63 characters'.

Screenshots

Additional context

No response

Relevant log output

[billz]

Execute sudo iw dev wlan0 scan on your device (substituting wlan0 for your client interface, if necessary) and capture the details of the network you're trying to connect to.

[tsull360]

I'm not at this hotel anymore. Perhaps I can setup a test router with no password to try and duplicate the issue.

[billz]

Coincidentally, I was at a hotel recently that's part of the Marriott Bonvoy group. I did a scan of the guest network and found the following:

Aloft_GUEST - bssid=b0:b8:67:d6:f9:91, security=open, channel=5g149/20

So the network is indeed open (no encryption) and has the expected captive portal auth, which happens after the layer 2 connection. I didn't have a device to test this, but RaspAP shouldn't treat this as needing authentication.

[tsull360]

Thanks @billz for taking the time to test and repro. Any additional information or data needed at this point?

[billz]

@tsull360 I was unable to reproduce the issue as I didn't have a Pi on hand; only a laptop. A scan from the original network would be helpful, otherwise this is inconclusive.

[tsull360]

@billz understood. What all testing/data gathering is needed? There is one not too far from me I can go to.

[billz]

That would be ideal. Get within range of the guest network with your device and execute sudo iw dev wlan0 scan (see my original comment). thanks