# Feature request: Add Passpoint features for all bands including s1g

**URL:** <https://community.morsemicro.com/t/feature-request-add-passpoint-features-for-all-bands-including-s1g/2018>\
**Category:** Software\
**Created:** [September 14, 2026, 12:28am UTC](https://community.morsemicro.com/t/feature-request-add-passpoint-features-for-all-bands-including-s1g/2018 "2026-09-14T00:28:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![hgot07](https://avatars.discourse-cdn.com/v4/letter/h/bcef8e/32.png) [@hgot07](https://community.morsemicro.com/u/hgot07)\
**Post date:** [September 14, 2026, 12:28am UTC](https://community.morsemicro.com/t/feature-request-add-passpoint-features-for-all-bands-including-s1g/2018/1 "2026-09-14T00:28:09Z")

</div>

It seems the current MorseMicro/openwrt 3.1.1 lacks Passpoint features.

I’d like to request for Passpoint features, especially STA side at the moment, for all bands including s1g. The first step is to add Passpoint configuration parameters for STA to hostapd.sh since it lacks client-side configuration parameters while already has AP-side ones.

The vanilla OpenWrt also lacks this feature. I’ve tried adding some parameters for Passpoint STA and my repository would be useful. You could simply try patch command with --dry-run to see what would be the changes.

> **[openwrt-passpoint/sta/25.12/lib/netifd at main · hgot07/openwrt-passpoint](https://github.com/hgot07/openwrt-passpoint/tree/main/sta/25.12/lib/netifd)**
>
> main/sta/25.12/lib/netifd

Please see also the following:

> [@Passpoint configuration for Wi-Fi HaLow](https://community.morsemicro.com/t/passpoint-configuration-for-wi-fi-halow/2003):
>
> I’ve been trying Passpoint configuration on two HaLowLink 2 (JP), one for AP and the other for client. I tested WPA3 Enterprise configuration earlier and it worked. I’ve added Passpoint configuration (hs20\_ and iw\_ options) to /etc/config/wireless on the AP. It seems that they are successfully added to hostapd-phy1-wlan0.conf and working well. On the client side, however, the authentication by WPA3 Enterprise fails to start despite the successful ANQP. I think there are some parameter mismatc…

s1g needs additional `pmf=1`parameter in the output wpa\_supplicant-\*.conf file.
