# Wpa\_supplicant\_s1g.conf for WPA3 (connecting to HaLowLink 1) **URL:** \ **Category:** Software\ **Tags:** halowlink-1\ **Created:** [August 26, 2025, 11:43pm UTC](https://community.morsemicro.com/t/wpa-supplicant-s1g-conf-for-wpa3-connecting-to-halowlink-1/793 "2025-08-26T23:43:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![bstewart](https://avatars.discourse-cdn.com/v4/letter/b/85f322/32.png) [@bstewart](https://community.morsemicro.com/u/bstewart)\ **Post date:** [August 26, 2025, 11:43pm UTC](https://community.morsemicro.com/t/wpa-supplicant-s1g-conf-for-wpa3-connecting-to-halowlink-1/793/1 "2025-08-26T23:43:06Z")
Hi, I’m having a problem with this setup and likely need help creating a proper WPA3 wpa\_supplicant\_s1g conf file. I am getting _AUTH TIMEOUT_ errors specifically when trying to connect a **GW16159 STA** to a **HaLowLink 1 AP** with WPA3 SAE. **What works:** - GW16159 STA ↔ GW16159 AP - GW16159 MESH ↔ GW16159 MESH - EKH05 STA ↔ GW16159 AP (WPA3) - EKH05 STA ↔ HaLowLink 1 AP The HaLowLink appears when I scan for APs on the GW16159 ([attached log](https://gist.github.com/ChipDev/20655681af35c03bd43821499a9d8b2a)) The [output from wpa\_supplicant\_s1g](https://gist.github.com/ChipDev/7a0867e5096df25e8f4b4f978eaa34bc) seems to get to the authentication phase but times out, specifically between lines 348 and 379. The log also contains the morse\_cli version and conf file. I couldn’t find any pre-made examples of WPA3 S1G configuration, and all the other ones I’ve tried have failed due to parsing or the same AUTH\_TIMED\_OUT error. Another interesting thing to note is after this error, `iw dev wlan0 scan` returns nothing, until I reload the kernel module and ifconfig wlan0 up. Any sanity checks and default configuration would be greatly appreciated. Thank you ---
**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\ **Post date:** [August 27, 2025, 4:14pm UTC](https://community.morsemicro.com/t/wpa-supplicant-s1g-conf-for-wpa3-connecting-to-halowlink-1/793/2 "2025-08-27T16:14:23Z")
Hi @bstewart There is an example (and minimal) set of both hostap and wpa\_supplicant configurations towards the end of the [Linux Porting Guide](https://www.morsemicro.com/download/linux-driver-porting-guide-app-note-24/) - which you’ve also reminded me to chase down the update. You can also extract configs off HaLowLink1s configured in ways you desire by looking at `/var/run/wpa_supplicant-wlan0.conf` and `/var/run/hostapd-phy.conf`. Still going through the error log, but the HaLowLink1 will be set as sae\_pwe=1. With the supplicant config set as sae\_pwe=2, maybe it’s trying hunting and pecking? Wi-Fi HaLow certification allows Hash-to-Element only. Worth trying sae\_pwe=1. Will let you know if we spot anything else in the log. ---
**Author:** ![bstewart](https://avatars.discourse-cdn.com/v4/letter/b/85f322/32.png) [@bstewart](https://community.morsemicro.com/u/bstewart)\ **Post date:** [August 27, 2025, 6:43pm UTC](https://community.morsemicro.com/t/wpa-supplicant-s1g-conf-for-wpa3-connecting-to-halowlink-1/793/3 "2025-08-27T18:43:59Z")
Thank you for the quick reply @ajudge I’ve read through the Linux Porting Guide and brought over your minimal conf file and startup command. Still getting AUTH\_TIMED\_OUT and then no longer finding the network (log includes when I ^C and manually stop the process) Here’s a few things that I’ve noted: - I was using the wrong ctrl\_interface, so I changed it to be s1g - Both the HaLowLink and my GW16159 (Silex SX-SDMAH module) have the same FW and HW version, but my HaLowLink Morse\_cli version is rel\_1\_12\_4\_2024\_Jun\_11 while my SBC is Morse\_cli version rel\_1\_12\_5\_2024\_Jul\_25-4-g3541610. Here’s the [log from today](https://gist.github.com/ChipDev/2d0254260b078e2c72cde653933d0538) which includes my lsmod, conf, morse\_cli version, and the wpa\_supplicant\_s1g. If you think that there might be a kernel/firmware problem, let me know and I can send any other system configuration. Also: my HaLowLink has no wpa\_supplicant configuration files in /var/run, only an empty directory. I’ll now try and test AP/STA between two GW16159 boards (instead of using the HaLowLink as the AP) to try and narrow down this issue. Thanks again for the help. Blake EDIT: Between two GW16159s running on identical setups, one as the STA I’ve been trying to connect and another as a WPA3 AP, I’ve successfully made a connection. It seems that the security is the same, and here’s a link to an iw scan that shows both APs. Both seem to be on CCMP and SAE. [Here’s a link to that scan](https://gist.github.com/ChipDev/1da49565c363f36549131f8c78f02bb7). Thanks again. ---
**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\ **Post date:** [August 28, 2025, 12:28am UTC](https://community.morsemicro.com/t/wpa-supplicant-s1g-conf-for-wpa3-connecting-to-halowlink-1/793/4 "2025-08-28T00:28:42Z")
The morse\_cli version is an artefact of the initial effort to Open Source software which was previously closed source. Not pretty, but shouldn’t be a contributing factor here. Sorry I should have been clearer. If your HaLowLink1 is configured as an AP, it will only have a `/var/run/hostap-phy.conf` file. If you put it into a client mode, it will build a supplicant config. Curious to know if a HaLowLink1 in client mode connects to the GW16159 AP. So there are two things that stand out to me here: - SAE auth timeout - which I would have expected to be the sae\_pwe setting. Moving on.. - Signal strength from the HaLow AP is -11dBm. This is quite a hot signal (though anecdotally things should still function here), moving the devices another few meters away or angling the HaLowLink1 antenna ~45 degrees, might add enough attenuation if an SAE frame is corrupted in transit. It might be helpful to extract AP logs from the HaLowLink1 if the above doesn’t work. ssh into the HL1 and add `option log_level '0'` to the `wifi-device` of `option type morse` in `/etc/config/wireless`. Then `service network restart` to restart the AP. This should output more hostap logging to the HL1 syslog which you can extract with `logread -l -f -e hostapd_s1g`. Hopefully this tells us why the AP is rejecting the station. Failing that - putting a third device in monitor mode to inspect the packets in flight might be required as well. There’s some instructions for putting Morse Micro devices into a sniffer mode in [APPNOTE-36](https://www.morsemicro.com/download/how-to-do-a-sniffer-capture-app-note-36/). This should work for your GW-16159 devices as well if you follow the CLI configuration. ---
**Author:** ![bstewart](https://avatars.discourse-cdn.com/v4/letter/b/85f322/32.png) [@bstewart](https://community.morsemicro.com/u/bstewart)\ **Post date:** [August 28, 2025, 7:14pm UTC](https://community.morsemicro.com/t/wpa-supplicant-s1g-conf-for-wpa3-connecting-to-halowlink-1/793/5 "2025-08-28T19:14:09Z")
@ajudge Turns out the problem was relatively expected behavior; as per the GW16159 documentation `924MHz is disabled in mm6108 firmware due to noise exceeding specification` Upon changing the HaLowLink AP frequency to 916MHz the board connects nicely.