Losing WAN connection on a WRT54G; also with BEFW11S4; problem is widespread

First, for my particular setup:

-WRT54G wireless router
-originally running 1.02.01 firmware
-2.00.8 firmware (the most recent)
-using ping hack to boost signal to 84
-At this time, no security at all. So don't tell me 'disable WPA',
it's already done.


Note that the wireless router has exhibited this problem no matter
what the settings were (old firmware, new firmware, less power
consumption, more power, etc).


-Cable modem (blah, don't have the particular model), obviously
connected to the WRT54G WAN port

-WUSB54G connected to my Win98SE machine, though I've tested with
other machines as well w/ different adapters and on WinXP.


Channel distribution:
-Channel 2 *YOU ARE HERE*
-Channel 6 is in use by three visible wireless networks
-Channel 11 in use once
-Channel 1 in use once


Let me emphasize that this is _NOT_ a wireless problem. I think. The
*symptoms*, I should say, are not between the wireless router and the
wireless adapter. I am *never*, to my knowledge, disconnected from
the router. When the internet goes 'down', I can still access
192.168.1.1 and log in as the "admin"[1] and tinker. To no avail.

When the internet goes 'down', I go to the Status page of the admin
web pages. It shows that the router is no longer connected to the
internet. IP/Subnet mask are all 0.0.0.0, and the DNS/gateway
settings are blank. Any combination of "Release"/"Renew" does not
work.[2]

The problem can be fixed by 'cycling' the router.[3] Which is
ridiculous.

If I do not cycle the router (i.e. go to bed, go do something else,
throw in the towel in a general sense), the internet connection comes
back 'up'. I have lost the internet for as long as 12+ hours, and as
few as 30 minutes. This is equally ridiculous.


Now. I'd like to point out that this problem is widespread[see
references]--though the symptoms may originally seem dissimilar. In
all cases, the user(s) lose internet (WAN) connection but retain the
local (LAN) connection. This, FOR SURE, occurs with the 11Mbps
wireless routers; I've provided links below.

There is no mention of this problem on the Linksys web site. I'd
hope, with the frequency of this error, that Linksys would have a FAQ
entry or a workaround.


And speaking of workarounds. I have been told several things in my
quest. One is to change my MTU settings. Originally it was set at
1500. I changed it to 576, to no effect. Is there something I should
know or do regarding the MTU setting?

I was also told that putting a hub between the router and the cable
modem may fix the problem. If it does so (I have not tried this yet),
I will be even more unhappy. What good could this do?


What bothers me the most is that of all the threads I've read, almost
none have a successful resolution. Is there a proper solution for
this (apparently widespread) problem? This is really why I'm
attempting to link every known related error I could find. Because no
one seems to notice. This error is incredibly common, incredibly
frustrating, and *NO ONE SEEMS TO HAVE A WORKING SOLUTION*. I can't
emphasize how bad this is.

I don't even know exactly why I'm posting this, except perhaps in the
vain wish that someone will have the (cue the choir) Universal
Solution (/choir).


Pete

[1] Yes, I changed the "admin" password.

[2] I have used the Release/Renew while the internet was 'up', just to
ensure they work. They _do_ properly release/renew the DHCP lease.

[3] Cycling, meaning powering down then powering up the router. I
have a hacked version of the firmware, so I am able to telnet into the
router as well. I have tried messing with 'udhcpc' to no avail. I
also have used the 'reboot' command, which indeed reboots the router.
Rebooting via 'reboot' does *NOT* fix the problem.


references
----------
(explanations provided where needed; otherwise assume it's a link to a
single individual with a similar problem)

[1] - same problem with both versions of the routers:
http://www.broadbandreports.com/foru...1349~mode=flat

[2] -
http://www.broadbandreports.com/foru...5350~mode=flat

[3] -
http://www.broadbandreports.com/foru...5468~mode=flat

[4] -
http://forum.digitalspy.co.uk/board/...e46125dds.html

[5] - (from this newsgroup)
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den

[6] - two people with the same problem
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den

[7] - with the BEFW11S4
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den

[8] -
http://www.broadbandreports.com/foru...8420~mode=flat

[9] - with the BEFW11S4
http://www.broadbandreports.com/foru...3076~mode=flat

[10] - eerily similar
http://www.broadbandreports.com/foru...1980~mode=flat

[11] -
http://www.tek-tips.com/gviewthread....916/qid/733679

[12] -
http://www.tek-tips.com/gviewthread....916/qid/727112

[13] - with an interesting solution
http://www.tek-tips.com/gviewthread....916/qid/729512

(E-Mail Removed) (Pete) writes:
> When the internet goes 'down', I go to the Status page of the admin
> web pages. It shows that the router is no longer connected to the
> internet. IP/Subnet mask are all 0.0.0.0, and the DNS/gateway
> settings are blank. Any combination of "Release"/"Renew" does not
> work.[2]
>
> The problem can be fixed by 'cycling' the router.[3] Which is
> ridiculous.

You're right this is not a wireless issue.

In your detailed post I haven't seen any mention of you eliminating
the ISP or its cable modem as the source of your woes. The closest
datapoint we have is that rebooting the router always seems to solve
your internet connection problems.

Have you tried swapping in a new wireless router to rule out defective
hardware, and/or isolate it down to some strange flakiness of the
cable modem/connection?

--
Todd H.
http://www.toddh.net/

Pete,

A couple of questions for you that may or may not help...

1. When you lose your connection, does your cable modem still show
you on-line? i.e., my Surfboard lights would show an error (blinking
lights, etc) if I really dropped off-line.

2. Can you still access your cable modem diagnostic page during an
outage? On my Surfboard, I can see the diagnostics at
http://192.168.100.1

3. Have you removed the router and connected directly to your cable
modem? Do you stay on-line with a wired connection for extended
periods of time with this configuration?

4. Have you swapped the Ethernet cable between the cable modem and
router?

5. During an extended outage, does your router get issued a new IP or
is it somewhat static?

6. Have you tried a static (local) IP (192.168.1.100) for your
machine instead of DHCP? Any difference? From what you wrote, this
should not change anything. Just a thought...

Hopefully I didn't waste your time. I just thought that another
perspective might help. I guess I am one of the lucky ones with a
WRT54G/WPC54G combo that never dies.

Best of luck,

Scott

On 22 Dec 2003 13:17:00 -0800, (E-Mail Removed) (Pete)
wrote:

>First, for my particular setup:
>
>-WRT54G wireless router
> -originally running 1.02.01 firmware
> -2.00.8 firmware (the most recent)
> -using ping hack to boost signal to 84
> -At this time, no security at all. So don't tell me 'disable WPA',
>it's already done.
>
>
>Note that the wireless router has exhibited this problem no matter
>what the settings were (old firmware, new firmware, less power
>consumption, more power, etc).
>
>
>-Cable modem (blah, don't have the particular model), obviously
>connected to the WRT54G WAN port
>
>-WUSB54G connected to my Win98SE machine, though I've tested with
>other machines as well w/ different adapters and on WinXP.
>
>
>Channel distribution:
> -Channel 2 *YOU ARE HERE*
> -Channel 6 is in use by three visible wireless networks
> -Channel 11 in use once
> -Channel 1 in use once
>
>
>Let me emphasize that this is _NOT_ a wireless problem. I think. The
>*symptoms*, I should say, are not between the wireless router and the
>wireless adapter. I am *never*, to my knowledge, disconnected from
>the router. When the internet goes 'down', I can still access
>192.168.1.1 and log in as the "admin"[1] and tinker. To no avail.
>
>When the internet goes 'down', I go to the Status page of the admin
>web pages. It shows that the router is no longer connected to the
>internet. IP/Subnet mask are all 0.0.0.0, and the DNS/gateway
>settings are blank. Any combination of "Release"/"Renew" does not
>work.[2]
>
>The problem can be fixed by 'cycling' the router.[3] Which is
>ridiculous.
>
>If I do not cycle the router (i.e. go to bed, go do something else,
>throw in the towel in a general sense), the internet connection comes
>back 'up'. I have lost the internet for as long as 12+ hours, and as
>few as 30 minutes. This is equally ridiculous.
>
>
>Now. I'd like to point out that this problem is widespread[see
>references]--though the symptoms may originally seem dissimilar. In
>all cases, the user(s) lose internet (WAN) connection but retain the
>local (LAN) connection. This, FOR SURE, occurs with the 11Mbps
>wireless routers; I've provided links below.
>
>There is no mention of this problem on the Linksys web site. I'd
>hope, with the frequency of this error, that Linksys would have a FAQ
>entry or a workaround.
>
>
>And speaking of workarounds. I have been told several things in my
>quest. One is to change my MTU settings. Originally it was set at
>1500. I changed it to 576, to no effect. Is there something I should
>know or do regarding the MTU setting?
>
>I was also told that putting a hub between the router and the cable
>modem may fix the problem. If it does so (I have not tried this yet),
>I will be even more unhappy. What good could this do?
>
>
>What bothers me the most is that of all the threads I've read, almost
>none have a successful resolution. Is there a proper solution for
>this (apparently widespread) problem? This is really why I'm
>attempting to link every known related error I could find. Because no
>one seems to notice. This error is incredibly common, incredibly
>frustrating, and *NO ONE SEEMS TO HAVE A WORKING SOLUTION*. I can't
>emphasize how bad this is.
>
>I don't even know exactly why I'm posting this, except perhaps in the
>vain wish that someone will have the (cue the choir) Universal
>Solution (/choir).
>
>
>Pete
>
>[1] Yes, I changed the "admin" password.
>
>[2] I have used the Release/Renew while the internet was 'up', just to
>ensure they work. They _do_ properly release/renew the DHCP lease.
>
>[3] Cycling, meaning powering down then powering up the router. I
>have a hacked version of the firmware, so I am able to telnet into the
>router as well. I have tried messing with 'udhcpc' to no avail. I
>also have used the 'reboot' command, which indeed reboots the router.
>Rebooting via 'reboot' does *NOT* fix the problem.
>
>
>references
>----------
>(explanations provided where needed; otherwise assume it's a link to a
>single individual with a similar problem)
>
>[1] - same problem with both versions of the routers:
>http://www.broadbandreports.com/foru...1349~mode=flat
>
>[2] -
>http://www.broadbandreports.com/foru...5350~mode=flat
>
>[3] -
>http://www.broadbandreports.com/foru...5468~mode=flat
>
>[4] -
>http://forum.digitalspy.co.uk/board/...e46125dds.html
>
>[5] - (from this newsgroup)
>http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
>[6] - two people with the same problem
>http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
>[7] - with the BEFW11S4
>http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
>[8] -
>http://www.broadbandreports.com/foru...8420~mode=flat
>
>[9] - with the BEFW11S4
>http://www.broadbandreports.com/foru...3076~mode=flat
>
>[10] - eerily similar
>http://www.broadbandreports.com/foru...1980~mode=flat
>
>[11] -
>http://www.tek-tips.com/gviewthread....916/qid/733679
>
>[12] -
>http://www.tek-tips.com/gviewthread....916/qid/727112
>
>[13] - with an interesting solution
>http://www.tek-tips.com/gviewthread....916/qid/729512

> A couple of questions for you that may or may not help...
>
> 1. When you lose your connection, does your cable modem still show
> you on-line? i.e., my Surfboard lights would show an error (blinking
> lights, etc) if I really dropped off-line.

Yes, the cable modem lights are still on (all three, or whatever).

>
> 2. Can you still access your cable modem diagnostic page during an
> outage? On my Surfboard, I can see the diagnostics at
> http://192.168.100.1

Yes, with absolutely no problems.

> 3. Have you removed the router and connected directly to your cable
> modem? Do you stay on-line with a wired connection for extended
> periods of time with this configuration?

Yes, no problems.

> 4. Have you swapped the Ethernet cable between the cable modem and
> router?

Honestly, no, but I can't imagine the cable itself is the problem.
Note my multiple-references to people with the same problem. If it
was an isolated issue, such as bad cable, you wouldn't see as many
unresolved mentions of the same problem.


> 5. During an extended outage, does your router get issued a new IP or
> is it somewhat static?

I honestly don't know. I'm pretty sure it leases a different IP any
time I release/renew at all, I'll check.

> 6. Have you tried a static (local) IP (192.168.1.100) for your
> machine instead of DHCP? Any difference? From what you wrote, this
> should not change anything. Just a thought...

I'm running Windows 98SE (though for the wireless capabilities/general
network flexibility, I might make the jump to XP very soon) and my
network settings are consistently messed with by the Linksys wireless
connector program dealie, so the short answer is No. I suppose I
could have just wrote 'No' and moved on.

> Hopefully I didn't waste your time. I just thought that another
> perspective might help. I guess I am one of the lucky ones with a
> WRT54G/WPC54G combo that never dies.
>
> Best of luck,
>
> Scott

Thanks. I think I'll just give in and buy a hub/switch and plug the
router into one port and the cable modem into another, but I'd still
like some honest resolution of this problem.


Pete


> >references
> >----------
> >(explanations provided where needed; otherwise assume it's a link to a
> >single individual with a similar problem)
> >
> >[1] - same problem with both versions of the routers:
> >http://www.broadbandreports.com/foru...1349~mode=flat
> >
> >[2] -
> >http://www.broadbandreports.com/foru...5350~mode=flat
> >
> >[3] -
> >http://www.broadbandreports.com/foru...5468~mode=flat
> >
> >[4] -
> >http://forum.digitalspy.co.uk/board/...e46125dds.html
> >
> >[5] - (from this newsgroup)
> >http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
> >
> >[6] - two people with the same problem
> >http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
> >
> >[7] - with the BEFW11S4
> >http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
> >
> >[8] -
> >http://www.broadbandreports.com/foru...8420~mode=flat
> >
> >[9] - with the BEFW11S4
> >http://www.broadbandreports.com/foru...3076~mode=flat
> >
> >[10] - eerily similar
> >http://www.broadbandreports.com/foru...1980~mode=flat
> >
> >[11] -
> >http://www.tek-tips.com/gviewthread....916/qid/733679
> >
> >[12] -
> >http://www.tek-tips.com/gviewthread....916/qid/727112
> >
> >[13] - with an interesting solution
> >http://www.tek-tips.com/gviewthread....916/qid/729512

> You're right this is not a wireless issue.
>
> In your detailed post I haven't seen any mention of you eliminating
> the ISP or its cable modem as the source of your woes. The closest
> datapoint we have is that rebooting the router always seems to solve
> your internet connection problems.
>
> Have you tried swapping in a new wireless router to rule out defective
> hardware, and/or isolate it down to some strange flakiness of the
> cable modem/connection?

The cable modem works when directly connected to the computer. Which,
of course, defeats the purpose of going wireless.

I haven't done many things, primarily because I've read the
experiences of others and so many of the suggested solutions won't
work. One person RMA'ed three routers, all consistently failed. So I
am not going to bother RMA'ing this router, because it's not
necessarily defective hardware (meaning, not /specially/ damaged
hardware; there may be some flakiness, but it is consistently flaky).

I could attempt to try the ISP, but did you notice I found thirteen
references with one (or more) similar users with identical problems?
If there is an issue, it is probably between Linksys wireless routers
and a specific brand of cable modems. But that's not the point. The
point is that this is *NOT* an isolated issue. And everyone seems to
think it is. It's not. Check my references (which I found by light
Googling, and by searching a few forums/fora).


I replied to the other helpful gent, and told him that I would
probably shove a switch/hub in between the router and the cable modem.
I'm not particularly pleased about this, and I truly wanted an honest
solution. But oh well.


Pete

Pete wrote:
>>You're right this is not a wireless issue.
>>
>>In your detailed post I haven't seen any mention of you eliminating
>>the ISP or its cable modem as the source of your woes. The closest
>>datapoint we have is that rebooting the router always seems to solve
>>your internet connection problems.
>>
>>Have you tried swapping in a new wireless router to rule out defective
>>hardware, and/or isolate it down to some strange flakiness of the
>>cable modem/connection?
>
>
> The cable modem works when directly connected to the computer. Which,
> of course, defeats the purpose of going wireless.
>
> I haven't done many things, primarily because I've read the
> experiences of others and so many of the suggested solutions won't
> work. One person RMA'ed three routers, all consistently failed. So I
> am not going to bother RMA'ing this router, because it's not
> necessarily defective hardware (meaning, not /specially/ damaged
> hardware; there may be some flakiness, but it is consistently flaky).
>
> I could attempt to try the ISP, but did you notice I found thirteen
> references with one (or more) similar users with identical problems?
> If there is an issue, it is probably between Linksys wireless routers
> and a specific brand of cable modems. But that's not the point. The
> point is that this is *NOT* an isolated issue. And everyone seems to
> think it is. It's not. Check my references (which I found by light
> Googling, and by searching a few forums/fora).
>
>
> I replied to the other helpful gent, and told him that I would
> probably shove a switch/hub in between the router and the cable modem.
> I'm not particularly pleased about this, and I truly wanted an honest
> solution. But oh well.
>
>
> Pete
FWIW, I had a similar issue with a BELKIN wireless g router. Went thru 3
of them with the same problem.

In the the end, the problem was with my SB4200 cable modem. It would
perform fine when connected directly but caused a WAN droput issue when
connected to the routers. I replaced my modem and it fixed the problem.

Harvey

I have a similar problem with the v2.00.8 firmware on a 1.0 WRT54G (LAN part
disconnected from WAN part). However, this never happened with any of the
prior firmware revisions.

The following things currently irritate me with the router:
* WPA-PSK does not work when trying to connect to the router with a WPC11v3
unless a newer firmware than v1.41.2 is used (does linksys not test their
own products for compatibility?)
* The wireless part of the router disconnects every few minutes and
sometimes for extended periods of time in all firmware newer than v1.41.2
(again, does linksys not test their own products for compatibility?);
linksys has acknowledged that this is a problem with the firmware but has
not corrected it for the past few months.
* The listed changes with each firmware do not include some of the bug fixes
or group them by saying that a particular driver has been upgraded. Thus,
one has to try each firmware to find out if a particular bug has been fixed.
* Firmware never than v1.41.2 does not allow downgrading to v1.41.2 without
having to briefly install the european v1.41.8 firmware. The european
firmware revisions cleary mention the inability to downgrade; the US ones do
not even bring this up.

Thus, I'm still using the v1.41.2 firmware with WEP. That combination
appears to be stable for days at a time. I'd like to use WPA-PSK, but that
does not appear to be possible without the frequent disconnects experienced
with newer versions of the firmware. In addition, the drivers for WPA under
XP have a problem (at least the ones for the WPC11v3) in that the connection
to the router is not kept alive after logout (it is established before the
first user logs on) and must therefore be manually reestablished after the
next user logs on. This is not the case with WEP or when no encryption is
used (the connection is maintained between logons and logouts).

-Yves

"Pete" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> First, for my particular setup:
>
> -WRT54G wireless router
> -originally running 1.02.01 firmware
> -2.00.8 firmware (the most recent)
> -using ping hack to boost signal to 84
> -At this time, no security at all. So don't tell me 'disable WPA',
> it's already done.
>
>
> Note that the wireless router has exhibited this problem no matter
> what the settings were (old firmware, new firmware, less power
> consumption, more power, etc).
>
>
> -Cable modem (blah, don't have the particular model), obviously
> connected to the WRT54G WAN port
>
> -WUSB54G connected to my Win98SE machine, though I've tested with
> other machines as well w/ different adapters and on WinXP.
>
>
> Channel distribution:
> -Channel 2 *YOU ARE HERE*
> -Channel 6 is in use by three visible wireless networks
> -Channel 11 in use once
> -Channel 1 in use once
>
>
> Let me emphasize that this is _NOT_ a wireless problem. I think. The
> *symptoms*, I should say, are not between the wireless router and the
> wireless adapter. I am *never*, to my knowledge, disconnected from
> the router. When the internet goes 'down', I can still access
> 192.168.1.1 and log in as the "admin"[1] and tinker. To no avail.
>
> When the internet goes 'down', I go to the Status page of the admin
> web pages. It shows that the router is no longer connected to the
> internet. IP/Subnet mask are all 0.0.0.0, and the DNS/gateway
> settings are blank. Any combination of "Release"/"Renew" does not
> work.[2]
>
> The problem can be fixed by 'cycling' the router.[3] Which is
> ridiculous.
>
> If I do not cycle the router (i.e. go to bed, go do something else,
> throw in the towel in a general sense), the internet connection comes
> back 'up'. I have lost the internet for as long as 12+ hours, and as
> few as 30 minutes. This is equally ridiculous.
>
>
> Now. I'd like to point out that this problem is widespread[see
> references]--though the symptoms may originally seem dissimilar. In
> all cases, the user(s) lose internet (WAN) connection but retain the
> local (LAN) connection. This, FOR SURE, occurs with the 11Mbps
> wireless routers; I've provided links below.
>
> There is no mention of this problem on the Linksys web site. I'd
> hope, with the frequency of this error, that Linksys would have a FAQ
> entry or a workaround.
>
>
> And speaking of workarounds. I have been told several things in my
> quest. One is to change my MTU settings. Originally it was set at
> 1500. I changed it to 576, to no effect. Is there something I should
> know or do regarding the MTU setting?
>
> I was also told that putting a hub between the router and the cable
> modem may fix the problem. If it does so (I have not tried this yet),
> I will be even more unhappy. What good could this do?
>
>
> What bothers me the most is that of all the threads I've read, almost
> none have a successful resolution. Is there a proper solution for
> this (apparently widespread) problem? This is really why I'm
> attempting to link every known related error I could find. Because no
> one seems to notice. This error is incredibly common, incredibly
> frustrating, and *NO ONE SEEMS TO HAVE A WORKING SOLUTION*. I can't
> emphasize how bad this is.
>
> I don't even know exactly why I'm posting this, except perhaps in the
> vain wish that someone will have the (cue the choir) Universal
> Solution (/choir).
>
>
> Pete
>
> [1] Yes, I changed the "admin" password.
>
> [2] I have used the Release/Renew while the internet was 'up', just to
> ensure they work. They _do_ properly release/renew the DHCP lease.
>
> [3] Cycling, meaning powering down then powering up the router. I
> have a hacked version of the firmware, so I am able to telnet into the
> router as well. I have tried messing with 'udhcpc' to no avail. I
> also have used the 'reboot' command, which indeed reboots the router.
> Rebooting via 'reboot' does *NOT* fix the problem.
>
>
> references
> ----------
> (explanations provided where needed; otherwise assume it's a link to a
> single individual with a similar problem)
>
> [1] - same problem with both versions of the routers:
> http://www.broadbandreports.com/foru...1349~mode=flat
>
> [2] -
> http://www.broadbandreports.com/foru...5350~mode=flat
>
> [3] -
> http://www.broadbandreports.com/foru...5468~mode=flat
>
> [4] -
>
http://forum.digitalspy.co.uk/board/...e46125dds.html
>
> [5] - (from this newsgroup)
>
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
> [6] - two people with the same problem
>
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
> [7] - with the BEFW11S4
>
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
> [8] -
> http://www.broadbandreports.com/foru...8420~mode=flat
>
> [9] - with the BEFW11S4
> http://www.broadbandreports.com/foru...3076~mode=flat
>
> [10] - eerily similar
> http://www.broadbandreports.com/foru...1980~mode=flat
>
> [11] -
> http://www.tek-tips.com/gviewthread....916/qid/733679
>
> [12] -
> http://www.tek-tips.com/gviewthread....916/qid/727112
>
> [13] - with an interesting solution
> http://www.tek-tips.com/gviewthread....916/qid/729512

(E-Mail Removed) (Pete) writes:

> > You're right this is not a wireless issue.
> >
> > In your detailed post I haven't seen any mention of you eliminating
> > the ISP or its cable modem as the source of your woes. The closest
> > datapoint we have is that rebooting the router always seems to solve
> > your internet connection problems.
> >
> > Have you tried swapping in a new wireless router to rule out defective
> > hardware, and/or isolate it down to some strange flakiness of the
> > cable modem/connection?
>
> The cable modem works when directly connected to the computer. Which,
> of course, defeats the purpose of going wireless.
>
> I haven't done many things, primarily because I've read the
> experiences of others and so many of the suggested solutions won't
> work. One person RMA'ed three routers, all consistently failed. So I
> am not going to bother RMA'ing this router, because it's not
> necessarily defective hardware (meaning, not /specially/ damaged
> hardware; there may be some flakiness, but it is consistently
> flaky).

But also note that it's not necessarily NOT defective hardware, and
that if you're committed to not replacing any hardware, you may well
be committing yourself to the continuation of your problems.

Todd H.
http://www.toddh.net/

"Pete" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> First, for my particular setup:
>
> -WRT54G wireless router
> -originally running 1.02.01 firmware
> -2.00.8 firmware (the most recent)
> -using ping hack to boost signal to 84
> -At this time, no security at all. So don't tell me 'disable WPA',
> it's already done.
>
>
> Note that the wireless router has exhibited this problem no matter
> what the settings were (old firmware, new firmware, less power
> consumption, more power, etc).
>
>
> -Cable modem (blah, don't have the particular model), obviously
> connected to the WRT54G WAN port
>
> -WUSB54G connected to my Win98SE machine, though I've tested with
> other machines as well w/ different adapters and on WinXP.
>
>
> Channel distribution:
> -Channel 2 *YOU ARE HERE*
> -Channel 6 is in use by three visible wireless networks
> -Channel 11 in use once
> -Channel 1 in use once
>
>
> Let me emphasize that this is _NOT_ a wireless problem. I think. The
> *symptoms*, I should say, are not between the wireless router and the
> wireless adapter. I am *never*, to my knowledge, disconnected from
> the router. When the internet goes 'down', I can still access
> 192.168.1.1 and log in as the "admin"[1] and tinker. To no avail.
>
> When the internet goes 'down', I go to the Status page of the admin
> web pages. It shows that the router is no longer connected to the
> internet. IP/Subnet mask are all 0.0.0.0, and the DNS/gateway
> settings are blank. Any combination of "Release"/"Renew" does not
> work.[2]
>
> The problem can be fixed by 'cycling' the router.[3] Which is
> ridiculous.
>
> If I do not cycle the router (i.e. go to bed, go do something else,
> throw in the towel in a general sense), the internet connection comes
> back 'up'. I have lost the internet for as long as 12+ hours, and as
> few as 30 minutes. This is equally ridiculous.
>
>
> Now. I'd like to point out that this problem is widespread[see
> references]--though the symptoms may originally seem dissimilar. In
> all cases, the user(s) lose internet (WAN) connection but retain the
> local (LAN) connection. This, FOR SURE, occurs with the 11Mbps
> wireless routers; I've provided links below.
>
> There is no mention of this problem on the Linksys web site. I'd
> hope, with the frequency of this error, that Linksys would have a FAQ
> entry or a workaround.
>
>
> And speaking of workarounds. I have been told several things in my
> quest. One is to change my MTU settings. Originally it was set at
> 1500. I changed it to 576, to no effect. Is there something I should
> know or do regarding the MTU setting?
>
> I was also told that putting a hub between the router and the cable
> modem may fix the problem. If it does so (I have not tried this yet),
> I will be even more unhappy. What good could this do?
>
>
> What bothers me the most is that of all the threads I've read, almost
> none have a successful resolution. Is there a proper solution for
> this (apparently widespread) problem? This is really why I'm
> attempting to link every known related error I could find. Because no
> one seems to notice. This error is incredibly common, incredibly
> frustrating, and *NO ONE SEEMS TO HAVE A WORKING SOLUTION*. I can't
> emphasize how bad this is.
>
> I don't even know exactly why I'm posting this, except perhaps in the
> vain wish that someone will have the (cue the choir) Universal
> Solution (/choir).
>
>
> Pete
>
> [1] Yes, I changed the "admin" password.
>
> [2] I have used the Release/Renew while the internet was 'up', just to
> ensure they work. They _do_ properly release/renew the DHCP lease.
>
> [3] Cycling, meaning powering down then powering up the router. I
> have a hacked version of the firmware, so I am able to telnet into the
> router as well. I have tried messing with 'udhcpc' to no avail. I
> also have used the 'reboot' command, which indeed reboots the router.
> Rebooting via 'reboot' does *NOT* fix the problem.
>
>
> references
> ----------
> (explanations provided where needed; otherwise assume it's a link to a
> single individual with a similar problem)
>
> [1] - same problem with both versions of the routers:
> http://www.broadbandreports.com/foru...1349~mode=flat
>
> [2] -
> http://www.broadbandreports.com/foru...5350~mode=flat
>
> [3] -
> http://www.broadbandreports.com/foru...5468~mode=flat
>
> [4] -
>
http://forum.digitalspy.co.uk/board/...e46125dds.html
>
> [5] - (from this newsgroup)
>
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
> [6] - two people with the same problem
>
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
> [7] - with the BEFW11S4
>
http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
>
> [8] -
> http://www.broadbandreports.com/foru...8420~mode=flat
>
> [9] - with the BEFW11S4
> http://www.broadbandreports.com/foru...3076~mode=flat
>
> [10] - eerily similar
> http://www.broadbandreports.com/foru...1980~mode=flat
>
> [11] -
> http://www.tek-tips.com/gviewthread....916/qid/733679
>
> [12] -
> http://www.tek-tips.com/gviewthread....916/qid/727112
>
> [13] - with an interesting solution
> http://www.tek-tips.com/gviewthread....916/qid/729512

Pete,

I have been experiencing the exact same issues
with my BEFW11S4 V4 (firm1.5). Don't bother troubleshooting
any further, RMA it to Linksys. (I'm on my second one)

I described to a Linksys tech what was going on, but
of course they haven't had any serious issues
with this router and bascially just told me
to RMA it. This is potentially the most
annoying piece of hardware I have ever
used in 15 years of computing. What's better,
I'm now AP'less for the months upon months
it will take to get a new one. Buy Linksys again?
Never.

You might want to just save some time and buy a (different company's)
router. Check the single link below, titled "Post your BEFW11S4
problems here". The thread is ... I think 14 pages and running. It's
all the same problem--ours.


Pete


http://www.broadbandreports.com/foru...9184~mode=flat

> Pete,
>
> I have been experiencing the exact same issues
> with my BEFW11S4 V4 (firm1.5). Don't bother troubleshooting
> any further, RMA it to Linksys. (I'm on my second one)
>
> I described to a Linksys tech what was going on, but
> of course they haven't had any serious issues
> with this router and bascially just told me
> to RMA it. This is potentially the most
> annoying piece of hardware I have ever
> used in 15 years of computing. What's better,
> I'm now AP'less for the months upon months
> it will take to get a new one. Buy Linksys again?
> Never.




> > references
> > ----------
> > (explanations provided where needed; otherwise assume it's a link to a
> > single individual with a similar problem)
> >
> > [1] - same problem with both versions of the routers:
> > http://www.broadbandreports.com/foru...1349~mode=flat
> >
> > [2] -
> > http://www.broadbandreports.com/foru...5350~mode=flat
> >
> > [3] -
> > http://www.broadbandreports.com/foru...5468~mode=flat
> >
> > [4] -
> >
> http://forum.digitalspy.co.uk/board/...e46125dds.html
> >
> > [5] - (from this newsgroup)
> >
> http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
> >
> > [6] - two people with the same problem
> >
> http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
> >
> > [7] - with the BEFW11S4
> >
> http://groups.google.com/groups?hl=e...TF-8%26hl%3Den
> >
> > [8] -
> > http://www.broadbandreports.com/foru...8420~mode=flat
> >
> > [9] - with the BEFW11S4
> > http://www.broadbandreports.com/foru...3076~mode=flat
> >
> > [10] - eerily similar
> > http://www.broadbandreports.com/foru...1980~mode=flat
> >
> > [11] -
> > http://www.tek-tips.com/gviewthread....916/qid/733679
> >
> > [12] -
> > http://www.tek-tips.com/gviewthread....916/qid/727112
> >
> > [13] - with an interesting solution
> > http://www.tek-tips.com/gviewthread....916/qid/729512
>