The article on the twindx site was pulled, but I managed to grab the google cache
Just the other day I wrote about my research into what makes the FON-supplied WRT54GL routers tick. Now I've got mine at home, set up and with FON's firmware removed. I haven't registered it with FON - if they come crying to me about having taken delivery of the router but not setting it up for FON, then I'll back it up, stick on their firmware, register and then go back to OpenWRT with my 'heartbeat' being faked by a cron job.
Here's what I've done, in the order that I've done it. I absolutely have to disclaim here - you're on your own if you do this, your milage may vary, Google is your friend, etc. If you ah heck things up you can generally recover, but be aware - it is possible to ah heck things up. I'm only talking from my experience.
First of all, I downloaded the most recent relevent OpenWRT firmware. This is available here at present, but if you're reading this in a few months time, take the time to explore the website first. The firmware you want is named openwrt-wrt54gs_v4-jffs2 at present, but expect the version 4 to become v5. Update: I was misreading the filename, v4 is referring to the hardware model, not firmware revision.
Next I hooked up my laptop to the router by cable, and powered up the router without having it connected to my DSL. After a moment or two I could get an IP address from it, and when I opened Firefox it opened straight into the FON frontend - which betrayed its origins by having OpenWRT splashed across the screen =) It wanted me to set a password, which I did, before I could get in to tinker. (The username to go with this is 'root'). I seem to recall, first boot up, it refused to let me set a password because the filesystem had been mounted read-only. When I reset, all was well - I think this is part of the normal behaviour straight after writing the firmware because exactly the same thing happened when I booted the vanilla OpenWRT for the first time.
Once this had been done, I went straight back into the web frontend and went to the section that lets you update your firmware. I can't remember what the tabs are - I'm typing this at work, and I haven't set up incoming HTTP access to the router so I can't check - but I found it quite quickly. Now, remember - FON's firmware is a patched version of OpenWRT, so it takes the same firmware files very happily. I uploaded thie firmware mentioned above, and... it just worked. Just like that. The router rebooted, I did "ipconfig /renew" in the Windows command prompt to get a new IP address from it, and I could see the same frontend, no longer in FON's orange and yellow but in the calmer blue hue of OpenWRT's default setup. The IP address it had given itself had gone from 192.168.10.1 to .1.1 and the password had gone.
Things to note:
1. Uploading new firmware from a PC is better by cable than by wireless. It makes more sense. It's probably get CRC checks and all sorts to make sure that it doesn't try and apply a corrupt firmware file, but you can't be sure without going through manuals. Be on the safe side and hook up with a Cat5.
2. I didn't have it hooked up to my DSL because I wanted to have full control over what was going to be going on, and I'd already seen the heartbeat.php thing mentioned before.
3. This router hasn't been registered with the FON network.
If you have registered with the FON network, apparently you'll find that, if you try and access the web frontend (probably 192.168.10.1) over your wifi connection, it'll fail. Wisely they decided that if you're going to run an insecure network (such as FON is) it might be a good idea to prevent access to the panel. You have no choice - you need to hook up with a patch cable. You should still be able to flash to a vanilla OpenWRT firmware though. They may also notice that you've gone missing from the FON network if you do this, in which case you'd need a script to run to periodically ping the heartbeat URL mentioned last time.
Okay - that's all I can offer in the way of information for now. Be aware that you will need to have a knowledge of Linux to get anything remotely useful out of this - if you don't, you might want to consider flashing the router with official Linksys firmware instead.