Re: Problem with wrt54gl router
Keeping power off on the cable modem fixed the problem. I had recycled it before but only for a short time. When it was working /etc/resolv.conf had an entry to search and 3 name servers. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Problem with wrt54gl router
I have a Linksys WRT54GL router with the original firmware. It worked fine until yesterday. When I bring up the network /etc/resolv.conf has the following: search nameserver 192.168.1.1 This is true for both hardwired and wireless. If I run dhclient it acts as if everything is working but I get no nameservers. If I connect directly to the external network everything works fine. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
On 9/17/07, Don Leslie [EMAIL PROTECTED] wrote: When I bring up the network /etc/resolv.conf has the following: search nameserver 192.168.1.1 This is true for both hardwired and wireless. What were you expecting instead? Have you tried actually running a lookup with that IP address as the nameserver? 192.168.1.1 may actually be correct. As I recall, the stock LinkSys firmware runs a DNS proxy on the router. That means machines inside your LAN can just send their DNS queries to the router, and the router will handle forwarding the request out to whatever the ISP nameservers are today. Assuming that is *not* the situation: Have you tried rebooting the router? Have you tried updating to the latest firmware on the router? (These are standard procedures, yes, but they're standard because they often work. :) ) Assuming *that* does not fix anything: What OS/distribution/release are you running on your DHCP client? -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
Date: Mon, 17 Sep 2007 09:05:04 -1000 From: Don Leslie [EMAIL PROTECTED] X-MIMETrack: Itemize by SMTP Server on AD2-MSG01/SRV/Raytheon(Release 7.0.2FP1|January 10, 2007) at 09/17/2007 15:05:06, Serialize by Router on AD2-MSG01/SRV/Raytheon(Release 7.0.2FP1|January 10, 2007) at 09/17/2007 15:05:06, Serialize complete at 09/17/2007 15:05:06 Sender: [EMAIL PROTECTED] I have a Linksys WRT54GL router with the original firmware. It worked fine until yesterday. When I bring up the network /etc/resolv.conf has the following: search nameserver 192.168.1.1 Is this on the router itself or a client on the LAN? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
Ben Scott wrote: On 9/17/07, Don Leslie [EMAIL PROTECTED] wrote: When I bring up the network /etc/resolv.conf has the following: search nameserver 192.168.1.1 This is true for both hardwired and wireless. What were you expecting instead? Have you tried actually running a lookup with that IP address as the nameserver? 192.168.1.1 may actually be correct. As I recall, the stock LinkSys firmware runs a DNS proxy on the router. That means machines inside your LAN can just send their DNS queries to the router, and the router will handle forwarding the request out to whatever the ISP nameservers are today. Assuming that is *not* the situation: Have you tried rebooting the router? Have you tried updating to the latest firmware on the router? (These are standard procedures, yes, but they're standard because they often work. :) ) Assuming *that* does not fix anything: What OS/distribution/release are you running on your DHCP client? -- Ben I do not remember what it looked like when things worked. If I try to ping the Roadrunner name server I get from 192.16.1.1 Destination Unreachable dig fails to find a server I am running SuSE 10.2 . I rebooted the router which made no difference. I could look into new firmware but it has been running fine for months. Don ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
On 9/17/07, Don Leslie [EMAIL PROTECTED] wrote: If I try to ping the Roadrunner name server I get from 192.16.1.1 Destination Unreachable I assume you mean 192.168.1.1 in the above (168, not 16), and that 192.168.1.1 is the IP address of your router. If my assumptions are correct: What your router is saying is that it has no route to the address you were pinging. That occurs below the level of DNS (at the IP layer), so the DNS issue is likely more of a symptom than a cause. Most likely, your router isn't getting any DHCP information from the ISP, so it does not have an IP address on the public Internet (which is why it has no route to the Internet). See if you can log-in to the web management UI on the LinkSys router. Typically this will mean entering http://192.168.1.1 on the router. The default password will be in the manual, but I think it's either linksys, admin, or password. The username doesn't matter on most LinkSys models. Once you're in the web UI, go to the Status information screen, and check the Internet/WAN status. I rebooted the router which made no difference. I take it you have cable Internet? Have you tried the standard generic cable Internet reset procedure? That is: 1. Note the present indicator lights on the cable modem and LinkSys router. 2. Shutdown your LAN DHCP clients. 3. Unplug power from cable modem and LinkSys router. 4. Wait 15 minutes. (Yes, that long. Really.) 5. Plug cable modem power back in. 6. Wait for the cable modem to re-acquire service. This will typically be indicated by indicator lights on the modem. See step 1. :) 7. Plug LinkSys router power back in. 8. Wait for the LinkSys to boot. Again, look at the lights. 9. Power one of your LAN DHCP clients back on. See if it works. The above fixes a lot of problems. I could look into new firmware but it has been running fine for months. Right, but it's not running fine now. Obviously *something* happened. :) Re-flashing is the firmware equivalent to unplugging everything and plugging it all back in again. It sometimes fixes things, but we never really know why. Possible correlations include the ISP changing something which broke your old firmware, and the existing firmware somehow getting corrupted. Still, at this point, it sounds more like a provider service problem to me. I'd save re-flashing for later, as more of a last resort. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
Date: Mon, 17 Sep 2007 17:37:24 -0400 From: Ben Scott [EMAIL PROTECTED] See if you can log-in to the web management UI on the LinkSys router. Typically this will mean entering http://192.168.1.1 on the router. The default password will be in the manual, but I think it's either linksys, admin, or password. The username doesn't matter on most LinkSys models. If the admin password is still the default admin password, it may not be anymore. A neighbor with a default password list could easily cause this kind of trouble. ;) 3. Unplug power from cable modem and LinkSys router. 4. Wait 15 minutes. (Yes, that long. Really.) I have to second step #4. That's how long it really takes for all the broken electrons to flow back down the wires to Comcast. 5. Plug cable modem power back in. I could look into new firmware but it has been running fine for months. Right, but it's not running fine now. Obviously *something* happened. :) Did you try the reset button? ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
On 9/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 4. Wait 15 minutes. (Yes, that long. Really.) I have to second step #4. That's how long it really takes for all the broken electrons to flow back down the wires to Comcast. For those interested in Why: What we're after here is two things: One is that most cable operators have their modems set to speak to only one Ethernet (MAC) address on the customer side. The modem associates with the first address it sees. Power cycling the modem will reset this. This one really only needs a wait for a few seconds. The second thing is that sometimes there is some kind of glitch between the cable modem and the cable operator's plant (inclusive). Dropping signal at your end for several minutes will cause the head-end to decide you've gone away, and clear whatever state it keeps about you. Thus when you come back, it re-does all of the initialization stuff. If you come back too quickly, it might decide you just glitched for a bit, and keep that (presumably corrupt) state around. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
Re: Problem with wrt54gl router
If you need to reset this router back to defaults, power it down, and then push in the reset button and hold for 30 seconds.. I think this can also be accomplished va the admin GUI as well JFeole -- Ben Scott wrote: On 9/17/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: 4. Wait 15 minutes. (Yes, that long. Really.) I have to second step #4. That's how long it really takes for all the broken electrons to flow back down the wires to Comcast. For those interested in Why: What we're after here is two things: One is that most cable operators have their modems set to speak to only one Ethernet (MAC) address on the customer side. The modem associates with the first address it sees. Power cycling the modem will reset this. This one really only needs a wait for a few seconds. The second thing is that sometimes there is some kind of glitch between the cable modem and the cable operator's plant (inclusive). Dropping signal at your end for several minutes will cause the head-end to decide you've gone away, and clear whatever state it keeps about you. Thus when you come back, it re-does all of the initialization stuff. If you come back too quickly, it might decide you just glitched for a bit, and keep that (presumably corrupt) state around. -- Ben ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ ___ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
