388 | | Please note that !WiFi interfaces do not appear in /sys/class/net in OpenWrt. Gateowrks typically uses the webadmin to configure the radio in AP or STA (client) mode. |
| 388 | Please note that !WiFi interfaces do not appear in /sys/class/net in OpenWrt. |
| 389 | |
| 390 | For testing !HaLow AP/STA/Mesh, Gateworks currently recommends avoiding the OpenWrt UCI layer for configuration of the interface, as it is not yet fully compatible with all features (i.e. WPA3 setup) out-of-the-box. Instead, a reliable approach is to have UCI not configure the !HaLow radio/interface, and manually set it up via the s1g tools (```wpa_supplicant_s1g```, ```hostapd_s1g```), explained in the [#configuration-(ap,-sta,-mesh) Configuration] section below. This route still allows for UCI / LuCI GUI to be used to configure other interfaces, bridges, etc. depending on your intended goal. |
| 391 | |
| 392 | {{{#!bash |
| 393 | # Disable UCI’s wifi control for radio0 (gw16159) |
| 394 | uci set wireless.radio0.disabled='1' |
| 395 | uci commit wireless |
| 396 | |
| 397 | # Setup interface manually |
| 398 | # i.e. |
| 399 | iw phy phy0 interface add wlan0 type managed |
| 400 | ifconfig wlan0 up |
| 401 | # For quick testing, allow incoming traffic |
| 402 | /etc/init.d/firewall stop |
| 403 | |
| 404 | # Now bring up network with hostapd_s1g or wpa_supplicant_s1g |
| 405 | }}} |
| 406 | |
| 407 | **Note**: By default, the OpenWrt firewall will block incoming data from wlan0 as /etc/config/firewall does not assign it into a zone. For testing, you can stop and disable the firewall, or configure it properly according to the [https://openwrt.org/docs/guide-user/firewall/firewall_configuration OpenWrt firewall documentation]. |