aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/net/lapb/lapb_timer.c
diff options
context:
space:
mode:
authorBenjamin Berg <benjamin@sipsolutions.net>2025-04-30 21:10:42 +0200
committerJohannes Berg <johannes.berg@intel.com>2025-05-08 23:59:12 +0200
commitcf1b684a06170d253b47d6a5287821de976435bd (patch)
tree7833d3b285308cfedb544c4ad08d372c3cb8bb83 /net/lapb/lapb_timer.c
parentMerge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (diff)
downloadwireguard-linux-cf1b684a06170d253b47d6a5287821de976435bd.tar.xz
wireguard-linux-cf1b684a06170d253b47d6a5287821de976435bd.zip
wifi: mac80211: do not offer a mesh path if forwarding is disabled
When processing a PREQ the code would always check whether we have a mesh path locally and reply accordingly. However, when forwarding is disabled then we should not reply with this information as we will not forward data packets down that path. Move the check for dot11MeshForwarding up in the function and skip the mesh path lookup in that case. In the else block, set forward to false so that the rest of the function becomes a no-op and the dot11MeshForwarding check does not need to be duplicated. This explains an effect observed in the Freifunk community where mesh forwarding is disabled. In that case a mesh with three STAs and only bad links in between them, individual STAs would occionally have indirect mpath entries. This should not have happened. Signed-off-by: Benjamin Berg <benjamin@sipsolutions.net> Reviewed-by: Rouven Czerwinski <rouven@czerwinskis.de> Link: https://patch.msgid.link/20250430191042.3287004-1-benjamin@sipsolutions.net Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions