|
 biker45
join:2003-10-18
Erie, CO
| Re: Looking for the Common Thread in router problems dellsweig:
I received your email with suggestion that I change my DHCP lease interval to 32767.
You have a good point. The router hang problem could be related to its processing of the DHCP lease renewal.
I just changed my lease expiration to 32767 and will post results in this thread. | |
|
 | |
| | pooter
join:2002-11-26
Somerset, NJ
1 edit | Re: Looking for the Common Thread in router problems I bought a new BEFSW11S4 V4 last week and upgraded it to firmware 1.50 first thing. It has up to 4 clients and froze once a day.
UPnP: off
WEP: enabled
WPA: off
Log: enabled
MTU: default
DHCP:default
SSID: broadcast disabled
Port Forwarding: Yes - 1 port
Filter Ports: none
Edit: I forgot to mention, I could not detect any patterns regarding the router hanging. Twice it happened overnight when the router was not in use (all PCs and other Internet devices were turned off.) Once it happened while I was using XBox Live and the other time it happened while surfing. | |
|
| | | 
Johkal
Cool Cat
Premium,MVM
join:2002-11-13
Happy Valley
clubs: | Re: Looking for the Common Thread in router proble Flash back to 1.45.7 | |
|
| | biker45
join:2003-10-18
Erie, CO
| Dan:
Setting DHCP lease interval to 32767 in BEFW11S4 v4, to try and resolve the router hang problem, did not work.
Router was in a hung state when I booted my PC this morning and attempted to access the net (i.e., pings to the inside IP address, 192.168.1.1, failed). After power cycling the router, the problem cleared as usual.
I leave my router and cable modem powered on 24x7, but I shut down my PCs at night. Before shutting down last night, I verified that the router was not hung. When I booted my wired PC this morning, I found the router was hung (pings to 192.168.1.1 confirmed the hang). Nothing in the router's log indicated a problem.
After booting in the morning is typically when I first encounter the router hang problem. The router hang problem occurs regardless of whether I boot my wired or wireless PC. Subsequent boots of either PC do not cause the router to hang (so booting is not causing the problem). Also, on rare occasions, I find that the router is not hung when I first boot my PCs in the morning.
Often during the day (with my PCs already booted), I will notice that I cannot access a web site. Subsequent pings to 192.168.1.1 fail, indicating that the router has hung again. On rare occasions, I can get through an entire day without a hang, but not often.
I really hoped that setting the DHCP lease time to 32767 would solve the problem, but I guess I won't be that lucky.
Since the hang often occurs at night when my PCs are down, I am wondering if the catalyst for the hang is something that my cable company is doing/sending. I guess I could power down my cable modem over night, leave the router powered up, and see if the router hangs (over night). If so, that would eliminate my cable company from the list of usual suspects.
Any other thoughts/suggestions would be appreciated. | |
|
| | | mikeyuf
join:2003-01-05
Gainesville, FL | Re: Looking for the Common Thread in router problems Well, Im having all the same problems.. But Im trying to to find 1.45.7? anyone have it? | |
|
| | | 
ToasterMan78
Premium
join:2003-11-26
| said by biker45  :
Any other thoughts/suggestions would be appreciated.
Probably others have mentioned this to you, but wired setups are intrinsically more stable than wireless setups. I don't know how long you have had problems (I see you have posted in other threads on your BEFW11), but it may be time to move to a wired setup. | |
|
| | | | biker45
join:2003-10-18
Erie, CO
| Re: Looking for the Common Thread in router problems ToasterMan:
Thanks.
The PCs that I use at home are wired to the BEFW11S4. When it hangs, my wired connections are down (until I reboot).
My wife's PC (in another room of the house) connects wirelessly to the BEFW11S4.
Prior to my wife getting her PC (last Oct), I was in an all wired configuration (and did not have any problems - I used a different vendor's hub to connect my PCs).
When my wife bought her PC, I installed a BEFW11S4 to serve as a wireless AP and router. That's when I began having reliability problems caused by the BEFW11S4 hanging. I could probably move my wired PCs to a different (non-Linksys) device, but I'd still have the Linksys box to contend with for my wife's wireless connection (running wires to the room where my wife's PC is located is not an option ... I will need some kind of wireless AP in my network ... Linksys or otherwise). | |
|
| | | | |
ToasterMan78
Premium
join:2003-11-26
| Re: Looking for the Common Thread in router problems said by biker45 :
...running wires to the room where my wife's PC is located is not an option ...
I suspect you don’t want to damage your house by drilling to run wires. I had a friend who had Comcast cable TV installed, and before he could say “don’t drill through the hardwood floor” the Comcast guy did just that. | |
|
| | | | | | MSNhurts
join:2003-12-27
Los Alamos, NM
| Re: Looking for the Common Thread in router problems My router used to hang constantly, and then I upgraded to 1.44 or 1.45 (forget) - and it worked great. Then, in hopes of WPA, I upgraded to 1.5 - now all the convenience of wireless is lost because every 10 minutes (ok, not quiet that often) I have to get up and go reset the router. Is this the first upgrade since Cisco acquired linksys? I want to know who to be pissed at for releasing a firmware upgrade that re-introduced a problem that had, at one time, been solved. At least the firmware reminds me of who I can likely thank - Linksys *A division of Cisco, inc.* | |
|
|
|
|
·
·