[FS#550] hostapd (wpad-mesh) fails to start interface at same time with meshpoint interface

[LEDE Bugs]

The following task has a new comment added:

FS#550 - hostapd (wpad-mesh) fails to start interface at same time with meshpoint interface
User who did this - Charlemagne Lasse (charlemagnelasse)

----------
I think I found out what I did differently with OpenWrt. I think I was using auth_sae:


CONFIG_TARGET_ar71xx=y
CONFIG_TARGET_ar71xx_generic=y
CONFIG_TARGET_ar71xx_generic_DEVICE_OM2P=y
CONFIG_OPENSSL_WITH_DEPRECATED=y
CONFIG_OPENSSL_WITH_EC=y
CONFIG_OPENSSL_WITH_NPN=y
CONFIG_OPENSSL_WITH_PSK=y
CONFIG_OPENSSL_WITH_SRP=y
CONFIG_PACKAGE_authsae=y
CONFIG_PACKAGE_libconfig=y
CONFIG_PACKAGE_libopenssl=y
CONFIG_PACKAGE_wpad-mesh=y
# CONFIG_PACKAGE_wpad-mini is not set



phy#0
        Interface ap-2
                ifindex 9
                wdev 0x5
                addr ac:86:74:00:00:01
                ssid meshedAP
                type AP
                channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
                txpower 20.00 dBm
        Interface mesh-2
                ifindex 8
                wdev 0x4
                addr ae:86:74:00:00:01
                type mesh point
                channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
                txpower 20.00 dBm



But afaik, auth_sae is not supporting DFS and is extreme limited
----------

More information can be found at the following URL:
https://bugs.lede-project.org/index.php?do=details&task_id=550#comment1955