Linksys WRT54GL Loses WLAN Connection

Linksys Wrt54gl wireless router
May 25, 2010 at 10:33:23
Specs: Windows 7 Home & XP Pro SP3, Intel Core Duo, 1024
I have a Linksys WRT54GL v1.1 router running DD-WRT v23 SP2 (09/15/06) std -build 3932, hooked up to a Comcast cable modem (don't know the model number offhand).

Recently, I bought a Netgear ReadyNAS Duo 2210. It works fine now, but every now and then my router will not allow wirelessly connected PCs (Win 7 & XP) to access the internet (PCs still connect to the router and can ping intranet devices, but a ping of external sites fails). Rebooting the router fixes the problem (no need to reset the cable modem). During these times, PCs hardwired to the router still have internet connectivity.

I though this was the ReadyNAS trying to access the WAN/internet, so I disabled any feature that reaches beyond the intranet. However, this is STILL happening. Most recently, no problems for a week (during which I didn't use the NAS much). I then copied a large folder to the NAS (which went fine), and the next morning had lost WAN connectivity with the laptops. Router reboot fixed it.

I'm using IP Reservation for all the devices attached to this network. I'm thinking of disabling this to see if that helps.

I have a bridge set up for my Blu-ray player (it's a Linksys as well, I think a WRT54G or WRT54G2, also running DD-WRT, but no devices connect to that except the Blu-ray player).

Would love to use this device, but not if it's going to shut down my connection for my laptops every now and then.

To clarify, these problems never happened until I installed the NAS.

Any help is appreciated! Thanks!
Jon


See More: Linksys WRT54GL Loses WLAN Connection

Report •


#1
May 25, 2010 at 12:02:55
Rebooting doesn't fix the issue permanently so you'll have to try a couple other things.

First, ensure you have the most up-to-date version of the firmware available. I use Tomato myself and have had no problem with the ones I'm running so if there isn't a more recent version of the DD-WRT, you may want to try Tomato instead.

If that doesn't fix it, you will want to try resetting the unit to factory defaults and reconfiguring it.

If none of the above fixes it, it may very well be time to replace the unit.

Oh and FYI, I doubt the NAS has anything to do with it. I haven't checked to see if there are any known issues with that NAS and that router (you can if you want to) but in my estimation, it doesn't seem likely.


Report •

#2
May 25, 2010 at 12:21:05
I'll definitely look into upgrading the firmware or trying Tomato. Is it as easy to set up a bridge on Tomato?

I would have thought you were right about the NAS, but I've had this identical set up for 2 years and this NEVER happened until I hooked the NAS up. I'm willing to bet if I turn it off things will go back to normal. I can't see how that would be, but I really can't think of anything else.

Any other thoughts are much appreciated! Thanks!


Report •

#3
May 25, 2010 at 13:00:18
I would suggest to give the current version DD-WRT v24 SP1 a try.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

Related Solutions

#4
May 26, 2010 at 06:13:02
Curt R: Many apologies. You were 100% right. After leaving the NAS off for 2 days, the router dropped the DHCP connections again. NAS had nothing to do with it- Which is great! I love the device and didn't want to have to get rid of it.

PaulSep: I've upgraded to v24 SP1, will keep you posted to see if that helps. I checked the "keep settings" box, which did not work at ALL. I had to reset to factory defaults, which unfortunately means I have to reconfigure IP reservation, MAC filter, and the bridge (which was a real pain, as I recall). Might be a good excuse to simplify, though...

Thanks for the responses! I'll keep you posted on how the new firmware works out.


Report •

#5
May 26, 2010 at 07:18:10
Good news!

I hope the updated firmware fixes the issue because if it doesn't, your router may be toast.

I'm also glad you tried the updated version of the firmware you're already running. I phrased the portion of my first response relating to firmware most carefully because it's always better to stick with what you know when troubleshooting an issue. Swapping firmware in the middle of the process could lead to problems or having to redo steps.

If you're interested in tomato, have a look at it after you figure out what's going on with your router.

I've never used bridge mode on anything so I can't answer your question about that.


Report •

#6
May 26, 2010 at 09:40:36
jbroses

it's mostly a good idea, to reset the router to factory defaults, right after you've made a firmware upgrade.

Be smart, use your computer to write down the settings or make screenshots of each page, you have to make changes.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#7
June 10, 2010 at 11:55:42
Update: I upgraded firmware on both routers. Both were having strange problems during the configuration process (not broadcasting, unable to log in), but I got it done.

So now everything is working perfectly... except for one hitch. I cannot log into the routers (via 192.168.0.1/2) from wifi. If I plug an ethernet cable directly in, it's OK. Very strange, right?

I struggled so much with this I'm just going to leave it be, but it'll be a real pain if I have to change settings later. Can anyone think of why this would be?


Report •

#8
June 10, 2010 at 15:37:58
The default IP address of the updated router is 192.168.1.1 not 192.168.0.1.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#9
June 11, 2010 at 05:58:17
I know, I changed it. I've also tried 192.168.1.1. And like I said, I can connect on that IP address when direct connected via ethernet, so that's not the issue.

Any other ideas?


Report •

#10
June 11, 2010 at 06:45:17
Ok so have you disabled the wired card while using the wireless connection?

What does an ipconfig /all show, when you're connected only wirelessly?
Best is to post the output of ipconfig /all

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •

#11
June 11, 2010 at 07:33:22
Good idea! I will do that when I get home and post the results here. Thanks!

Report •

#12
June 11, 2010 at 17:07:37
I usually do NOT disable the other adatpers before checking the router address, but I just tried it now. Still not working. Very strange.

Here's the ipconfig /all results:

Windows IP Configuration

Host Name . . . . . . . . . . . . : JiggyNewLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.ma.comcast.net.

Ethernet adapter Leaf Networks Adapter:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Leaf Networks Adapter
Physical Address. . . . . . . . . : 00-FF-A5-0E-6D-68
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::bccc:630f:ff99:3de%24(Preferred)
IPv4 Address. . . . . . . . . . . : 5.169.10.135(Preferred)
Subnet Mask . . . . . . . . . . . : 255.0.0.0
Default Gateway . . . . . . . . . : 5.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 604045221
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-74-2F-07-00-21-9B-EB-81-1D

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . : hsd1.ma.comcast.net.
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
Physical Address. . . . . . . . . : 00-21-5C-3B-EA-87
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::55b5:1083:703b:dbd1%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.7(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, June 11, 2010 7:35:47 PM
Lease Expires . . . . . . . . . . : Saturday, June 12, 2010 7:35:47 PM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 218112348
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-74-2F-07-00-21-9B-EB-81-1D

DNS Servers . . . . . . . . . . . : 68.87.71.226
68.87.73.242
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Marvell Yukon 88E8040 PCI-E Fast Ethernet
Controller
Physical Address. . . . . . . . . : 00-21-9B-EB-81-1D
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.hsd1.ma.comcast.net.:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.ma.comcast.net.
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{27CE614C-3060-46D3-930B-822D309FCA3B}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e74:cd1:2f1d:be9f:5457(Prefe
rred)
Link-local IPv6 Address . . . . . : fe80::cd1:2f1d:be9f:5457%15(Preferred)
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{A50E6D68-6F72-4A44-9069-B582EC7C7F02}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter 6TO4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Reusable Microsoft 6To4 Adapter:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 12:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter #4
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2002:5a9:a87::5a9:a87(Preferred)
Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled


Report •

#13
June 11, 2010 at 19:25:50
So I guess the Leaf Network Adapter is connected to a NAS or something like that.
The Wireless Network Adapter gets it's ip address via DHCP from the router. That's quite ok.
But look, both network adapters do have a default gateway. That mostly doesn't work.

If you use the Leaf Network Adapter only for local access to a network device, you don't need a default gateway.
While it's configured manually, simply don't set the default gateway for that network adapter, so that the wireless network adapter is the only adapter, that has a default gateway.
This default gateway is used only, if a request can not be resolved locally.
So it's forwarded the the wireless router, which forwards it to your ISP.

Try that and post back the result.

The original poster should always write the last response !!!
Let us know, if the problem is solved !!!


Report •


Ask Question