GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
PLEASE NOTE: All LQ Rules apply to the General forum. Flame wars, personal attacks, hostility, insults and behavior of that nature will not be tolerated. Differing opinions are one of the things that make this site great, but to benefit from differing opinions the discourse must happen respectfully and thoughtfully... without insult or personal attack. Members who are unable or unwilling to participate in General under those parameters will not be permitted to do so. If you see behavior of this nature please report it.
I know that the Linksys WRT54G firmware does not support URL whitelisting, so my question is this: Is there a firmware mod (or replacement firmware altogether) that will allow for URL whitelisting for the WRT54G?
What I'm trying to do is create a makeshift family content filter because I'm dirt poor right now and can't afford to pay for a content filtering service or buy an extra machine to set up a Linux-based content filter with Squid, and I can't trust any kind of per-computer software to do the trick because its waaaaaay too easy to get around with things like live CDs...
Distribution: Fedora mainly, but I am open to others.
DD-WRT (possibly Open-WRT) on the WRT54G is a definite possibility for you.
I run Micro DD-WRT on my WRT54GS v5. I haven't fooled around with it, but you can block websites and keywords. This might be available on the default Linksys firmware, but I've never seen it on there. I've only seen it on DD-WRT.
Not sure precisely where I went wrong, but this is the course of events as best as I can remember.
1. Restored factory defaults on the router.
2. Tried to install v24-sp1 generic micro bin (or whatever the filename is) and got a goofy message like "Upgrade are failed." I tried it with both IE7 and FF3.
3. Tried various combinations of browsers and v24 .bin files that were supposed to be for v6. All of them gave "upgrade are failed."
4. Did a 30/30/30 reset, which seemed to have no effect.
5. Tried one of the off-site tutorials specifically for v5 and v6, but I don't know which one it was. It involved a "linux prep" bin and a "linux install bin" and TFTP.
6. The linux prep flash seemed to work okay and brought me to a maintenance screen (like the tut said it would).
7. Used the maintenance mode to use the "linux install bin." After 10 seconds or so the browser refreshed but said it was unable to access 192.168.1.1.
8. I took that as my queue to install the v23 bin (the one given by the tutorial) using TFTP. However, TFTP could not connect to 192.168.1.1 either. No firewalls or anti-viruses were enabled and I had full admin rights.
9. Not sure exactly what I did after that but it was around here that I think the router got bricked.
10. I tried another 30/30/30 reset but was unable to use the router.
Now all I have is a rapidly-blinking power LED that doesn't ever go away and no ability to connect to 192.168.1.1. When plugged in Windows says "limited or no connectivity" and Ubuntu gives me a "connected to wired network" icon in the systray but does not connect to 192.168.1.1 or anything else.
I can't ping it, either.
Last edited by TheMusicGuy; 09-11-2008 at 08:59 PM.
Distribution: Fedora mainly, but I am open to others.
Yikes, sounds like fun. I had a similar problem and here's what I did... mind you, you could brick your router for good.
You could look into the jtag method, which is a better way of doing things... but I didn't feel like doing one and I like living on the edge. So this is what I did...
You're going to have to open up your router. Disconnect the antennas, if any, and flip it upside down with the front facing away from you (the blue part) and hold the black portion in your palms and your thumbs on the rubber grips on the front, push away from you and this should pop off the front. There are no screws. Then, the bottom should be able to slide out. Here is a link to what it should look like when opened: http://lookforitoverhere.com/5/unbrick-wrt54g-v5/
The chip that is circled in that picture is the flash ROM and is where you're going to short the pins. My router has little white lines counting ever 5 pins, you can use this to help you count the pins. As the link describes, you're going to want to short out pins 15 and 16. It was 16 and 17 for me, but it's more than likely going to be 15/16 for you. I'd do this in Windows because it's easier. Unplug the power chord from the router, but leave the ethernet cable plugged into the computer. Manually set your IP address. Make your IP address 192.168.1.100 and make your gateway 192.168.1.1, leave your subnet mask at the default whatever it is and do not put in any DNS info... you don't have to. Go into the command line and start pinging with: ping -t 192.168.1.1
Now I use a copper wire from an unused power cable. Cut off the protective coating on each side, about an inch, and spin the copper really tight so it's compact and pointy. You're going to want a second person to help you here... girlfriend, sibling.. whatever. You're going to want to put one end of the copper cable on the left antenna block (the one the braided wire is connected to) and the other end is going to go on to pins 15 and 16. Have a second person hold the reset button for 30 seconds and at 30 seconds apply power to the router and then release the copper wire from pins 15 and 16. It's possible you could see a spark fly, that's ok. Once you release the copper wire, you should see the port number light up that you're plugged into and your router should start responding to the pings.
From there, use this how-to to install the firmware again. You can use the tftp program. Should be able to find it with a simple Google search if you don't already have it. http://www.bitsum.com/openwiking/owb...WRT54G5_CFE#h9 As it mentions on the page, look for the most recent version of dd-wrt micro generic. It's the ONLY one that will work with your router. Make sure you wait at least two minutes in between loading the .bin files to the router to allow it to do it's thing. It may mention power cycling (unplug the power and plug it back in), but doing this resulted it in going back to the power light blinking and being bricked all over again. So don't do it!
Let us know how you make out.
Last edited by BallsOfSteel; 09-12-2008 at 02:48 PM.
1. Connected by Ubuntu laptop via Ethernet to the WRT54G.
2. Started a continuous ping to 192.168.1.1.
3. Power cycled the WRT.
4. Ubuntu refused to connect until at least 15 seconds after powering the WRT, dashing any hopes of getting to the WRT before that magic "5-second startup period" during which it may be possible to get to a bricked WRT. So, I tried a different approach...
5. Replaced the WRT with a Linksys NR041 wired-only router (which I happened to have lying around) as my gateway.
6. Plugged all my computers plus the WRT into the NR041, with one of the client ports of the former connected to that of the latter. Let me explain via ASCII diagram:
7. Power cycled everything except the Win box.
8. Used the web GUI interface of the NR041 to change its IP to 192.168.1.126 so that it would not conflict with the WR.
9. Used the Ubuntu box to do a continuous ping to 192.168.1.1 (the WRT)
10. At this point I can't remember whether or not I power cycled the WRT again...I'm thinking I probably did.
11. **Started getting responses from the WRT in the ping output!**
12. Went back to the Win box and attempted to use TFTP to flash the DD-WRT v24 bin to 192.168.1.1. This time, it succeeded after less than a minute.
13. Waited about five minutes, then (while still connected to the NR041) browsed to 192.168.1.1 and was greeted by the DD-WRT gui interface telling me to input a username and password.
14. Unplugged everything, then plugged the Win box and the Ubuntu box into the now-working WRT.
15. Plugged the WRT router into the cable modem.
16. Power cycled everything.
17. Browsed to linuxquestions.org.
18. Started typing this list.
And that's how it happened!
Last edited by TheMusicGuy; 09-12-2008 at 03:32 PM.
Distribution: Fedora mainly, but I am open to others.
Y'know, I can see the feature in my head, but I don't know exactly where it is. I'm at work and my dd-wrt router is at home. But good work getting it going. If you don't find it before I do, I'll post how to disable wireless configuration.
And let us know how the white-listing thing goes too.
Nevermind, I found it. Oddly, though, it seemed to disable all wifi access altogether at first; I had to mess around with the wireless security settings to get wi fi working again.
But here's the irony of the whole thing: The access restrictions of DD-WRT (Micro, at least) don't seem to support white listing, either. But hey, now at least I can say I have an open source router...
Btw, I didn't see your instructions for unbricking via pin-shorting until after I posted my last response, presumably because I was still typing when you replied. Just so you don't think I was ignoring you or anything. (Though I'm glad I tried it my way before delving into possible elctrocution of my circuitboard...)
Anyway, thanks for all your help!
Last edited by TheMusicGuy; 09-12-2008 at 04:38 PM.
Okay, so DD-WRT was working fine for a while, but then it started fizzling out once every apx. 1/2 day and I kept having to reset/power cycle it to get internet connection back up. LAN worked okay, but the router could not connect to the open web. (I heard this had been happening with v23, but I thought it had been fixed with v24-SP1.)
I tried everything I could think of as far as configuration could go, and I *think* may have tried to reflash DD-WRT once, but the problem persisted. Finally, I decided to switch back to VxWorks just to see if that would fix the problem.
Well, that was quite a fiasco. I really don't remember what all I did, but the tutorial for reverting that was on DD-WRT's website did not work; I basically just kept trying different things until I finally got the Linksys Web GUI to come back. So far so good (though no more DD-WRT, unfortunately).
...then I started losing the connection again. I tried resetting it. For some reason, that brought me into Management Mode. I tried re-flashing the Linksys firmware. It didn't let me. I reset again, and the Web GUI came back, and it was working as usual for a short time.
After another 1/2 day, the internet connection quit again, but, as usual, LAN stayed up. I've tried resetting several times now; each time I do it I get a seemingly random response; sometimes I get the Web GUI, sometimes I get Management Mode, sometimes I can't connect at all and the router acts like it's bricked (i.e. continuously blinking power LED).
At the moment the Wi-Fi router is connected through a hard-wired router so that if the WRT54G fizzles out again the wired devices on my network won't be effected. I am able to connect to the WRT via Wi-Fi, but I can't access the internet or the GUI for the WRT.
I'm really confused. I have no idea what the state of my router is; sometimes it acts like it works, sometimes it doesn't. It's so random. Help....!