Updated my Linksys WRT54G firmware, now it's bricked and my Belkin router won't handle DNS
2 replies, posted
Earlier today I was attempting to forward some ports for a dedicated server, but as always my Linksys WRT54G v2 completely ignored the fact that I had set up port forwarding as per the instructions verbatim. Usually when this happens I switch over to my generic Belkin Wireless G router because, while it does randomly disconnect the entire network every 3-4 hours, it does port forwarding very well (unless you have the gall to name two port forwarding settings the same thing or have their port ranges overlap, then it shits itself and starts throwing Java errors at you, deleting all your port forwarding settings, but that's getting tangential).
Anyway, today I decided I'd had enough of its bullshit and downloaded a firmware update for it. I entered its administration control panel and selected the file for it to use, and it summarily filled the progress bar and told me everything had gone just fine. It was at that point my network was disconnected entirely from the internet, and Windows began recognizing the router only as an unidentified network with no connection to the internet. Fortunately, I keep the aforementioned Belkin router in reserve for when things go as ferociously tits-up as they just had and often do, so I switched all my connections over. Unfortunately, when I tried to browse the web, I still couldn't connect and would time out. I couldn't ping Google, couldn't reach a webpage, nothing.
Then I noticed that I was still connected to the Steam network, and could talk with my friends. Skype was working too. Only the web was giving me shit, and when I attempted to browse directly to an IP address, everything was fine. If I manually set my network adapter to use Google's DNS (8.8.8.8), normal operation resumes. When I plugged my modem directly into my computer, everything was fine again. So the only conclusion I can draw is that my router is standing between my modem's DNS and my computer. I can even set the router's DNS manually to 8.8.8.8, but it doesn't seem to take.
I've reset and factory reset every component along the line, the Linksys router is dead for now, the Belkin is back to defaults, but still won't pass along a proper DNS to my system, either because it's not receiving it right from the modem, or isn't transmitting it right to the PC.
How in blazes did a firmware update cause a completely different router to stop handling the DNS properly?
Have you tried following the stuff [URL=http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash]on this page[/URL], especially the 30/30/30 reset? I'd be very surprised if you completely bricked that WRT. Try plugging a laptop in on its own after the reset and see if it gets an IP address, and you should be able to get into the Web UI and reconfigure.
Also, running stock firmware on that WRT is a huge waste, have you considered dd-wrt or tomato?
[QUOTE=leach139;35163510]Have you tried following the stuff [URL=http://www.dd-wrt.com/wiki/index.php/Recover_from_a_Bad_Flash]on this page[/URL], especially the 30/30/30 reset? I'd be very surprised if you completely bricked that WRT. Try plugging a laptop in on its own after the reset and see if it gets an IP address, and you should be able to get into the Web UI and reconfigure.[/QUOTE]
Well, I followed the procedures on that page, the 30/30/30 reset didn't take, and if their diagnostic guide is correct then I'll need to open up the router and build a cable to interface with it. I can't get any sort of connectivity with it from any system.
[QUOTE=leach139;35163510]Also, running stock firmware on that WRT is a huge waste, have you considered dd-wrt or tomato?[/QUOTE]
Until yesterday I didn't know third party router firmware was a thing. Had I known about it before having to investigate router firmware as a result of this, I would have installed DD-WRT instead of trying to update the firmware.
Honestly I never cared for the Linksys router, I could live without it if I just had any idea how bodging a flash with it could stop a completely different router from passing along the DNS from the modem.
Sorry, you need to Log In to post a reply to this thread.