digininja

Here is a link to the karma framework, just download it and unpack it to a directory. It doesn't like the standard debian dhcp server, all machines I've ran it on use this version http://www.isc.org/sw/dhcp/ . You also need the patched madwifi drivers, either grab the patches or, if you've got an eee then I've got the full source code, and install it then reboot. download karma

is your laptop set up to auto connect to APs?

Jasager doesn't broadcast ssids, it listens for probe requests and replies to them. Without having to rewatch 412, are you talking about the windows list of ssids or ones shown in the Jasager interface?

It shouldn't find your laptop, your laptop should find Jasager. Give us more to work on to help diagnose.

If you are prepared to do a bit of coding then you can get Jasager running on a laptop but you need to be careful as the web interface needs access to the iw and if commands so it either needs to be running as root, have sudo access or have them setuid to root. I've deliberately not released a version for that because I've got a plan for a slightly different version of Jasager which will run on laptops. I've no idea when I'll get round to building it so don't hold your breath. Someone else asked me for a copy of karma and I'll try to sort that out this weekend. To install it on any system you install patched madwifi drivers then drop the framework in a directory. There are a couple of config files need setting up but it almost works out the box.

Darren has his setup to use wireless to do the connection sharing, if you wanted to leave it somewhere you could use this as an option, particularly if the target has a starbucks close to their office. This is one of the advantages of the fon, you can leave it places you wouldn't want to leave a laptop.

if by transparent browsing you mean that a user can directly access the net through the laptop then this is exactly what Jasager offers. when set up correctly it acts as an AP and routes all traffic through itself and any other machines you want in the middle then out to the net.

yes

You've found it all. The error you report is generated by the portscan script. That is sym-linked to the rc.dhcp directory in a default install, that is why it is being called. It may be that the script is trying to run slightly faster than the dhcp server is actually giving out the ip address, even though it is sending to the log that it has issued the address. To debug this, delete the S01portscan symlink in /karma/etc/rc.dhcp and create a symlink from ../../scripts/echo.rb to S01echo . This will then trigger the echo script when a dhcp address is given which will then display the info passed to it. Have a look at the ip field and see what it says.

I haven't got round to looking at airbase yet but I know I should. I'll try to have a look at it and if it will help I'll try to incorporate it.

How long did you leave it to restart, it can take some time to parse the scripts directory and create the config files.

That error message is when you do a port scan and the device doesn't have an ip address yet. Are you manually running a portscan on the clients or have you done a symlink between the portscan module and the rc.assoc directory?

It does take quite a while to start up, it has to go through the scripts directory and parse the xml to create files. You probably won't notice the time on system start up as it looks like just part of the normal boot time.

Not seen either of the problems. I did have an issue with dhcp when I first setup my second fon but a bit of fiddling and that started working fine. As for the web interface, someone reported it playing up in IE but again I couldn't reproduce it. If you can get anything that is definitely reproducible then I'll happily look at fixing it, even if it does mean starting up windows.

I think it is the level at which the probe responses are done that is the issue. Madwifi does it in software, I think that broadcom does it in the firmware. I could be completely wrong with this as I've not any any reason to look too deeply into other chipsets. If you have a go at porting it and get anywhere let us know.

Flashing for me on a Fon+ took the best part of an hour, if I hadn't done it before on the original Fon I would have given up but I just left it and carried on and finally it finished. Best advice, be patient. I've not yet managed to get it bad enough that I can't get the redboot on the Fon or Fon+, once you are there you can always (I think) recover to some working state

Jasager doesn't have an ssid set so if you are seeing beacons for openwrt then something isn't setup right. The idea is that Jasager stays quiet until it hears a shout then it answers.

It has already been written up by rob in in this post. If you want to know how to do it in redboot, I followed the instructions on the gargoyle site but make sure you use gargoyle rather than openwrt in the load steps.

Nothing is stopping you, go for it. I've never installed ddwrt so I don't know what you'd need to do, I'm not even sure if it is binary compatible with openwrt. If it is then you could take the tarballs, extract them on your pc then work out where to put them on the ddwrt. In the end, it is all linux and my stuff is just an application that sits on top of it so it should run fine.

I regularly have this when trying to install packages. I think it is caused by filling an area of memory/disk that is write only. This is why I provide both tarball and package as I regularly have to install stuff by untar'ing the package, working out what is going on, then installing it by hand. If you want to go to v2 it should work with what you installed, I install at least 2 other packages (vim and its dependency) and other people have had it working with that list. Maybe it is the order they are installed, maybe it needs a reboot at a certain stage, I don't know. Best option, with v1.2 installed, install the dependencies then grab the tarball and un-tar it to the root of the fon then reboot it. That should give you v2. Any problems, or if you do try again and get it working, let me know.

I've checked the file on the site and it is fine. To help you check it at your end I've added the md5s of all the files to the download page.

If you only followed Darrens instructions you won't have. To check for sure run ipkg list_installed and look for them.

This forum is for discussion of Jasager related issues and you've drifted off topic quite a bit here. Try asking again in one of the more generic forums.

Sorted it, thanks.

I've sorted out the upgrade issues and put 2.1 up. Something I realised I'd documented in my install notes but not actually implemented is the dependency on the two ruby packages ruby-rexml and ruby-core. If you haven't got these installed, grab them from http://downloads.openwrt.org/kamikaze/packages/mips/ and install them with ipkg Functionality hasn't changes so for anyone who has v2 working, don't bother upgrading, you won't get anything better.