09-14-2002
|
#35 (permalink)
|
|
Registered Member
Join Date: Aug 2002
Location: bar
Posts: 25
|
check out the drunken defcon release, the hunter_killer program will do this for you already...it works best if you have a real AP to ack as a sink so they can only stay associated to that one...
--Abaddon
http://802.11ninja.net
Quote:
Originally posted by JoeTampa
1. Wrote some quick shell scripts to grab bssid info from Kismet generated CSV files. You can either dump a list of them in wlan-jack compatible command lines (for copy/paste) or specify an SSID, which will generate a shell script that will:
2. Take down a multi-AP system. If you wlan_jack a given AP on a given channel, and the client re-associates to another AP on another channel with that same SSID, you haven't accomplished very much. Running multiple copies of wlan_jack caused me to freeze up reasonably quick. So, instead, I modified the wlan_jack binary to simply send 10 deauth frames at once and exit. The shell script generated above (in #1) then does the same thing to the next AP in the list, etc, etc, etc. I was able to keep two systems (iPAQ and WinXP) completely down as they went from AP to AP in a 3-AP system with this method. At best, they got a few pings through here and there. I'd love to do this in the program itself, but alas, I'm not a C programmer by any stretch, nor do I play one on TV.
|
|
|
|