| reply to ChrisDAT
Re: So, Linksys can we get a word on BEFSR41 issue I have BEFSR41 v1 with 1.45.7 firmware and USR CMX modem, on Comcast.
I upgraded the firmware within last 1-2 weeks to fix the problem. I had been using firmware from 2000, and had disconnect and router freezing problems.
I still have the problem. Things look like they should work, but they don't. Sometimes the router red DIAG led is on. Past few days the first PC turned on cannot connect, and I can't ping the router. Power cycling is a temporary fix, til the next day.
There is not much heat coming from the router, and all the vents are clear. It is located in a cool, dry basement.
Before downgrading, I am going to try a reset. I did not do that after the firmware upgrade.
At this point, I have to guess that some type of incoming traffic is at fault, and the Linksys cannot handle it properly.
I see incoming attempts every ten minutes or so from various IPs, attempting to connect to different ports. |
|
| reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issues? When problems like this occur, people try things, and make comments.
It is possible that heat buildup could cause problems. In this case it is unlikely.
I also read a post where someone suggested power problems. But some have UPS installed, and still there is a BEFSR problem.
Still, I took time to unplug everything and check the outlets for voltage. I did find that the router was no longer plugged into my surge strip, but had somehow plugged itself into the wall outlet.
It is worth checking out each idea. |
|
approval from:
golden eagle 
| reply to ZeitgeistJ
This is my original post in the "comp.dcom.modems.cable" newsgroup on 3/15/04.....
Long story - please read on and be patient....
For years I have been using a Surfboard 4100 Cable Modem connected to Linksys BEFSR11 router. The router is then connected to a Dell PowerConnect 16 port 10/100 switch....that everything else is connected to. The PCs,
print servers, etc, use a mix of static TCP/IP address and DHCP assigned TCP/IP addresses from the router.
It seems like over the last few months (along the same time frame I was upgraded to 3 mbps) I stared having an interment problem. About once a day - everything freezes up. I cannot get to the internet, I cannot send/get mail, I cannot update newsgroups.....BUT I also cannot get to the
cable modem 192.168.100.1, AND I cannot get to the router 192.168.1.1. Al the lights on the cable modem, router and switch look normal at this point - and I even see the activity light blinking on both the cable modem and the
router - even thought the PC's can only see the LAN side.
The solution has been to turn off the switch on the power bar - which kills power to the cable modem, the router, and the switch - I then wait 10 seconds - and turn everything back on. By the time I walk from the basement
back up to my home office - everything is back to normal.
Today I swapped out the BEFSR11 ver. 1 with a BEFSR41 ver.2 that I borrowed from a friend. Same thing happened today, and the same solution fixed the problems.
Since I cannot get to the router - the problem is either the router or the switch. I have eliminated the switch because everything on the network can see and communicate to each other....so that leaves the router.
Both routers are running the most current firmware - 1.45.7, Jul 31 2003. I cannot remember when I updated the firmware last - but it would have been in the fall some time - long before this problem started to occur.
Has anyone seen anything like this before? My next step is to downgrade the firmware - but to what version? 1.45.6 or 1.44.2 or 1.44 ?
P.S. I did call Comcast because I saw some odd entries (Unit Update - Not updating. This image is not for this platform) in my cable modem log after turning it on. He said 1) don't worry about the odd entries, and 2) using a
router? Eliminate the router and direct connect, and call back if you see the problem.
P.S.S. This router is sitting on a shelf in the basement - cool, dry area...no heat problems
P.S.S.S. I dropped the firmware down to 1.44.2 and it seems better - no problems in the last 2 days. |
|
 ChrisDATGoogle Keyword Compsysnyc
join:2002-02-26
Hollis, NY | reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issue I agree with both ZeitG and alluviun -- There are two ways to approach this issue... Let's agree the LinkSys is at fault -- Then what? Option 1, would be to flame the boards, and wait for LinkSys to do something and in the meantime get a router from another vendor. Option 2, is to aggressively attempt to determine the cause by looking for a common thread, then try to work around the issue until LinkSys can read all of the info and produce a suitable fix.
Option 2 is the way I would apporach it -- For example -- Let's assume that we conclude that the LinkSys is succeptable to internet borne attacks. What can you do about it? If the succeptability is due to insufficient buffering, you would think that the only fix is a firmware upgrade, but that is not the case. The MTU determines not only the max size of packets that the router will recieve and send, it may also determine the number of buffers that the LinkSys will create for incoming data. Decreasing the size of the buffers, by lowering the MTU, can allow the LinkSys to recieve more packets and thus possibly prevent a buffer overflow between it and the modem. An MTU of 576 may allow the LinkSys to buffer almost three times as many packets as before [in the same buffer space], and since the MTU is so small, mal-formed packets, targeted at overflowing buffers, will hopefully fail fragmentation, and be truncated by the LinkSys. Now I realize that performance will decrease with such a small MTU, but unfortunately, security and performance are almost always mutually exclusive... You'll have to decide, lose a little performance, but stay running 24/7, or go for max performance, and wait for a firmware upgrade.
I have used different sized MTU values on the LinkSys, and it's interesting how the characteristics of your internet conection change with different values -- When I use 576, and I have no incoming clients, there is only a small performance difference [decrease] from a 1492 MTU, however when my outbound is under load [upload], the smaller MTU allows me to browse better, and my ShoutCAST listeners experience fewer "skips" than when I have the higher MTU, I can also support more HTTP clients concurrently downloading binaries with the lower MTU -- I also make sure that when I change the router's MTU, I always adjust the TCP Recieve Window on the PCs to be an exact multiple of the MSS [MTU-40]. It also goes without saying that any machine that needs to "talk" through any LinkSys must have "Max Path MTU Discovery" ON [or an MTU less than or equal to the MTU on the LinkSys] -- The lower MTU is less efficient, and will test worse in speedtests, but because the smaller MTU requires more flow and error "control" data, this increases stability and reliability.
You don't have to try this if you feel you can't afford the performance hit, but you'll never know if it helps your issue if you don't try. |
|
 Noley
join:2001-01-22
Tallahassee, FL | reply to ZeitgeistJ
Re: So, Linksys can we get a word on BEFSR41 issues? So what is everyone's recommendation? Downgrade to 1.44.2? |
|
|
|
| I skimmed through his pretty quick, so if this has been suggested already then I am sorry for the redundancy.
I have several networks around town using this router. I have found that an IP Scheme change helps a lot.
I have been running 10.10.0.1, but I let my server handle DHCP, and rarely have the problem of disconnects on cable modems.
On my peer to peer networks, I maintain the IP change, but statically assign the adresses.
I still get disconnects with DSL, but I believe it is because of DNS issues with SBC/Ameritech conflicting with the DNS of my servers.
Hope this helps.
tab |
|
| reply to ChrisDAT
Re: So, Linksys can we get a word on BEFSR41 issue MTU setting is disabled. What value is the BEFSR using in this case? |
|
 nycdavePremium,MVM
join:1999-11-16
Melville, NY
kudos:7
1 edit | This Issue Seems To Be Worse On Cable All,
I've read other threads here about the Linksys problem, and one thing that caught my attention was a post in the RoadRunner forum about a DOCSIS upgrade that might have caused certain routers to behave abnormally. Anyone else heard about a DOCSIS upgrade causing these issues with cable modem/broadband router combinations?
Here is the link to the RR thread:
»Can't Use Linksys Router Anymore TWC SI NYC |
|
ChrisDATGoogle Keyword Compsysnyc
join:2002-02-26
Hollis, NY | reply to alluvium
Re: So, Linksys can we get a word on BEFSR41 issue When the LinkSys MTU setting is disabled it defaults to 1500. What would be a substantial improvement is if "disabled" would enable the max path MTU discovery algorithm. |
|
 CorvusFlaming Tards Since 2003Premium,VIP
join:2003-11-26 | 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 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 ******** |
|
| reply to ZeitgeistJ
I had the same problem, setting my NICsto 10Mbit half helped a little, butt putting a 10/100 switch between my cable modem and router solved the problem completely.
My guess is that the linksys has trouble switching between 10 and 100 Mbit.
»[wired] BFSR41 v3 - possible solution !!! for more .nfo |
|
CorvusFlaming Tards Since 2003Premium,VIP
join:2003-11-26 | I'll try the switch right now. |
|
| I have a BEFSX41 at home. It will restart it's self for no reason at all. We have the latest firmware update. Also we are using Comcast Cable. |
|
DodgePremium
join:2002-11-27 | reply to ZeitgeistJ
I have a BEFSR41 V2, I did have all these problems described here about a year (maybe less ago) when I switched to 1.45 (or whatever the latest one is). After I switched to that firmware the router just went insane, it had to be shut off and back on several times a day that was on RoadRunner. The while the firmware was still on the latest one I moved to OOL area, and the router refused to work at all!! I switched the firmware back to 1.44.2 and it works perfectly did not have to reset it in almost 7 months now. |
|
 DavidNow accepting new patientsPremium,VIP
join:2002-05-30
Granite City, IL
kudos:70
·AT&T Southwest
 ·DIRECTV
·AT&T Midwest
 ·Google Voice
| reply to ZeitgeistJ
The only issue I have with the BEFRS41 was the FTP issue that was never resolved. I had to downgrade the firmware to get a FTP to load.
--
Give a man a fish and you feed him for a day. Teach him how to fish and you feed him for a lifetime - Lao Tzu |
|
 hqh510
join:2001-03-24
Manassas, VA | reply to SkaarjMaster
Don't forget the classical and legendary v1. 
said by SkaarjMaster:
Yep, looks like new firmware is needed on the v2 and v3. Any idea on when this might be released?
--
HQH
===
My website; DLink DI-624,DWL-G520,DWL-G650 Super G Performances; BEFSR41 Setup Guide:»www.geocities.com/hqh51/ |
|
hqh510
join:2001-03-24
Manassas, VA | reply to x062pea
Router make/model and firmare version:
Linksys BEFSR41 version 1, firmwares 1.44.2 & 1.45.7
ISP type and provider:
Cable, Comcast
Cable Modem make/model:
Motorola SURFBoard 4100
--
HQH
===
My website; DLink DI-624,DWL-G520,DWL-G650 Super G Performances; BEFSR41 Setup Guide:»www.geocities.com/hqh51/ |
|
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/ |
|
hqh510
join:2001-03-24
Manassas, VA | reply to klam2002
I know mine isn't running hot. My basement stays cool all year round and it's been down there ever since. Why start to reboot now? It's not because of temperature. Heck, it's still winter here!
said by klam2002:
Has anybody taken the routers temperature.
I have noticed that sr41 seems to run rather hot, and that as the temp rises the stability seems to drop off.:(
I just had a v2 fail through overheating and the replacement a v2.1 seems to run quite a bit cooler.
Just my 2c worth.
ANO
--
HQH
===
My website; DLink DI-624,DWL-G520,DWL-G650 Super G Performances; BEFSR41 Setup Guide:»www.geocities.com/hqh51/ |
|
