Wellenreiter And Kismet On Cacko, small tutorial Options

[Tomoe]

This is a small instructional I slapped up couple minutes ago for TsingTao when he asked me how did I get these two running; pardon the grammar mistakes and such, English is not my native language and it's rather late here.

-----

About Wellenreiter, I installed the files from the alternative cacko feed ( http://web.mol.ru/~zaurus/feed/ - libpcap, libopie1, libopie2, wellenreiter - install them in this order), at first I got some grays too because it didn't work, I clicked on Autodetect in settings, then checked if the driver name is correct, and there it was, hostap, and everything should work, but it didn't.
The thing was, after 20-some tries without any success I noticed the 'Name' selection box in Wellenreiter configuration, it defaults to wifi0 and it should be wlan0, I changed that and voila! it works. So, first you click on Autodetect, and then switch from wifi0 to wlan0 in Interface box.

About kismet, it is a bit more work. First, make sure you installed libpcap, kismet and kismet-qt from the cacko feed, then:
In the network app create a new service, call it anything you wish, on the config tab untick the 'Non-Spec ESS-ID' and enter 'any' as SSID. Switch the network type from Infrastructure to Ad-hoc and on the TCP/IP tab untick the box for automatic address assignment, then enter this: IP – 10.1.0.2 Mask - 255.0.0.0 Gateway 10.1.0.1
Also, untick the 'Autodetect nameservers' on the DNS tab and enter 10.1.0.1 in the first box.
Now, open /opt/QtPalmtop/etc/kismet/kismet.conf with your favourite editor =) and then find the 'source=blablabla' line (almost on the beginning). Change it to match your card (in my case it looks like this:
source=hostap,wlan0,hostap
first one is the driver name (write it according to your card or according to what Wellenreiter had autodetected) and the second one is the interface name, be sure to change the interface name to wlan0 since the default is 'eth0', not much sense in leaving that right? The third part is name and you can put anything.
Now, scroll down, somewhere at 1/3 of the file there's a line 'gps=true', comment it down (put # in front of it). Save the file.

Connect to the network (dummy network) we configured on the beginning, then open a terminal (don't run the icon for kismet, fails for me too) and enter 'sudo kismet'. It should work. If it acts weird, try entering these two lines:
cardctl eject
cardctl insert
before starting up the network and running 'sudo kismet' (try the same with Wellenreiter if it fails too).


BTW, anyone knows how to get Kismet to display colors, AND the full lines (frames)? When I put TERM=vt100, color is not supported, when I put TERM=linux, lines do now show up correctly, and I'm not too sure if there's color, either.

[GadgetGuy]

I just installed kismet (with the required libraries), and it worked after changing the config file ( source=hostap,wlan0,Wireless).

There was no need to create any network profile, and there is no need to connect to any network.

I just launch kismet and it works.

[rebski]

Thanks for posting this, Kismet is just too hard (though it worked perfectly on my 5500) however Wellenreiter is fab.

Good result!

[maslovsky]

I will update kismet package to reflect wireless interface name in 1.23
I will also include most recent kismet version

[Tomoe]

I just installed kismet (with the required libraries), and it worked after changing the config file ( source=hostap,wlan0,Wireless).

There was no need to create any network profile, and there is no need to connect to any network.

I just launch kismet and it works.

It doesn't work for me like that, tho.

[Tomoe]

Thanks for posting this, Kismet is just too hard (though it worked perfectly on my 5500) however Wellenreiter is fab.

Good result!

You mean you still didn't manage to get Kismet working? If yes, what's the problem?

[rebski]

No, still not working. It also seemed to require the installation of libstdc++2.10-glibc2.2_1-2.95.4-16_arm.ipk though.

Once that was installed the ‘sudo kismet’ command on Terminal then came to the end of its processes but with “Can’t start server”.

I shall wait now for Maslovsky to work his magic.

Your advice on Wellenreiter is a total success and there could well be something that I am doing wrong with Kismet..

Just a curious footnote, my Symbol card detects 2 local networks but the Linksys finds 3. Why that should be, I wonder? If there was to be any discrepancy in performance I would have assumed the Symbol to be the superior card.

[GadgetGuy]

I just installed kismet (with the required libraries), and it worked after changing the config file ( source=hostap,wlan0,Wireless).

There was no need to create any network profile, and there is no need to connect to any network.

I just launch kismet and it works.

It doesn't work for me like that, tho.

I have tried this with two cards: an Ambicom and a Symbol card - with my C3100.

In both cases it worked fine. What wifi card do you use? Which Z?

[drakecoldwinter]

for me Wereiller work very well, but kismet says error opening terminal: vt100.
killing server...

and then stops... :'(

[Tomoe]

for me Wereiller work very well, but kismet says error opening terminal: vt100.
killing server...

and then stops... :'(

Tomoe to the rescue!

Actually, I was dealing with this (among others) problem for the last half an hour, just finished troubleshooting.
Try entering these commands in shell:

sudo kismet_server

(now open a second shell tab and enter this there:)

export TERMINFO=/usr/share/terminfo
kismet_client

Let me know if it works this way.

[Ragnorok]

...snip...
About Wellenreiter, I installed the files from the alternative cacko feed ( http://web.mol.ru/~zaurus/feed/ - libpcap, libopie1, libopie2, wellenreiter - install them in this order), at first I got some grays too because it didn't work, I clicked on Autodetect in settings, then checked if the driver name is correct, and there it was, hostap, and everything should work, but it didn't.
The thing was, after 20-some tries without any success I noticed the 'Name' selection box in Wellenreiter configuration, it defaults to wifi0 and it should be wlan0, I changed that and voila! it works. So, first you click on Autodetect, and then switch from wifi0 to wlan0 in Interface box.
...snip...

- I did this ... the lastest on the Cacko feed has wlan0 already. (grin) After autodetect I had to shut down and relaunch Wellenreiter, but then it scans just fine as you please.
- But it never finds anything. There are two networks visible from my house, and Kismet finds them both. Wellenreiter just scans and scans and comes up with nothing. Ideas?...

[Ragnorok]

...snip...
Now, open /opt/QtPalmtop/etc/kismet/kismet.conf with your favourite editor =)
...snip...

- I installed Kismet from the v1.23 feed last night, and it looks for the kismet.conf file at /usr/local/etc/kismet.conf, for some reason. Don't recall it doing that in the past, but a soft link fixes it straight away. Gotta love Linux! (wolfish grin)
- This version has handy enablehost settings for hostap and orinico already. Nice! But it won't work with my Symbol card unless I leave hostap_source in force. Says "FATAL: channel get ioctl failed 19:no such device" if I enable orinoco_14. Weird.
- Wifi never finishes connecting with the recommended setup. The little lightning bolt is on the connection applet, and it just flashes balefully at me. The card looks dead ... no blinky lights or anything. Eject and reseat. Ding!
- Now it says "FATAL: Failed to set Channel 6 110:Connection timed out". Additionally, my WiFi link says "No Connection detected." and it disconnected me.
- If I eject and reseat the card, then change back to orinono_source, I get "FATAL: Could not find 'monitor' private ioctl ... <blah><blah>" followed by "No Connection detected" and a disconnect. Looks like I need to check a lib ... though I've never had this particular problem when installing Kismet from the Cacko feed before. (shrug)

- I've always had a ton of trouble getting Kismet to work, but once it works, it's a very nice tool. Wellenreither has always been just the opposite ... it's very simple to configure, but it rarely finds anything. (bemused grin)

- Just some ramblings from the peanut gallery on this cloudy afternoon...

[drakecoldwinter]

Kismet working Tomoe, I send you all my gratitudes

[drakecoldwinter]

on a side note, now that we have wereiller and kismet working how about a link to step by step cracking tutorial ?
I understand the theory, I use kismet and were to find networks and get their MAC adresses, computers connected, etc, then I use aircrack tools to provoke very high wifi trafic and force the AP to send identification keys to his clients, then I grab as much of those packets as I can and then I try to figure out the WEP key out of those packets. Then, the theory is very okay, but then I know nothing of how to use airodump, aireplay and I don't know what else... I saw that wereill can dump those packets, but then I played around and my zaurus got a full memory trouble... :'( I guess I will need to do a big ram swapfile for wereiller and kismet... anyway, the point is a link to a tutorial would be fine. Also I understand that you are getting your hands full with zdict, kismet, wereiller kioku dojo (I hope you port this one, it gives a japanese message error, and my japanese is low level) anyway, you don't have the time to write tutorials with is very understandable, so a link would be nice. Also it would be nice a tutorial section on the forums, to put all tutorials and links to tutorials together in the same place.

In the end thanks a lot for sharing the knowledge you posses, without you we would not even have kismet and wereiller and zdict and more

[Tomoe]

In the end thanks a lot for sharing the knowledge you posses, without you we would not even have kismet and wereiller and zdict and more

I don't possess any factual knowledge, I'm just a stuborn mule who doesn't give up and is good at debugging from all the years of Commodore and IBM PC fixing. Praises should go to people who invest a lot of their time for the benefit of others, like maslovsky and sash.