 | reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issues? I called Links they say there is no problem with the firware the problem is with the cable povider "comcast". Comcast tech's told me they are aware of problems in their lines however no one with the authority to fix it wants to admit there is a problem. |
|
 | I'm on Comcast and started having the problem about 2 weeks ago. But I also know people who are not on Comcast that are having the same problem. All of them are/were running the 1.45.7 firmware. Downgrading to 1.44.2z fixed the problem.
So as has been brought up before, something is sending out bad data and routers using 1.45.7 are being affected by it, so it points to a software issue with the Linksys router.
I'm wondering if the Beagle worms are responsible for this problem. That is, they open up a port to listen for a specially formatted data message to the port. So people scanning for the open ports could end up locking the router up. |
|
 | reply to CatchingSpy I doubt it's Comcast's problem as there is others using different ISPs and having the same problem.
Linksys has morons for tech support and I just hope they don't ignore this issue like they do all the others. |
|
 CorvusFlaming Tards Since 2003Premium,VIP join:2003-11-26 | reply to Mordrid said by Mordrid: I'm on Comcast and started having the problem about 2 weeks ago. But I also know people who are not on Comcast that are having the same problem. All of them are/were running the 1.45.7 firmware. Downgrading to 1.44.2z fixed the problem.
So as has been brought up before, something is sending out bad data and routers using 1.45.7 are being affected by it, so it points to a software issue with the Linksys router.
I receive a lot of request on 65506 for the new Phatbot since two weeks, could it be related?
»The Attack of PhatBot |
|
 ShootistPremium join:2003-02-10 Decatur, GA kudos:3 Reviews:
·AT&T Southeast
| It seems everyone that is having problems is on CABLE. So maybe it is your CABLE ISP that is causing the problem. Yes it also is a Linksys SR41 problem BUT no one here is on DSL, except the people that don't have the problem. -- Shooter Ready--Stand By BEEP ******** |
|
 hqh510 join:2001-03-24 Manassas, VA | reply to Mordrid I was on a 1.44.2 firmware in the first place. Router rebooted. So I thought upgrading the firmware would help a bit. Went to 1.45.7. Still didn't work. Router would reboot.
said by Mordrid: I'm on Comcast and started having the problem about 2 weeks ago. But I also know people who are not on Comcast that are having the same problem. All of them are/were running the 1.45.7 firmware. Downgrading to 1.44.2z fixed the problem.
So as has been brought up before, something is sending out bad data and routers using 1.45.7 are being affected by it, so it points to a software issue with the Linksys router.
I'm wondering if the Beagle worms are responsible for this problem. That is, they open up a port to listen for a specially formatted data message to the port. So people scanning for the open ports could end up locking the router up.
-- HQH === My website; DLink DI-624,DWL-G520,DWL-G650 Super G Performances; BEFSR41 Setup Guide:»www.geocities.com/hqh51/ |
|
 | reply to Mordrid I have about 100+ BEFSR41, 100+ BEFSX41, 75+ BEFVP41 units across the US, all of them are running firmware that has been available as of Dec 2003. Some of the BEFSR41 units are almost 5 years old (I think it's that old in some places - they were purchased when Linksys first released them).
In all that time, I've had one unit that became defective, and it was a couple bad caps.
Our networks use RR Cable or Adelphia DSL, or are internal networks for different offices/centers within the company.
We have yet to see any of the problems described in this thread. |
|
 | Re: So, Linksys can we get a word on BEFSR41 issue "We have yet to see any of the problems described in this thread."
This is good to know. What firmware are they running? |
|
|
|
 | reply to Mordrid
Re: So, Linksys can we get a word on BEFSR41 issues? said by Mordrid: I'm on Comcast and started having the problem about 2 weeks ago. But I also know people who are not on Comcast that are having the same problem. All of them are/were running the 1.45.7 firmware. Downgrading to 1.44.2z fixed the problem.
So as has been brought up before, something is sending out bad data and routers using 1.45.7 are being affected by it, so it points to a software issue with the Linksys router.
I'm wondering if the Beagle worms are responsible for this problem. That is, they open up a port to listen for a specially formatted data message to the port. So people scanning for the open ports could end up locking the router up.
MY GOD!!! I'm on Comcast and started having this problem about two days ago...have been using BEFSR41 with v1.44.2 for almost a year with no problems. I upgraded today to 1.45.7 and that only made things worse.
I've been a packet geek for 15 years and I STILL spent two DAYS trying to figure this out...I assumed it was my problem since the Linksys has been working well for so long.
I've put packet analyzer on both sides of my Linksys, so I can shed a bit more detail on what I see happening. Here's my config:
PC -> hub1 -> BEFSR41 -> hub2 -> SonicWall -> hub3 -> CM -> Comcast
Analyzers injected on hub1 and hub2.
Shortly after getting a fresh DHCP lease PC is able to surf no problem, but them some minutes or hours later intermittent problems..the first sign is high failure of DNS queries.
Using the analyzers I can see that my DNS requests go out correctly, the DNS response is recorded by Analyzer on hub2, but NOT on Analyzer 1. Thus is appears that incoming response packets are being dropped by the Linksys.
I even tried configuring the PC as a DMZ host, thinking that if there was some NAT translation problem, that would work around it...no go.
I also checked the incoming and outgoing logs on the LInksys to see if something was being blocked...no indication of that.
If I do a ipconfig/release /renew, traffic then begins flowing again. This problem only seems to impact tcp and udp traffic, ICMP traffic is unaffected...which is what also makes the troubleshooting confusing.
I finally gave up and ripped out the Linksys and dropped in an old Netgear RT318...it has been working flawlessly for hours now.
Based on what is being reported here I guessing that some kind of (new) traffic is being presented to the Linksys that triggers some kind of latent bug that has been there all along. -- Lawrence Baldwin myNetWatchman The Internet Neighborhood Watch |
|
 | said by NetWatchMan: said by Mordrid: I'm on Comcast and started having the problem about 2 weeks ago. But I also know people who are not on Comcast that are having the same problem. All of them are/were running the 1.45.7 firmware. Downgrading to 1.44.2z fixed the problem.
So as has been brought up before, something is sending out bad data and routers using 1.45.7 are being affected by it, so it points to a software issue with the Linksys router.
I'm wondering if the Beagle worms are responsible for this problem. That is, they open up a port to listen for a specially formatted data message to the port. So people scanning for the open ports could end up locking the router up.
MY GOD!!! I'm on Comcast and started having this problem about two days ago...have been using BEFSR41 with v1.44.2 for almost a year with no problems. I upgraded today to 1.45.7 and that only made things worse.
I've been a packet geek for 15 years and I STILL spent two DAYS trying to figure this out...I assumed it was my problem since the Linksys has been working well for so long.
I've put packet analyzer on both sides of my Linksys, so I can shed a bit more detail on what I see happening. Here's my config:
PC -> hub1 -> BEFSR41 -> hub2 -> SonicWall -> hub3 -> CM -> Comcast
Analyzers injected on hub1 and hub2.
Shortly after getting a fresh DHCP lease PC is able to surf no problem, but them some minutes or hours later intermittent problems..the first sign is high failure of DNS queries.
Using the analyzers I can see that my DNS requests go out correctly, the DNS response is recorded by Analyzer on hub2, but NOT on Analyzer 1. Thus is appears that incoming response packets are being dropped by the Linksys.
I even tried configuring the PC as a DMZ host, thinking that if there was some NAT translation problem, that would work around it...no go.
I also checked the incoming and outgoing logs on the LInksys to see if something was being blocked...no indication of that.
If I do a ipconfig/release /renew, traffic then begins flowing again. This problem only seems to impact tcp and udp traffic, ICMP traffic is unaffected...which is what also makes the troubleshooting confusing.
I finally gave up and ripped out the Linksys and dropped in an old Netgear RT318...it has been working flawlessly for hours now.
Based on what is being reported here I guessing that some kind of (new) traffic is being presented to the Linksys that triggers some kind of latent bug that has been there all along.
Yes! I noticed ICMP traffic was working as well. I'll be getting rid of this pos linksys now. Thanks for looking into that. |
|
 | reply to Mordrid CONFIRMED! FIRMWARE Problems in 1.45.7. I also downgraded my Firmware version 1.44.2z. Port forwarding working again. |
|
 zCobra join:2003-01-07 Houston, TX | To Rainfire: So was Port forwarding the only issue you were having? Most of the problems being discussed in this thread have been related to the BEFSR41 locking up and preventing any access out to the net. Quick fix has been to recycle the power but problems return shortly after.
Some users have reported success in downgrading from 1.45.7 to 1.44.2z but I can confirm that this did NOT help me at all nor many other users. The only fix I found was in replacing my modem. I have been running 1.45.7 since it came out without any problems and for 1.45.7 to suddenly start crapping out for hundreds of users around the country, all at the same time, doesn't make sense. Yes, I agree there is a flaw in the firmware on the BEFSR41's but I don't believe it is limited to just 1.45.7.
Something started happening early this year that's upstream of our routers and it's exposing this flaw in the firmware. For Linksys to fix this, they have to determine what that is. Some type of attack? Malformed packets from our Modems due to ISP firmware upgrades being remotely pushed out? Changes made to the ISP infrastructure that are having a negative impact? or maybe it's just the new RIAA plan (knock everyone off the internet)
Something changed outside of our Routers that caused this to begin. |
|
 jmstr join:2002-07-24 Clovis, CA | I will also confirm that with BEFSR41 V2, FW 1.45.7, port forwarding does NOT work. I downgraded to 1.42.2 and it works. Wasted too much time figuring this one out. Something like this should have been found at the factory. All these router manufacturers (DLink, Netgear & Linksys) are selling un-tested products and using customers as there test department. Bad business! |
|
 kar98 join:2004-04-29 Longview, TX | reply to Shootist Nawww, it's not limited to cable. I'm on SBC DSL and I'm pulling my hair out here. |
|
 | reply to zCobra No, on my BEFSR11, with the latest BIOS I also had connection issues with ISP router (Cisco) meaning that it would drop connection 4 or 5 times a week and needed reset as in power off/on. Haven't had the problems since I went back to the older BIOS. |
|
 | I am having the same lockup problems. Internet goes dead, can't access the linksys setup page etc. Restarting the router gets everything back up.
Linksys BEFSR41 ver.2 Firmware 1.45.7 Bell Sympatico Speedstream 5200
This started happen after I have upgraded to the 1.45.7 firmware. |
|
 mikehdWhat day is it?Premium join:2000-07-11 Lebanon, OR | Re: So, Linksys can we get a word on BEFSR41 issue I've been on 1.44.2 with my V2 for about a month now. Stability is good. Only one non-responsive router incident after my wife had been running ICQ for a while. Prior F/W was 1.45.7 and had daily loss of connection, or router lockups, starting in the Feb/March timeframe.
Linksys BEFSR41 V2 F/W 1.44.2, Dec 13 2002 Centurytel DSL (1.5/512) Westell 36R516 |
|
 | funny how you guys must upgrade to the "newest and best" when you can't tech what you have. |
|
 n0xlf join:2001-03-28 Castle Rock, CO kudos:1 | No one should have to "tech" the firmware of their router..It's not like there is some sort of user adjustable parameter that will stop these lockups... |
|
 jbobReach Out and Touch SomeonePremium join:2004-04-26 Little Rock, AR | reply to azua1232 One thing to remind yourself is that newer firmware wouldn't be issued unless the previous one didn't have any problems. So don't just blantantly blame the upgraders. The only reason why the newest and best is not the "best" is because of bad codeing. Not actually the upgraders fault is it? |
|