digininja

Not sure what you mean, ask again in its own thread and I'll try to help.

The md5 problem will be due to you running or not running ipkg update at some point. ipkg keeps a db of the md5's of the packages it expects to install, my version doesn't match the md5 due to the alterations so it fails. For the problem, it sounds like there is a problem with it creating ath0 in Master mode. Try ssh'ing to the fon and doing an iwconfig ath0 and an ifconfig ath0, see what you get. You should get either an interface in Master mode or nothing. Nothing is ok because Jasager creates it on start up, Master mode is ok because that should work, anything else and you need to destroy it with wlanconfig ath0 destroy then try Jasager again.

LordC - the only thing I can suggest is to get a serial cable and attach that, see what happens when it boots. txx - that is about what I have but for some reason it didn't work for the first few attempts. I ended up with what I thought was the same as I started with but it all working. Who knows, computers are not always the logical things they are supposed to be!

Something I forgot to add, it takes ages for it to come up from a boot, loads longer than a normal fon. Be patient, and when you are about to give up, wait a little longer!

This is the start of a howto on getting stuff working on the Fon+. I'm going to start it here and transfer it to the wiki once it is complete and can be done as a complete walk through. So, here goes... These instructions are based on you using linux with a wired interface named eth1, obviously adapt them if you use a different interface. You need a tftp server running. I actually found this the second hardest thing to get running for some reason, it never seemed to start up when it should do. The best way to install this is to use your distro package manager and to follow any instructions in their wiki or howto guides. Once it is running it should be fine from then on. To start with, grab the redboot.pl script and make sure you have all the dependancies installed, the quick way to test it is it just run it and see if it complains. Grab the following files and put them in your tftp directory: Fonera Firmware - this needs to be renamed openwrt-fonera.image loader.bin Power down the Fon and attach a network cable between eth1 and the black (LAN) port on the fon. Set eth1 to 192.168.1.254 and start redboot by running ./redboot.pl 192.168.1.1 It should start complaining about network down. Power on the Fon. After a second or two you should get a connection and a redboot prompt. If you haven't had one after 20 seconds you've done something wrong, check ip addresses and connections and try again. At the redboot prompt run the following commands: fis init load -r -b 0x80100000 loader.bin This will grab the file from the tftp server. If it doesn't work then check the server. Test it by trying to download a file on your local machine. fis create loader This will take a while (possibly 10 mins+) fconfig boot_script_data At this point you'll be given a second prompt, enter fis load loader exec and hit a final return to enter a blank line, that should give you a question about updating redboot, hit y and enter. You'll then drop back to a redboot prompt. load -r -b %{FREEMEMLO} openwrt-fonera.image Again, load from tftp server fis create image This one is the biggy, it took over 30 mins on my machine. Have patience , you'll go back to a redboot prompt once it is finished. As Darren says, go eat some fruit (I had cherry pie). After this you'll have a fon flashed with the latest firmware from fonera. This firmware is designed for the next model up from a fon+ so it has a load of extra stuff installed which takes up memory and processor. I'm looking at tidying up these to give a more streamlined device. To access the fon it should be the same as the original Fon, there will be a WPA protected AP called MyPlace with the serial number as the key. Once on, get a dhcp address and you should be able to ssh in over the wireless. The password for the root user is admin. As I said, I've started tidying it up but I've got quite a bit of work. I've published this now so that others can start doing the same, any one gets anything good let me know. The bigest problem I'm having is working out the network setup and how to decouple it all without locking myself out completely. There are a lot of firewall rules built in as well, I'm going to consult with Darren on those as they currently lock you out of wired access. I did manage to get wired access through the WAN port by using the web interface to set the Internet IP address to static on a 192.168.0.0 subnet then connecting it to my lan and accessing it from there, the only problem is that to do it I had to remove one of the firewall rules and I can't find which one it was! A couple of little things I do know, if you do this echo 1 > /etc/config/registered the web interface will show you as registered, and I've ran these two sets of commands to remove unneeded start up scripts and modules: cd /etc/rc.d rm S39usb S50telnet S98usb_led S99pureftpd S99scanner cd /etc/modules.d rm 20-nls-base 20-scsi-core 20-usb-core 30-ppp 30-sound-core 40-scsi-core 50-usb2 60-usb-audio 60-usb-printer 60-usb-serial 60-usb-storage 60-video-core To stop it from trying to call home, edit /bin/thinclient and put an exit statement on the like after KEY=/etc/dropbear/key Looking at what is there, I'm sure that I could easily remove half of it and still have a working system but, as I said earlier, I don't want to screw it up and lock myself out of it completely so I'm going to take it slowly, learn how it works and report back when I know more.

I have ssh on the Fon+ and an up-to-date firmware, unfortunately it is the fonera firmware not kamikaze but it is a lot more up-to-date than the one that comes pre-installed. Turned out not to be too hard in the end, just took a long time to find the right tutorial and even longer trying all the ones that failed because of how long it takes to write the firmware each time. I'm going to sort out packages (installing unneeded and installing needed) tomorrow night then I'll post my how-to. This proves that the fonera people have a sense of humour

I've got a module to let me play with the lights. I'm going to patch it in and release it soon.

USB cards should (theoretically) be able to work through vmware but other cards probably won't. The problem is that if the machine is offering the card to the vm then it has already stripped it down to a basic network interface so the vm can't access any of the low level stuff, such as controlling wifi settings etc. The reason USB ones work is you can get the host OS to pass the device through to be directly controlled by the vm.

I've been doing a lot of work trying to get openwrt installed on the Fon+. Loads of people say that they've done it but there seems to be little proof and no one is actually saying how it was done. So, for now, I'm going to give up on Kamekazi and go back to a fully opened version of the Fonera firmware which is, as far as I know, openwrt 7.06. I've got a source who has given me loads of pointers and does know how to do it so hopefully that will work. For Jasager, as long as I can get ruby and a web server on the device then I can get it working so all should be ok. I was supposed to be doing it tonight but fell asleep in front of Black Adder instead. Will try to look at it tomorrow.

When you first connect to the Jasager website, do you get an option to create the interface? If you do then let it create it. If you get the normal interface, have you turned wifi on with the first option button in the top left panel? To check the interface, ssh to the box and do an iwconfig, that should show one interface in AP (MASTER) mode, if not then something is wrong.

It is the first time but then after that it is a breeze! (but then I'm biased I think I've debugged virtually every part of it at some point)

A non-programming challenge, if you could find some time in my schedule for me to spend more time working on the todo list that would be great :-) Best things you can do are just use it, report bugs/problems/things that are unclear and also anything you'd like to see, then the todo list can grow even longer! Maybe a write up of your experience setting it up, anything that you found hard or any tricks that you found, maybe you bypassed a step or know how to do something better.

The catch_fonera script doesn't work, use redboot.pl instead. I've got to the point of all flashed but no booting of openwrt. I'm trying to find time to work on it.

telnet is a one off, once you've setup a password for root it shuts itself down for security reasons

That would be very impressive! I've been wondering what to do with mine! Tie the buttons to enabling black and white lists, kicking people etc. There would be a legit use of the power connector. If someone gets a cf mod going you could use the card slot at the top. I like it, I just wish I knew enough hardware mods to be able to do it.

If someone wants to send me one I'm sure I can come up with a project for it. Any hardware (or cash) gratefully accepted.

No, you need openwrt.

Jasager should work fine on the fon+. The hard bit at the moment is getting Kamikazi on it, I've got ssh but still with the Fonera firmware on.

Any device that has an atheros chipset and will run openwrt should run Jasager without any problems. No guarantees but from both software and hardware point of view I can't see any issues. I've got a Fon+ sitting waiting to be flashed, once I've done it I'll report if I find anything wrong.

For anyone wanting to try this from linux there is a script called redboot.pl that you start before powering on the Fon and it repeatedly tries telnet connections till it gets one. With the approach above you may need a few attempts to hit it right, if it fails the first time keep trying, you will hopefully get it at some point.

Make sure you are in blacklist mode, add the ssid of the legit AP (openwrt) so that Karma ignores it then start karma. Your alfa may then try to associate with it but it will be rejected. The only problem I can see is the laptop trying so hard to associate with it that it doesn't get chance to associate with the real ap. Have you tried doing a wired link between the laptop and the openwrt? BTW, what are you using for the diagrams? I like them.

I'm linux only so have no experience with ICS. Can you ssh to the fon then access the net from there? My guess is you have routing or DNS problems somewhere.

That sounds about right, I'll grab the package and try it then post a patch.

In my standard install anything on port 1471 is protected by the equivalent of htaccess. The setting for that is in /karma/etc/httpd.conf. Darren adding the step to rename index.html and replace it with mine is to stop the need for adding port 1471 onto the url. The problem may be the redirect that this is doing. Try closing browser down completely (all windows) and then hitting <fon>:1471/ directly, see what happens.

Not quite, the white list is the list of things that it will only reply to, you want to use black list mode and add the ESSID then. That means that the ssid of your WRT will be ignored.