The current CSA beacon implementation appears to always advertise a switch to channel 14.
Channel 14 is not available in many regulatory domains, so client behavior may differ depending on locale and device firmware.
It could be useful to make the advertised target channel configurable (e.g. via a CLI flag) or optionally select a channel dynamically.
This would improve testing across different regulatory domains and make the CSA implementation more flexible for interoperability research.
P.S.: Angryoxide is a really cool project—thanks for that!
The current CSA beacon implementation appears to always advertise a switch to channel 14.
Channel 14 is not available in many regulatory domains, so client behavior may differ depending on locale and device firmware.
It could be useful to make the advertised target channel configurable (e.g. via a CLI flag) or optionally select a channel dynamically.
This would improve testing across different regulatory domains and make the CSA implementation more flexible for interoperability research.
P.S.: Angryoxide is a really cool project—thanks for that!