| So, Linksys can we get a word on BEFSR41 issues? Well, it seems a lot of BEFSR41 users are having issues with a disonn/reconnect to the router every so often; this issue has just start happening recently to everyone...
I hope we can have some offical comment on this since you flat out ignore the bittorrent/emule connection problems on your cable modems. |
|
| Yep, looks like new firmware is needed on the v2 and v3. Any idea on when this might be released? |
|
x062pea
join:2002-04-07
Huntingtown, MD | reply to ZeitgeistJ
Let’s narrow the problem down and see if we can find any common factors. Everyone experiencing this problem should respond with the following:
Router make/model and firmare version
ISP type and provider
Cable Modem make/model
I will go first.
I have noticed that this problem has started about 3 weeks ago. I have the following:
Router BEFSR41 V2. w/1.45.7 and 1.44.2
ISP Cable/Comcast
Modem Surfboard SB3100 |
|
|
|
1 edit | reply to ZeitgeistJ
Same here ...
I got a replacement from the store, but same thing.
--------------
BEFSR41 v3 1.04.17 (came with 1.04.12 but was even worse)
Cable / Pandora (belgium)
Motorola surfboard cable modem
--------------
I noticed a few strange things though. (I have a Cisco CCNA degree, so I understand a little of what goes on inside these things)
Status - Local Network - Show local dhcp table button
When I press that button, the popup displays the titles, but no leased ip's. I have 2 XP boxes and an OSX 10.3.2 connected to the router, they all got a valid IP address.
Maybe it's a bug in the displaying of the table, maybe something's wrong with the dhcp leases. who knows....
change the router ip address
I changed my router address to 10.0.0.1 and the dhcp starting at 10.0.0.10 and going to 10.0.0.29 (20 leases)
You need to reboot the router first and give your pc a static 10.0.0.x ip before you can logon again to change the DHCP settings.
Even without a firmware upgrade, stability increased A LOT. but I expect it to work ALWAYS....
For as far as I know and see I think it has to do with IP related problems. (Layer 3, cisco'ers....)
NAT might be screwing up.
DHCP leases may be corrupting. (setting them from 0 to 10800 minutes (1 week) helped a bit as well. My connections come up faster on boot this way)
Well, anyway, if a Cisco / Linksys Rep. sees this, please help us out here.
Get us better firmware or get us access to all beta firmwares you guys have been making. I'll be happy to test and write reports on all of them.
*Dacode still thinks he should have saved the money to get a Cisco 2600 Series. |
|
| BEFSR41 v3 1.04.17 (no idea what it came with)
Cable/Roadrunner (Tampa, FL USA)
Ericsson PipeRider HM200C cable modem
I'm trying one more thing tonight and if it doesn't work, then this is what I posted at other forums:
"I've decided that I can't wait for the firmware upgrade as this could take a while and may not even work after this. I've already sent my RMA request into ZipZoomFly and was wondering should I get the D-Link DI-604 or the SMC 7004VBR to replace the Linksys BEFSR41 v3?" |
|
 CorvusFlaming Tards Since 2003Premium,VIP
join:2003-11-26 | reply to ZeitgeistJ
BEFSR41 V.2 1.45.7
Cable Videotron
Scientific Atlanta DPX-100
***
When disconnection happens: I can't ping my router with any device connected to it. There's no release/renew and my modem is still up, it's confirmed. |
|
| BEFSR41 v3 1.04.17
Terayon 715j Cable Modem
Adelphia Powerlink Cable
Have had all kinds of wierd things happen with this router. |
|
| reply to ZeitgeistJ
Linksys BEFSR41 V2 (was using 1.45.7 but downgraded to 1.44.2 and the problem seems to have disappeared - no disconnect for over a week)
Rogers Cable Internet
Terayon Blue 'Shark-Fin' Modem (TCM200)
I ran 1.45.7 since it was released but had some disconnect issues a couple of weeks ago that kept recurring. Downgraded to 1.44.2, hard reset and off we go. As a side note, the only other change was that when I downgraded I allowed the firmware to default to a MTU of 1500 rather than force it to 1500. Not sure if this was an issue or not. |
|
| reply to x062pea
said by x062pea:
Let’s narrow the problem down and see if we can find any common factors.
I've been playing with BEFSR11 and BEFSR41 firmwares for a few years now....
I'd suggest that you not only look into the hardware/connection side of things, but also the type of use of the PC(s)/router/modem. For example, using eMule or BitTorrent will *always* hose a BEFSR41 in a reasonable short time (depending on the number of connections) requiring a power cycle to reconnect.
Regards,
Marcelo |
|
x062pea
join:2002-04-07
Huntingtown, MD | reply to ZeitgeistJ
I personally do not run emule or bittorrent. In fact I do not run any bandwidth intensive applications. I have powered up the PC and not do anything and seen this problem happen. At least my problem is not bandwidth related. |
|
 nickzIn A Past Life I Was AstroguyPremium
join:2001-12-04
Hammond, IN | reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issue BEFSR41 v2 1.44.2
ISP WOW Internet
CM: Scientific Atlanta Webstar DPX100
Has happened twice in past 2 weeks. Never happened before. When it locks up, everything on the router looks normal, but is is no longer pingable (from the LAN) and I cannot access the config page. Power cycling router restores connectivity.
Have noticed a significant increase in incoming connection attempts in log in the same time period. |
|
| reply to x062pea
Linksys BEFSR41, original
Firmware: 1.45.7
Comcast Cable, ex-attbi area
3Com Home Connect 3cr29220
- Started in last 2 weeks. Has happened about 5 times.
- Rebooting modem alone doesn't fix it
- Diag light has come on one time
- MTU is disabled
- Router is 4+ years old
When router stops functioning:
- Cannot ping its LAN IP
- Cannot access http router pages
- Can seem to ping through to other parts of network
- Power cycle of router fixes problem |
|
 DR_JAY
join:2002-04-23
Verdun, QC | Linksys BEFSR41 V1 Original
Firmware: 1.40.2 (most stable for this router)
Cogeco High Speed Internet
-Started since Feb. 2003 (no kidding!) and I always have to reboot the damn thing every 2-3 weeks. If lucky, 1 month
-Purchased router back in 1999
--
Dr. Phil's Words of Wisdom: Get Horny and Call Me |
|
| reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issues? BEFSR41 v2.. started about late-feb/early march [as i noticed...]
Comcast cable @ linksys's own cable modem [the only one they make - it sucks] |
|
 cow116Cisco KidPremium
join:2003-03-10
Indianapolis, IN
1 edit | reply to ZeitgeistJ
Mediacom
BEFSR41 v2
1.45.7 or whatever the lastest one that causes the most problems recently
Motorola 4100 modem |
|
 ChrisDATGoogle Keyword Compsysnyc
join:2002-02-26
Hollis, NY | reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issue That's a lot of cable broadband -- Anyone with DSL/PPPoE?
BEFSR41v2, FW 1.45.7
Verizon DSL [MTU=1492, Dial On Demand Max Idle Time=0]
Westell Wirespeed Modem B90-36R515-01
*No problems +[real old] 10BaseT hub between modem and router. |
|
| reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issues? I have been having this problem with both a BEFSR11 ver. 1 and a BEFSR41 ver. 2. using ver 1.45.7. Dropping it back down to 1.44.2 seems to have worked.
BEFSR11 v1 / BEFSR41 v2 - 1.45.7
ISP - Comcast
Motorola Surfboard 4100 |
|
| reply to ZeitgeistJ
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. |
|
| reply to ZeitgeistJ
befsr41 v2 1.45.7
cable comcast
rca modem
problem really became noticable 4 days ago. Been running 1.45.7 for months. Have downgraded to 1.44.2 to see if it helps per some other posts. Same symptoms. All internal to linksys still works. Not able to ping it or access its web pages. Reboot of modem does not help. Reboot of router always helps. Tested with no load overnight - all PCs off - same thing happened. Saw post with linksys saying it was comcast... looks like a lot of non-comcast with same problems tho... |
|
| reply to CatchingSpy
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. |
|
