Kismet doesn't work on 1.9.2.7 ?

Quote:

---

Originally Posted by albi

Yes, is there anywhere 1,5 MB space on wl500g which will not be destroyed at boot? If not, I will have to look for some usb/hd solution, thats no problem, I just like to know. I checked with df, but this shows me only:
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 2944 2944 0 100% /
Which does not really tell much :)

I did install on my linux computer kismet client and connected to wl500g server, which worked fine. But I saw nothing happen. OK, I need to check this again.


ALBI...

---

no it's ram, when its too full it will cause the router to reboot, but if you don't need it often you could use that..

it works for me, but i don't receive any 'weak' keys from my own WEP128bit secured network.. so i guess my second wireless network is too well secured

Can anybody help me with compiling new version of Kismet? Version compiled for wrt54 doesn't work. Probably monitor mode is not supported by driver any more.

Monitor mode is supported:

Code:

---

[root@wl500g root]$ wl monitor 1
[root@wl500g root]$ tcpdump -i prism0

tcpdump: WARNING: prism0: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on prism0, link-type PRISM_HEADER (802.11 plus Prism header), capture size 68 bytes
18:52:55.793250 [|802.11]
18:52:56.304726 [|802.11]
18:52:56.611817 [|802.11]
18:52:56.714134 [|802.11]
18:52:56.919823 [|802.11]

---

I've copied and run kismet package (http://wiki.wl500g.info/index.php/PackageKismet) on my usb. I too modified kismet.conf in accordance to indications in this web.
This is the output:
[pepe@(none) kismet-2004-04-R1-wrt54]$ ./kismet_server -f ./conf/kismet.conf
Using alternate config file: ./conf/kismet.conf
Suid priv-dropping disabled. This may not be secure.
No specific sources given to be enabled, all will be enabled.
Enabling channel hopping.
Enabling channel splitting.
NOTICE: Disabling channel hopping, no enabled sources are able to change channel.
Source 0 (wrt54gsource): Enabling monitor mode for wrt54g source interface eth2 channel 0...
Source 0 (wrt54gsource): Opening wrt54g source interface eth2...
FATAL: pcap reported netlink type 1 (EN10MB) for eth2. This probably means you're not in RFMON mode
or your drivers are reporting a bad value. Make sure you have the correct drivers and that enterin
g monitor mode succeeded.

is this firmware imcompatible with kismet?

I did not test it yet but I believe there could be an incompatibility between Kismet and the latest Broadcom wl driver. BTW the most current Kismet revision is 2005-01-R1a > http://www.kismetwireless.net/code/k...a-wrt54.tar.gz
You can try it as well.

You need to use separate interface called prism0, not eth2.

Quote:

---

Originally Posted by Technik

I did not test it yet but I believe there could be an incompatibility between Kismet and the latest Broadcom wl driver. BTW the most current Kismet revision is 2005-01-R1a > http://www.kismetwireless.net/code/k...a-wrt54.tar.gz
You can try it as well.

---

2005-01-R1a segfaults... so I guess it does currently not work ;)

"NOTICE: Disabling channel hopping, no enabled sources are able to change channel."

What it is necessary to write in line "source" that kismet has started to switch channels on WL-500GX?
Default line "source=wrt54g,prism0,wireless" obviously does not arrange it.

Ogogon.

No channel switching required. Broadcom stuff do this on it's own, kismet will capture all channels.