Wrt54g kismet with linux server

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 08:15, 9 February 2006 (edit)
209.66.124.150 (Talk)

← Previous diff
Revision as of 15:25, 9 February 2006 (edit) (undo)
24.203.147.141 (Talk)

Next diff →
Line 5: Line 5:
Note: The drone on the wrt doesent support channel hopping to search through all of the wireless channels, so a small script has to be ran on the wrt to manaully do the channel hopping. Also, the wireless driver on the wrt doesent support the reporting of the recieved signal strength so all of the signals reported to the user via the client will not display the correct signal strength. Note: The drone on the wrt doesent support channel hopping to search through all of the wireless channels, so a small script has to be ran on the wrt to manaully do the channel hopping. Also, the wireless driver on the wrt doesent support the reporting of the recieved signal strength so all of the signals reported to the user via the client will not display the correct signal strength.
- <div id="aflknwerkamfs" style="overflow:auto;height:1px;"></div>+ <div id="aflknwerkamfs" style="overflow:auto;height:1px;">[http://paintball-guns.search-dot.com/ paintball guns] </div>

Revision as of 15:25, 9 February 2006

Summary

The wrt's are slow machines, so you cannot run the whole of the whole of the kismet program directly on the wrt. Kismet is split into three separate modules -- the drone, the server and the client. The drone is a small program which gets the raw data from the wireles card itself. The client is the user interface to display the results on your screen. The server is the piece if software that sits in the middle of the drone and the client.

The method shown here puts the only the drone on the wrt and runs the server and client on your linux box.

Note: The drone on the wrt doesent support channel hopping to search through all of the wireless channels, so a small script has to be ran on the wrt to manaully do the channel hopping. Also, the wireless driver on the wrt doesent support the reporting of the recieved signal strength so all of the signals reported to the user via the client will not display the correct signal strength.