kismet solution for c1000 and c3100
install-all to internal drive:
  * libstdc6_1.2.2_arm.ipk
  * libpcap - [libpcap0_0.7.2_arm.ipk
  * kismet3 - [kismet_3.0.1c-20031228_arm.ipk
  * kismet-qt - [kismet-qt_2.0.0_arm.ipk
hold down the kismet icon in applications and checkmark "start with root" and remove checkmark on "magnify".
su and use zeditor or your favorite editing program and change variables in /usr/local/etc/kismet.conf
change with zeditor or your favorite as su or root and change the variables in
the code looks like this combined
_____________________________________________________________
# source=cisco,eth0,ciscosource
# Other common source configs:
# source=prism2,wlan0,prism2source
# source=prism2_avs,wlan0,newprism2source
source=orinoco,eth0,orinocosource
to
this
# source=cisco,eth0,ciscosource
# Other common source configs:
source=prism2,wlan0,prism2source
# source=prism2_avs,wlan0,newprism2source
# source=orinoco,eth0,orinocosource
_____________________________________________________________
look deep but you will find it.
Once that is done create a network profile as follows:
_____________________________________________________________
   Account
    Name: kismet
   Config
    Non-Spec ESS-ID: "ANY" (unticked)
    ESS-ID: any
    Network Type: 802.11 Ad-Hoc
   WEP
    Key Type: Disabled
   PPoE
    Use PPoE Authentication (unticked)
   WEB Auth
    Use WEB Authentication (unticked)
   TCP/IP
    Obtain TCP/IP information Automatically (unticked)
    IP Address: 10.1.0.2
    Subnet Mask: 255.0.0.0
    Gateway: 10.1.0.1
   DNS
    Auto-detect name servers (unticked)
    Primary DNS: 10.1.0.1
    Secondary DNS:
    Default domain: (leave empty)
   Proxy
    No proxy
_____________________________________________________________
now start up kismet and it will lock up.....wait no more than probably a minute and it will say that it cannot connect to server. click on quit and then hit config tab in kismet. change scheme to socket and click on save and close kismet. click the icon connection manager in the taskbar and connect to kismet. Once it says "connected", go to applications tab and start up kismet. Give it a few seconds and you have your results.
after all that mess, all you need to to from now on is...
Connect to this network which is kismet and then start Kismet. that is all.
i found a problem though, if you cannot connect after to your regular wifi, just eject cf wifi and reinsert it. I dont know what causes this problem. or reboot as well if it fails.
Tutorial done by cresho@earthlink.net
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
i could not locate all thes ipks for the older Kismet so i tried the 2005-01-R1 along this instruction and with slight modifications i was able to make it work.
What i installed:
1. libstdc6 1.2.2 from hluc (is found under [a href=\"http://www.users.on.net/~hluc/myZaurus/stuff/]http://www.users.on.net/~hluc/myZaurus/stuff/[/url] (links on his page go wrong (edit - no more, just find the links on his page /edit) (2nd edit /stuff/ not /Stuff /edit))
2. libstdc++2.10-glibc2.20 from cacko feed (bryandeluca)
3. libpcap0.8 version 0.8.3-1 also cacko, difficult to locate the right one
4. kismet 2005-01-R1-1 also ...
5. kismet-qt also ....
only new thing i did was create a symlink in /home/root/usr/lib and /home/QtPalmtop/lib creating libpcap.so.1 pointing to libpcap.so.0.8
the kismet.conf is now located under /home/QtPalmtop/etc/kismet and the entry for my DLink 660W had to be:
source=wlanng,wlan0,Wireless - there is no more explicit prism2 driver support under this newer kismet, the prism cards are supported under wlanng.
all other same as cresho wrote.
i have a working textmode kismet (has to be started from terminal/qkonsole after a su, icon no go).
the qtkismet is fine-just make it run as root.
regards
George
P.S. excuse the long quote, i think this way the whole instruction stays together.
