digininja

I wish I could solder, a Fon with lots of storage seems like a really nice thing to have.

You could get one with wifi then use ics off it to connect through, if you have the fon connect to it periodically then you wouldn't loose much AP connectivity. I don't know the price of phones with wifi but I bet they are coming down in price all the time. The other option is one of the new Fons with the built in usb port, with that you could easily either tether a cheap phone or external storage. Give the Fon a second AP which you can connect to and use to suck off all the data whenever you are passing. Depends on how much you want to process and how busy you network is, but I agree, storage is possibly more of a problem than cpu but more of both wouldn't hurt.

Your idea is basically what I see as a white hat pen testing tool. I like the idea of the phone for data exfiltration, you would have to work out how much data you could store before you could send it out. An alternative is to have two Fons back to back joined on the wired side. The second would be in client mode connected to a wifi network and could send data out through that. Having two devices also doubles your potential processing power so you could use the main AP to do some work then pass the rest off to the second. However if you are sending data out you could probably leave most processing to the offline recipient or, if you have the network connection speed, have that do the processing then send back commands. I'm already working on running inline packet capture and data matching on traffic as it flows through the device and I'll be having a look at getting mdk or something similar working when I get chance.

Ye, some client software won't attach to a non-secure if it expects a secure one, some just fall back to unencrypted. Glad it is fixed

Got a solution for this. Working on integrating it soon, will release new stuff when I get chance.

If the install script doesn't finish then it probably doesn't get registered in the installed package list. By killing power you stopped it from finishing. I'll look. Read my install notes on how to fix the module problem.

That is odd, I'll have another look through what is ran in the post install script, it may be something in there rather than in the actual Jasager start up script.

Weird, something must be locking it open. If anyone else has an upgrade to do and fancies trying to debug it go for it, in the few times I tried it I didn't reproduce it.

I've found another bug with the auto run scripts. When I moved the log file from /karma to /tmp I missed one reference to it in /karma/bin/logwatch . There is a line that starts time_ssid= In the middle it references status.log, the file should be /tmp/status.log. I also found another possible bug in here, if Jasager has been restarted since a client connected the time_ssid line won't find any reference to the association in the log file so the ssid field will be blank. This causes problems because it is supposed to be the second parameter passed to the scripts, as it is blank all the other parameters move down one position and the IP address becomes the second parameter rather than the third. To fix this add the following lines under the ssid= line if [[ "$ssid" == "" ]] then ssid="Unknown" fi This isn't the best fix as it sets the ssid as "Unknown" which means we can't tell if that is what the user was probing for of if it is the result of this bug. I'll have a think about a better fix. A combination of these problems could have caused the issues some people have seen with the auto port scan complaining about not getting an IP address, it is getting one, just in the wrong place in the argument list. I've got another couple of issues to look at and when I get them sorted I'll put up a new version or give a list of files upgrade for people who don't want to do a full upgrade.

I've just found a bug in the log writing code. I did a port scan then did another dhcp request. The dhcp log entry overwrote most of the port scan entry. I remember seeing this during development but wrote it off to a one off problem caused by what I was working on at the time. I'll investigate it and report back when I have a fix.

Someone asked about getting a dhcp server running on the fon. I haven't got this working through the config files but if you run (assuming your wifi is on 10.1.1.0 subnet) /usr/sbin/dnsmasq -K -F 10.1.1.100,10.1.1.200 you will get a working dhcp server which gives out ip addresses in the range specified.

I didn't check it out that much but from what you've said it is a shame, it looked like such a nice little setup as well.

I've never had one reboot on me. Sounds like a hardware problem. Jasager listens to probe requests and replies with a probe response. It is then up to the client whether they try to associate or not. Some clients remember the MAC address of the AP they want to connect to so won't connect if it isn't right. If the AP it is looking for is supposed to be encrypted then some clients won't associate because Jasager isn't encrypted. Basically, Jasager can't force a client to associate but it will be there if the client wants to.

You should be able to find openwrt and it will respond to any probe requests. Is it that you aren't getting associations or an ip address? The two are distinct processes. A client has to first associate then it can optionally request an ip address through dhcp. If you add the one you want to associate to to the ssid list and you are in black list mode then it won't associate.

Nothing obvious, most people when they have this problem don't have the karma patched drivers but you definitely do. Can you try a different client? Maybe that client is probing but not associating when it gets a probe response.

Have you tried adding Unix to the ssid list and putting it in whitelist mode, see if it actually connects?

Best way to debug is to boot the fon and let Jasager create the interface, then turn karma on. ssh to the device and run logread -f that should tail the syslog file. Try to associate and see what happens, if you are getting white list messages when you are in white list mode then it shows karma is working and Jasager is working to pull stuff from the logs. The question is why black list stuff isn't working. Try this and see what happens.

I use js/ajax to do the auto-refresh, maybe the PSP has js turned off. IE on my windows mobile does.

Just to extend this a little. The madwifi patches also handle ad-hoc mode so they will allow a client who tries to auto connect to an adhoc network to connect to the Fon. Jasager doesn't handle running in adhoc mode but it wouldn't be too hard to get it to.

Just read about this nice little board. http://beagleboard.org/ I like that it integrates with the USRP boards, that could make an interesting mobile project.

Happy to help.

ARGV[0] is the first argument ARGV[1] isn't used ARGV[2] is the ip address The script is triggered by it being sym-linked into the rc.dhcp directory. When a client gets a dhcp address all files in that directory starting with an S are executed in numeric order.

Seeing as I was looking at it I just bought one for 11 AUD. Shipping is approx 5 days so when I get it I'll do some soldering and let you know if it works.

I haven't tried it but I've been told that this works quite well http://fonerahacks.com/index.php/Tutorials...SB-Adapter.html

Karma was never really documented properly and while I've done fixes to the framework most of my changes have been to the madwifi drivers. The whole thing needs a overhaul and documenting. If I ever get a spare week I'll look at it but it won't be in the near future.