> You don't think triangulation can be that accurate?
Does Cisco's anti-rogue AP tech perform triangulation? Why would it when it isn't designed to limit what people can do in physical spaces?
> You have even less basis for that statement than they had for theirs.
I know how the tech works. I know how the anti-rogue AP tech works. I have plenty of reasons for believing that they're disconnecting APs outside of a physical zone (since it isn't designed to do accomplish that to begin with).
>> If your WiFi network is called SmartCityWiFi and you disconnect MyHotSpot then you're breaking the law
> [citation needed]
Literally the article this entire thread is about... The FCC's fine of Smart City today that we're discussing is the citation. I cannot believe you even asked for that... Wow.
> Literally the article this entire thread is about
As another commenter so politely put it, and received no censure, absolutely wrong. You're trying to make a distinction based on SSIDs, and SSIDs have no legal standing. The string "SSID" doesn't even appear in the FCC's decision. Reasonable people can disagree on whether this was the right decision, and as it happens we do agree. Reasonable people can disagree on which statutes, definitions, etc. apply. However, reasonable people can not claim that the entire thread is about SSIDs. To quote you, "Wow."
That's a strawman, the term "SSID" appearing or not appearing is irrelevant. The distinction is about legal and illegal usage of rogue AP containment. To quote Cisco[0]:
> Rogue AP-connected clients, or rogue ad hoc connected clients, may be contained by sending 802.11 de-authentication packets from local APs. This should be done only after steps have been taken to ensure that the AP is truly a rogue AP, because it is illegal to do this to a legitimate AP in a neighboring WLAN. This is the reason why Cisco removed the automatic rogue AP containment feature from this solution.
You're arguing that it is illegal in all circumstances, Cisco disagrees. The FCC also has not brought a single enforcement action against anyone utilising rogue AP containment the way it was designed, they have only brought it against businesses using it to shut down third party WiFi (that wasn't pretending to belong to the same network).
Speaking of strawmen, I am not arguing that rogue AP containment is always illegal. Nor am I arguing that it's always legal. I believe this is a matter of consent. If you enter a space where wifi hotspots are forbidden, then your proprietor can de-auth you to hell and the FCC should have nothing to say about it. It's not interference any more; it's an agreed-to limitation on use.
Your Cisco quote is a complete non sequitur because you're assuming a very particular definition of "legitimate AP" when none is present or implied by law. A "legitimate AP" is one that is not itself being operated in violation of the law, and a "neighboring WLAN" is one that you do not own or have consent to manage. With correct or reasonable definitions, that quote doesn't support your position at all.
Does Cisco's anti-rogue AP tech perform triangulation? Why would it when it isn't designed to limit what people can do in physical spaces?
> You have even less basis for that statement than they had for theirs.
I know how the tech works. I know how the anti-rogue AP tech works. I have plenty of reasons for believing that they're disconnecting APs outside of a physical zone (since it isn't designed to do accomplish that to begin with).
>> If your WiFi network is called SmartCityWiFi and you disconnect MyHotSpot then you're breaking the law
> [citation needed]
Literally the article this entire thread is about... The FCC's fine of Smart City today that we're discussing is the citation. I cannot believe you even asked for that... Wow.