next »

[Malacoda]

Hi All!
so my XO came and Ive had a few days to play with it. Overall I'm quite pleased,the Opera browser is fantastic, Nmap works out of the box, tcpdump came installed, and even metasploit seems to work happily on it!
I'm even working on setting it up as a rogue AP via a few tiny shell scripts!
The only problem I can't seem to work out is Kismet.  It installs fine by Yum, but I don't know what to put into the "sources=" line in the .conf file.  The XO uses a Marvell Libertas chipset, which doesn't seem to be supported  by kismet.  I did come across an article from a guy who tore into and recompiled the drivers to suit his needs, but he did it on a bsd box so I'm not sure it applies and I don't know enough about device drivers to be comfortable doing that. =/
Any and all help or advice is appreciated!
Thanks!

[falter]

I started working on getting kismet working last night. I've hacked around for a couple hours, and got kismet to putting the interface in monitor mode, in addition to the gui coming up and it seeing networks.

I'm currently working on:
1. Having kismet put the interface into monitor mode with little/no hard-coding. The libertas driver has a funny way of going into monitor mode by echoing a string into a /sys file, which creates an rtap interface. I haven't seen how to figure out what the interface name is, aside from assuming that it is rtap0. Looking at the libertas-dev mailing list, it looks like they've recognized that this is a weird way to do things, but I don't know that there's been any significant work toward making it less weird.

2. Channel-hopping - I think this is just me not telling kismet how to do its job.

3. Getting it to turn monitor mode off properly. I think this has been mentioned in the libertas-dev mailing list, but the system/driver can get a bit wiggy if something tries to do something to eth0 whilst rtap0 is hanging around. This goes back to #1 on my list, in that they thought that it was important that eth0 still operate normally while rtap0 can be used to suck down packets. Turns out it makes the driver unstable. A few times, my command line prompt would hang if I tried to do an "ifconfig" after running kismet. I think this is as simple as cleanly resetting things to the way they were, prior to throwing things into monitoring mode.

Like I said, I'm still working on it. I'm going to play around with it a bit more, this weekend. Coding with the XO's keyboard is a little tough; things will go faster when I manage to get up off my duff, and plug a keyboard into it

When I've got something that I think would be usable to others, I'll post the patches to kismet, and what needs to be done in order to get it going.

~falter

[ianw]

any updates about kismet on xo from you falter? thanks in advance.

[grantbow]

More discussion at http://wiki.laptop.org/go/Wireless_network_hacking