fca4b87420
Increasing ev.type by one for these event types works due to the order of the elements in enum uevent_type, but makes the code harder to understand and debug. Imagine seeing the following event log: Mon Jun 27 22:08:43 2022 user.info usteer: usteer event=probe_req_deny node=hostapd.wl24-iot sta=e4:5f:01:00:92:b6 reason=better_candidate signal=-79 assoc=1 load=27 select_reason=signal remote=fe80::b2a7:b9ff:fecb:eeba#hostapd.wl24-iot remote_signal=-39 remote_assoc=13 remote_load=20 Trying to find probe_req_deny (UEV_PROBE_REQ_DENY) in the code will not yield any useful results. Assigning the enum element to ev.type makes it much easier to find where exactly the above log event comes from. Signed-off-by: Stijn Tintel <stijn@linux-ipv6.be> Acked-by: David Bauer <mail@david-bauer.net>
usteer
usteer is a client steering daemon written for OpenWrt.
Its goal is to optimize roaming behavior of wireless clients (STAs) in a ESS consisting of multiple BSS / APs.
Functions
- Synchronization of Neighbor Reports between multiple APs
- Policy-based decisions for probe- / association- / authentication requests received from STAs
- Requesting clients to roam to a different BSS based on SNR / signal-level
- Channel-load based client steering to different BSS
Installation
usteer is available from the OpenWrt packages feed and can be installed on devices running OpenWrt 21.02+ using opkg:
opkg update; opkg install usteer
Submitting patches
usteer patches are welcome on the openwrt-devel mailing list.
Before submitting patches, check out OpenWrts guide on submission policies.
Make sure to add a usteer subject prefix using the --subject-prefix option when exporting the patch with git format-patch.