I'm guessing that TP-Link is choosing to lock out all open source software on their devices and blaming it on the FCC.
There is no reason TP-Link or any other vendor can't use signed radio firmware enforcing region specific regulatory limits. Almost all countries have these rules (most follow the US FCC or the EU ETSI, but some have their own). The purpose is to prevent unauthorized use of the unlicensed spectrum. The limits include: allowed RF channels, effective indicated radiated power (EIRP), and Dynamic Frequency Selection (DFS) which protects incumbent services (Military and weather radar) that share the more recently authorized 5 GHz channels (Extended UNI-II)
This is something that PCs have done for years. . The radio is untouchable by user, yet the PCs can run all sorts of open source operating systems. WiFi adaptors have their own embedded firmware that is controlled by the chipset maker (Broadcom, Intel,...)
Slashdot Mirror
I'm guessing that TP-Link is choosing to lock out all open source software on their devices and blaming it on the FCC.
There is no reason TP-Link or any other vendor can't use signed radio firmware enforcing region specific regulatory limits. Almost all countries have these rules (most follow the US FCC or the EU ETSI, but some have their own). The purpose is to prevent unauthorized use of the unlicensed spectrum. The limits include: allowed RF channels, effective indicated radiated power (EIRP), and Dynamic Frequency Selection (DFS) which protects incumbent services (Military and weather radar) that share the more recently authorized 5 GHz channels (Extended UNI-II)
This is something that PCs have done for years. . The radio is untouchable by user, yet the PCs can run all sorts of open source operating systems. WiFi adaptors have their own embedded firmware that is controlled by the chipset maker (Broadcom, Intel,...)