Slashdot Mirror
Linux Distro For Linksys WRT54G
scubacuda writes "Here is a tiny Linux distro for the Linksys wrt54g (d/l the distro here). In just a few seconds, you can give your access point's ramdisk syslog, telnetd, httpd (with cgi-bin support), vi, snort, mount, insmod, rmmod, top, grep, etc."
Interesting -- "The script installs strictly to the ram disk of the box. No permanent changes are made. If you mess something up, power-cycle it."
does it still function as an AP properly?
yeah i was looking and i hit refresh and his counter jumped about 200 hits in a couple seconds so heres the article in case slashdot kills another site:
/var/modules/ in the following order : sunrpc.o, lockd.o, nfs.o then mount your disk.
/var/bin/snort -c /var/etc/snort.conf &
/var/log/snort
Jim Buzbee
September 05 2003
Mini wrt54g distribution Version 0.1
This is a mini Linux distribution for the Linksys wrt54g. In about 20 seconds, you can install a small set of Linux tools to your access point's ramdisk.
Upon completion of the installation, you will have a system with basic tools such as syslog, telnetd, httpd (with cgi-bin support), vi, snort, mount, insmod, rmmod, top, grep, etc.
To install, modify the script wrt54g.sh for your ip address and password. By default the script uses Java to move files to the wrt54g. If you would prefer wget, uncomment the wget lines in the script. I had a problem with older version of wget translating escaped characters before passing the URL on to the server. Your mileage may vary.
The distribution has been tested on firmware version v1.30.7, Jul. 8, 2003. The installation has been tested on Linux and OSX
The script installs strictly to the ram disk of the box. No permanent changes are made. If you mess something up, power-cycle it.
Upon successful execution of the script, you will be able to telnet to your box and start exploring its capabilities. Note that there is no login prompt, you telnet directly in as root. Be careful.
An alternate web server is installed on port 8000 of the box.
The nfs drivers are not loaded by default If you would like to mount a nfs disk, insmod the drivers from
To run snort, execute the following command on the box :
The snort configuration file should be changed for your network configuration and needs. Snort logs will be written to
If you wish to change the files sent to the box, untar distro.tar and add or subtract files. Normally you should not run the install script more than once for a power-cycle of the box. i.e. if you want to run the install again, reset the wrt54g first.
I have attempted to limit all changes to the ram disk, but there are no guarantees that you will not damage your unit by using these tools.
Download the distribution
Visit my wrt54g snort page
Thanks to Ross Jordan, C. J. Collier, Ben Grech and others who did the heavy lifting in figuring out how to get new code on the box
Jim Buzbee jbuzbee@nyx.net
consolevision roxors!
For us that buying a linksys router is even more preferable. For a personal user to any business criteria the advantage over having full source to this hardware is incredible. Certainly its going to ensure that they stay high on our prefered supplier list provising we can access the boxes and code. incidentally we install WiFi in Public spots for the UK which is being kinda slow to take this up.
And thats why Firecrackers and kittens don't mix.
Why not SSHD? Nobody in his right mind uses telnet nowadays.
http://blog.astyran.sg
None of them support Rendezous (AKA zeroconf), at least not on the level of Apple's airport base stations. That's a hack I'd really like to see.
---If you can't trust a nerd, who can you trust?
OK, this Linksys has only been out for like a few weeks or something, and they've got a linux distro for it... Yet my Toastmaster 5000xdr Quad-port (with FG-200R bagel attachment) STILL isn't supported!
I mean, the linksys probably works fine out-of-box... But my Toastmaster STILL can't check with my Mr.Refrigeration Model XII to see if I'm out of butter and order more online. Sheesh, technology SUCKS!
I was going to post "But Does it RUN LINUX!?" but then I RTFA. Grr....
Could this be used to establish ssh tunneling from clients to the AP? That would, in my eyes, be far preferable to the somewhat lacking link security that 802.11 offers today.
Trust the Computer. The Computer is your friend.
And emacs takes up 95% of those distros that come with it.
//ville
The "ssh tunnels are very bad performance" statement may be elaborated a bit more on this page titled "Why TCP Over TCP Is A Bad Idea".
(Full Disclosure: I designed part of OpenSSH's tunnelling subsystem.)
TCP over TCP has issues when both stacks attempt to respond to the same error conditions. This happens very commonly with PPP over SSH. However, TCP port forwards in OpenSSH actually terminate at the daemon, which extracts the payloads, repacks them into completely independent streams, and sends them on their way.
In other words, an error condition on the routerexternal_site link doesn't show up on the clientrouter link.
OpenSSH tunnels have surprisingly high performance (it certainly beats most proxy implementation hands down). Easy to set up, too: Simply SSH into your host of choice with the -D option(say, ssh -D1080 user@host), set the SOCKS4 proxy in your application to 127.0.0.1:1080, and you're done. It's really quite simple.
--Dan