[OpenWrt-Devel] [LEDE-DEV] [PATCH] mac80211: pass hostapd control socket to mesh-mode supplicant

Felix Fietkau nbd at nbd.name
Fri Apr 13 05:37:22 EDT 2018

On 2018-04-13 11:34, Sven Eckelmann wrote:
> On Freitag, 13. April 2018 01:41:31 CEST Daniel Golle wrote:
>> Unlike when operating in Ad-Hoc mode, we apparently need to pass the
>> hostapd control socket interface to wpa_supplicant when using 802.11s
>> mesh mode.
>> There also seems to still be something wrong with the logic setting
>> channel and (v)htmode parameters when using AP + mesh...
> I haven't tested the current state but this was basically breaking encrypted 
> mesh + AP (AP never came up). Problem was the code (OpenWrt specific) in 
> wpa_supplicant which called STOP_AP via this socket.
The control socket code was written for AP+Client. It usually calls
STOP_AP before it attempts a new scan + assoc. When the interface is
connected again, it starts the AP again on the new operating frequency.
I don't think the problem is STOP_AP itself, I think the problem is the
lack of a start call when the mesh interface is set up properly.

- Felix
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list