On 11/07/2017 01:19 PM, Sven Eckelmann wrote:
> The beacon_int is currently set explicitly for hostapd and when LEDE uses
> iw to join an IBSS/mesh. But it was not done when wpa_supplicant was used
> to join an encrypted IBSS or mesh.
>
> This configuration is required when an AP interface is configured together
> with an mesh interface. The beacon_int= line must therefore be re-added to
> the wpa_supplicant config. The value is retrieved from the the global
> variable.
>
> Fixes: 1a16cb9c67f0 ("mac80211, hostapd: always explicitly set beacon
> interval")
> Signed-off-by: Sven Eckelmann <sven.eckelm...@openmesh.com>
> ---
> This patch was only tested with LEDE 17.01.4. And only in sta and mesh mode.
>
> package/network/services/hostapd/files/hostapd.sh | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/package/network/services/hostapd/files/hostapd.sh
> b/package/network/services/hostapd/files/hostapd.sh
> index 68f84c5e8b..5a9381b4d1 100644
> --- a/package/network/services/hostapd/files/hostapd.sh
> +++ b/package/network/services/hostapd/files/hostapd.sh
> @@ -713,8 +713,9 @@ wpa_supplicant_add_network() {
> ;;
> esac
> }
> - local beacon_int brates mrate
> +This change is already in master, see https://git.lede-project.org/?p=source.git;a=commitdiff;h=5e481881d7abd814abbf40a046be90cbaf835e72 Let's just backport this trivial change to lede-17.01. > [ -n "$bssid" ] && append network_data "bssid=$bssid" "$N$T" > + [ -n "$beacon_int" ] && append network_data "beacon_int=$beacon_int" > "$N$T" 1a16cb9c67f0d2c530914aec31c721b75f03a908 moved setting beacon_int from wpa_supplicant_add_network() to hostapd_prepare_device_config(). Does encrypted IBSS/mesh setup somehow not use hostapd_prepare_device_config()? How do the resulting hostapd.conf look at the moment? Matthias
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Lede-dev mailing list Lede-dev@lists.infradead.org http://lists.infradead.org/mailman/listinfo/lede-dev
