a6969351a7
In AP+STA mode, wifi-scripts emits start_disabled=1 in the per-BSS section of the generated hostapd config so that hostapd defers beaconing on every BSS until apsta_state up clears the flag for the whole iface (uc_hostapd_iface_start clears start_disabled on every BSS and calls ieee802_11_set_beacon). When a new BSS is added later via iface.add_bss while the iface is already in HAPD_IFACE_ENABLED state, the freshly parsed config still carries start_disabled=1 for that BSS. hostapd_setup_bss is invoked with start_beacon=true, but hostapd_start_beacon then skips ieee802_11_set_beacon because conf->start_disabled is set. The kernel netdev is created without ever starting beacons, the carrier never comes up, and probe-response transmission attempts fail with "handle_probe_req: send failed". Mirror what iface.start does: when the iface is already enabled, the apsta channel selection has happened, so clear start_disabled for the incoming BSS before starting it. Signed-off-by: Felix Fietkau <nbd@nbd.name> |
||
|---|---|---|
| .. | ||
| config | ||
| ipv6 | ||
| services | ||
| utils | ||