Cisco makes the product that does the detection, too. So does Aruba, Motorola, and probably Meru.
The first main use case for the deauth packets is when someone is broadcasting your SSID but they're not actually part of your network. The second use case is when a client that you actually own (corporate laptop) connects to an access point it's not supposed to. And nobody will really mind if you do those.
The use-case doesn't really matter; it's against the regulations for that radio band to interfere with other people's usage. Even if you think they're attempting to commit fraud.
Comments
Cisco makes the product that does the detection, too. So does Aruba, Motorola, and probably Meru.
The first main use case for the deauth packets is when someone is broadcasting your SSID but they're not actually part of your network. The second use case is when a client that you actually own (corporate laptop) connects to an access point it's not supposed to. And nobody will really mind if you do those.
This anti-competitive use case is another matter.
I mind. You can't own an SSID and they are not uniquely set. Just because you have the same SSID as me what gives you the right to deauth my router?
What is the use case for using an SSID that is already taken? Especially in a business or corporate environment.
The use-case doesn't really matter; it's against the regulations for that radio band to interfere with other people's usage. Even if you think they're attempting to commit fraud.
Right about radio but the thread was talking about Cisco sending deauth packets to rouge APs.
... as was I! Just because you consider an AP to be rogue doesn't mean it's legal for you do something about it.
Right! because who decides if it is a rogue AP. In this cause Marriott has decided that all AP's that don't belong to them are rogue.
And I would argue that as it is their building they can decide what is legal and what is not, no?