Re: Wait a minute!
First, up, I'm not "jamming", I'm sending a perfectly legitimate packet over well-defined frequencies.
"If you make it clear that only your wireless is allowed at your place of business, you'll do without my business."
OK, that's fine. I'll tell the next person in line he can come in now.
" If you _really_ think that you're stopping the students from doing whatever they damn well please by jamming them"
No, I realize that. But it DOES give a bit of breathing space by preventing students from inadvertently connecting to a rogue SSID until I see the alert in my system and shutdown and confiscate the rogue AP. Have you ever had an angry parent piss fire down your back because their Little Johnny connected to another student's rogue SSID and got whacked? Boohoo. I have, and I will use whatever tech capabilities I have available to prevent such a recurrence, legal now or not. For me, THAT's the End of Story.
Look, hey, I know I'm in the minority here. In a general sense, yeah, deauth isn't great and is often used for great evil. But at the same time, I've got a job to do, and part of that job is making sure I'm providing reliable and safe (such as can be) wireless to the students on my campus, and in that case, deauth is a good first line of defense. (well besides education about the dangers of rogue APs, but what 18 year old is going to listen to that lecture?).