Slashdot Mirror
Linux Hackers Reclaim the WRT54G
An anonymous reader writes "The world's most ubiquitous wireless access point is free to run Linux again, thanks to a brilliant hack by db90h, aka Jeremy Collake. No soldering is required, as Collake's 'VxWorks Killer' nixes the WRT54G's VxWorks bootloader and installs a normal Broadcom one, allowing Linux to be installed easily. One distribution small enough for the series five WRT54G's 2MB of Flash and 8MB of RAM is the free DD-WRT project's "micro" edition. It lacks some of the fancier Linux router packages, such as nocat and IPv6, but does support PPPoE, and could be more stable than the VxWorks firmware, which seems to have generated mixed reviews." Update: 06/26 22:52 GMT by T : Note that the project's name is DD-WRT, not (as it was mistakenly rendered) WR-DDT. Check out the DD-WRT project's site.
Other manufacturers (nvidia, are you reading this) - this applies for you too. If you support the software I use most (Linux) I will support your hardware.
What's the real point. Sure, the VXWorks version of the WRT54G is a little bit cheaper but, it has less memory, which limits its capabilities. The old Linux capable WRT54G is still available in the form of the WRT54GL so, why would anyone choose this route?
As I think about it, this development may actually hurt the WRT54G Linux crowd. If price is the motivating factor and everyone opts for the slightly cheaper VXWorks version, Cisco will likely discontinue the WRT54GL due to lack of sales leaving the LInux crowd with a less featureful option.
Others have said it, but the reason is that VXWorks has a smaller footprint. The VXWorks versions have half the ram and half the flash space of the other versions.
Linksys/cisco embrace the whole "DIY" crowd and have produced a "WRT54GL" with the full amount of ram and flash so that linux hackers can do their thing. They made it difficult to flash the VXWorks one because too many idiots would try and flash a 4mb image on it and brick it, causing support headaches.
Difference between WRT54G and WAP54G = $20 and a little work. I wanted to set up MythTv for my home. My internet access is in the back room but I watch myth in the front room. Naturally I went with wireless since the wife didn't want the ugly cables. I went to my local electronics store and bought a 54G not thinking it couldn't be a client. I set it up and home and found out I bought the wrong product rather quickly. Knowing that hacks like this exist for anything with a chip I did a little research and found the SVEASoft firmware. Downloaded it from another site (it's open source, thank you Linksys). I upgraded my firmware and on reboot got a blinking red light. That's when I found out about the term brick. After my heart started beating again, I did another search and found a quick tutorial on how to un-brick your system and first step is to try the Linksys exe (worked like a charm, again thanks Linksys). I then found DD-WRT, installed and worked like a charm. I was a little confused that I had to set my clients name as the same as the wireless server to enable the bridge, but after getting that straight everything worked like a charm. Overall, the potential heart attack was not worth $20, but the satisfaction of buying something, finding out it doesn't work and turning to the open source community for the answer, Priceless.
Amazed, am I, at Linksys's continuing to miss the opportunity to sell a fully featured WRT54G themselves. They could have a knockout product out of the box in that price range that would leave the competition scrambling, but persist in sticking to a basic, no frills configuration.
"It's the height of ridiculousness to say for those 9 lines you get hundreds of millions."
Maybe you could check this:
/proc/sys/net/ipv4/ip_conntrack_max
~ # cat
4096
--- Hindsight is 20/20, but walking backwards is not the answer.