It turned out that some of my tests were bogus. Creation order does
not matter. Only the first one works. Still unclear why but it's
probably not a wpa_supplicant issue.
Sorry for the noise.
Regards,
Viktor
On Sat, 27 Jul 2019 at 15:10, viktor babrian <viktor.babrian@xxxxxxxxx> wrote:
>
> Hi,
>
> I am trying to bring up an AP and a mesh point on a wireless device
> that supports:
> * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{
> P2P-client, P2P-GO } <= 1,
> total <= 2048, #channels <= 1, STA/AP BI must match
>
> I create a second interface for mesh.
> If I run wpa_supplicant creating the AP first, mesh second, everything
> goes as expected:
> # wpa_supplicant -B -iwlan0 -c ~v/wpa_supplicant_ap.conf -N -imesh0 -c
> ~v/wpa_supplicant_mesh.conf -u -ffile -dd
> # iw dev
> phy#0
> Interface mesh0
> ifindex 5
> wdev 0x2
> addr f8:d1:11:7a:d5:89
> type mesh point
> txpower 14.00 dBm
> Interface wlan0
> ifindex 4
> wdev 0x1
> addr f8:d1:11:7a:d5:88
> ssid ceepbc:asdf
> type AP
> channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
> txpower 14.00 dBm
>
> Both networks are OK.
> However when I create mesh first, then AP:
> # wpa_supplicant -B -imesh0 -c ~v/wpa_supplicant_mesh.conf -N -iwlan0
> -c ~v/wpa_supplicant_ap.conf -u -ffile -dd
>
> AP is not set up. According to debug output:
> nl80211: Set beacon (beacon_set=0)
> [...]
> nl80211: Beacon set failed: -16 (Device or resource busy)
> Failed to set beacon parameters
>
> I experience this behavior on two different setups (wifi devices:
> ath9k and TI). I do not see it with mac80211_hwsim.
>
> Is this a hardware related issue? Or some wpa_supplicant settings?
> Any help is welcome,
> Viktor
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
