Skip to content
Snippets Groups Projects
Select Git revision
  • fc46d4470f5ef30f6a310c0819201ea8be96a806
  • experimental default protected
  • v2023.2.5-ffs
  • nrb/ex400-remove-wps
  • nrb/airmax-test
  • v2023.2.4-ffs
  • nrb/ar9344-reset-sequence
  • autinerd/experimental-openwrt-24.10
  • v2023.2.3-ffs
  • v2023.2.2-ffs
  • v2023.2-ffs
  • v2023.1-ffs
  • v2022.1.4-ffs
  • feature/addMikrotikwAP
  • v2022.1.3-ffs
  • v2021.1.2-ffs
  • v2022.1.1-ffs
  • master protected
  • v2021.1.1-ffs
  • nrb/gluon-master-cpe510
  • v2021.1-ffs
  • experimental-2025-07-04
  • experimental-2025-07-04-base
  • experimental-2025-07-01
  • experimental-2025-07-01-base
  • experimental-2025-06-25
  • experimental-2025-06-25-base
  • experimental-2025-06-24
  • experimental-2025-06-24-base
  • experimental-2025-06-22
  • experimental-2025-06-22-base
  • v2023.2.5-ffs0.1
  • experimental-2025-06-08
  • experimental-2025-06-08-base
  • experimental-2025-06-06
  • experimental-2025-06-06-base
  • experimental-2025-05-27
  • experimental-2025-05-27-base
  • experimental-2025-05-18
  • experimental-2025-05-18-base
  • experimental-2025-05-15
41 results

0020-mac80211-ath10k-fix-incorrect-multicast-broadcast-rate-setting.patch

Blame
    • Sven Eckelmann's avatar
      b2f249e9
      ath10k/ath10k-ct: fix incorrect multicast/broadcast rate setting · b2f249e9
      Sven Eckelmann authored
      If no mcast_rate is set for the wifi-iface then there is no rate_idx (0)
      set for the bss. This breaks for example 5GHz meshpoint interfaces because
      0 maps to a CCK rate (11Mbit/s).
      
      It must also be avoided that the ath10k-ct internal state for the rates is
      not synced with the mac80211 rates state. Otherwise, the user specified
      rate (e.g. a wifi-iface mcast_rate for a meshpoint interface) will only be
      set on startup. And a short while after that, ath10k-ct specific code in
      ath10k_check_apply_special_rates is missing a valid rate in its own
      structures and is then recalculating a new default rate. This default rate
      is in most situations not the requested rate.
      
      Fixes: a399b607 ("ath10k/ath10k-ct: support multicast and management rate control")
      b2f249e9
      History
      ath10k/ath10k-ct: fix incorrect multicast/broadcast rate setting
      Sven Eckelmann authored
      If no mcast_rate is set for the wifi-iface then there is no rate_idx (0)
      set for the bss. This breaks for example 5GHz meshpoint interfaces because
      0 maps to a CCK rate (11Mbit/s).
      
      It must also be avoided that the ath10k-ct internal state for the rates is
      not synced with the mac80211 rates state. Otherwise, the user specified
      rate (e.g. a wifi-iface mcast_rate for a meshpoint interface) will only be
      set on startup. And a short while after that, ath10k-ct specific code in
      ath10k_check_apply_special_rates is missing a valid rate in its own
      structures and is then recalculating a new default rate. This default rate
      is in most situations not the requested rate.
      
      Fixes: a399b607 ("ath10k/ath10k-ct: support multicast and management rate control")
    index.rst 4.42 KiB