This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| projects:software:openwrt_custom_wireless-regdb [2023/11/20 04:42] – [Installing your Custom wireless-regdb Package] --force-downgrade required for opkg generally because of version mismatch Andrew Yong | projects:software:openwrt_custom_wireless-regdb [2024/03/23 11:22] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== OpenWrt Custom wireless-regdb ====== | ====== OpenWrt Custom wireless-regdb ====== | ||
| + | Note: Do not use the patch below if you are in Singapore, as wireless-regdb is now maintained once again and updated Singapore regulatory rules have been released. | ||
| + | |||
| + | |||
| + | This information is just provided for reference in case one needs to test changes to wireless-regdb on an OpenWrt wireless AP. | ||
| ===== Motivation ===== | ===== Motivation ===== | ||
| - | As wireless-regdb | + | As wireless-regdb |
| Thankfully, it is pretty straightforward to set up a functional Wi-Fi 6E network, as only the Access Point requires a regulatory update, while stations (clients) do not. This is because the regulatory framework restricts [[https:// | Thankfully, it is pretty straightforward to set up a functional Wi-Fi 6E network, as only the Access Point requires a regulatory update, while stations (clients) do not. This is because the regulatory framework restricts [[https:// | ||