It should probably be noted changing the regulatory region of an RF device may result in you using illegal frequencies in your area depending on the combination of which region you're in and which region you're setting it to.

5 replies saying the same things appeared so I'll respond to myself rather than try to pick one:

A TV is indeed typically a client. Or station, if you want to dust off your CWNA certificate. One should still include the warning when sharing such projects/advice because of considerations like:

- With no explanations or warnings, the reader may very reasonably apply the same type of fix across several of their badly preconfigured devices. Now when they extend their Windows laptop display wirelessly to the TV over Miracast (a direct exchange this TV supports), both devices will agree they can do so on the bands in whatever region they were set to.

- It's not safe to assume only the AP needs and has a correct regulatory db or regulatory domain set. APs for the wrong region are sold/imported, do not always have correct regulatory dbs, and can also be similarly misconfigured. Clients can also peer to peer or hotspot. In general, you should fairly be warned you're removing one of the 2 sides to the safety system and "the channel I wanted appeared" is not the same thing as "I fixed the buggy channel config on the device".

- As some have pointed out, clients can perform either an active or passive scan based on, basically, what the system feels makes the most sense at the time. An active scan will result in probes across the supported channel list, so even if all of the above is true, people should be aware even a lone station can still transmit on all of the bands it is told to support.

I'm not against fixing buggy devices but I am against telling people the fix is to set it to Germany without warning they may result in using illegal frequencies in your area if not carefully considered. A muuuch cooler & safer fix might have been to patch the supported channel list for the given country to be correct rather than patch the region to be wrong, but that may have been harder to pull off.

Yeah, not sure if author knows, they certainly don't share if they understand this or not, but these things aren't available because the some governments say those frequencies are illegal to use. Turkey for example has multiple frequencies under 5Ghz WiFi that is banned, hence consumer don't get to use 5Ghz WiFi. If you change that, you're breaking the law and you might get a visit, depending on how hardcore they are about the rules. Tend to be pretty strict and swift payback when it comes to using frequencies you shouldn't, as they're used for other stuff and easily seen when other traffic appears.

If it's a station (client) then it's unlikely, as long as your APs are compliant.

With some chipsets it can end up being entirely ass-backwards - if you use an Intel WiFi chipset, a nearby AP can broadcast the wrong region and cripple your connectivity.

Outdated regulatory databases and firmware efforts by vendors have generally made both illegal and legal usage beyond ch 1-12 at 2.4GHz rather difficult.

It's wifi. The client and the base have to negotiate a channel they both can see. If the AP is compliant for it's region than you can assume the client will have to be as well.

BTW, I'm someone that use to by US region coded 802.11b wifi devices to get the 13th channel. Except for exploring, it was rarely useful since none of my other devices could connect on it.

TV is a client. If I remember correctly, it shouldn't transmit anything (unless connected) other than probe requests during active scanning.

Which could still be illegal, but I don't think anyone will realistically investigate a low-power device sending a few packets occasionally.

You mean that this helicopter hovering about my home is looking out for me?

This is about a WiFi client - on WiFi networks the AP station chooses frequency and manufacturers/driver writers fuck up legal frequency lists and regulatory codes all the time.