Linux Distro For Linksys WRT54G 227
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 (Score:5, Insightful)
Well this means... (Score:5, Insightful)
Re:That's cool. (Score:4, Insightful)
Slow? 125mhz MIPS is slow?
Might want to better explain what you mean.
Re:What is this for? (Score:5, Insightful)
More constrained by memory (Score:5, Insightful)
Re:What is this for? (Score:2, Insightful)
Re:More constrained by memory (Score:2, Insightful)
"Yes grandson, there was once a time where chips weren't able to and didn't need to run Linux and Java."
Re:Sigh (Score:3, Insightful)
wrong wrong wrong (Score:3, Insightful)
It should run a little file server, serving something like 9p [bell-labs.com] whihc would allow you to read/write settings and stream off the full data packets read for snorting.
fools.
Re:telnetd? (Score:5, Insightful)
Why yes it is, in the same way as your browser is "horribly insecure" when you login to slashdot.
It sends the data unencrypted, that is all. Granted, your server is probably more important than your
If you never would use telnet for anything, then you'd never surf without https either.
TCP over TCP is fine when payloads are unpacked (Score:5, Insightful)
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
Re:Well this means... (Score:3, Insightful)
If everyone released source happily, the GPL wouldn't be necessary in the first place. The point of the GPL is, in fact, to compel unwilling participants who recognize the value of the available GPL code to participate in Free Software. The instances where the difference between the GPL and the BSD license matter are the ones where it is necessary (and, due to the GPL, possible) to prod a vendor into releasing source. Fortunately, it's not all that hard to catch a vendor red handed. (c.f., "security by obscurity is fine, but things you sell to the public are not obscure")
Of course, I've found LinkSys hardware unreliable in the past, so I'm not that excited about them.
Re:telnetd? (Score:3, Insightful)
Re:Sigh (Score:3, Insightful)
When there is a "lack" of code, drivers, support, etc. in the Linux community, 99.999% of the time, it is due to lack of vendor support. Talk to them first. Ask them for the documentation. Ask them for the code. For the drivers. If they say buzz off, then you have your answer.
Companies that make it hard or impossible to get their hardware working with Linux, make it hard to want to get it working with Linux. There are other vendors who do support and embrace Linux, and we should support them instead.
The unhelpful companies will take a hint, or they'll go away; either way, problem solved.