| reply to RUdude0884a
Re: Firmware 1.45.11 for BEFSR41 (v1 and v2) What is all this stuff about disconnects? It doesn't seem to be happening to me. How do you know when it disconnects? Doesn't the stay alive feature keep you connected? |
|
 scarneyBbr Team Discovery - Bbr Team Rc5Premium
join:2001-02-18
Madison, WI | reply to stealth29206
probably due to different hardware used. these companies tend to buy the cheapest parts they can to keep profits up.. |
|
| reply to rwinegar6
You know if your disconnected because you can't access the internet or anything else connected to your router. I was fine until the 145.7 problems started. So far so good with the new one. I also was never able to downgrade any earlier than 145.6. If this doesn't work, I'll have to get a different brand router.
--
Charter Cable, 1500/128, XP Professional, Motorola 4100 modem. |
|
| reply to RUdude0884a
BEFSR41 ver 1 Firmware 1.45.11
I used to get DHCP leases for 1 hour and had to manually renew it to stay connected.
I did a hardware reset (hold pin down, power off/on) followed by setting the router to factory defaults. Now the DHCP leases are for 24 hours. Maybe the problem is fixed?
Try a hardware reset. Remember to reset the password to something complex (don't leave it at default).
Aloke |
|
 TexasGuy49 States And TexasPremium
join:2002-12-02
Houston, TX | reply to RUdude0884a
I had DHCP problems too, with every firmware. What I did was to buy a cheap Wi-Fi router and connect it to the cable modem. Then my linksys was set to be static and I connected it to the SpeedStream Wi-Fi router. Thus, linksys protects me from the Wi-Fi with another NAT f-wall and no problem with linksys - it is static. That cheap SpeedStream has no problem holding DHCP with my Toshiba modem.
--
My way of dealing with problems, ignore it and it will go away. Who drank has died, who drinks will die. Is he immortal who is sober? |
|
| im still using 1.44.2. it seems to be the most stable firmware and the new ones seem like junk. |
|
| I upgraded firmware a couple of days ago and did not experience any problems so far. After reading this thread I went to check DHCP status of my linksys and sure enough it has expired and shows remaining lease time as 0... However, my internet connection is still working fine. The thing is that even though my ISP uses DHCP to assign IPs, it uses the same IP every time. It seems to me that those who have ISPs that keep the same IPs for a customer, do not experience problems mentioned in this thread (or at least some of those problems). |
|
| reply to RUdude0884a
I upgraded to .11 from .7 over the weekend and things have been very stable. I did not have any problems with .7 so I had no reason to update to .11 except for my adventurous nature.
I have an older ver 1 router that has been working for over three years now with very few problems. My original flash was 1.2? or around there.
happy camper here....
bob |
|
|
|
 PretoriousTheres more behind the pic than the wallPremium,MVM
join:2003-01-08
kudos:1 | reply to RUdude0884a
Just for the record, I've been running the new firmware for over 48 hours now, with no problems what so ever. The only difference I can see is that my internet connection would suddenly drop and then reconnect resulting in my ip changing, this happened 2 to 3 times per day, and since the firmware upgrade in 48+ hours is hasn't done it once.
I do have static IP's assigned to all the boxes on my network, so obviously I haven't experienced the DHCP problems others are having. Sall good!  |
|
| That's good to hear. Just for the record, there are 2 DHCP settings: One is the lease time for the LAN - this you set yourself, and a WAN DHCP lease time which your ISP sets.
I asked a friend who worked in a large cable company and he says that once the lease time is up, this should not affect your connection. All it means is that if you have dynamic IPs, the next time you connect you will not necessarily get the same IP. He says in no way should an expired lease time disconnect you, and that it's more likely an ISP issue - not the router. Of course that's in theory, because if the router firmware is flawed, it could initiate a disconnection when the WAN DHCP lease expires. I will know in about 10 hours...
I emailed Linksys tech support and asked they check it out. Here the response:
"I'll be doing the best that I can to cascade your concern to our Product Support Department and I'll make sure that they address it as soon as possible. Again I would like to apologize for the inconvenience."
I hope he really does that.. |
|
| Good to know. eranros: That's interesting information from your friend. Hopefully Linksys/Cisco will truly get right on this and put out a new version soon. As it is now my WAN IP lease is exactly four hours every time I get a new one. The instant the lease counter hits 00:00:00 in the router, my connection stops working completely interupting any and all communications currently established. With a four hour lease (which is what it's always been for years now regardless of firmware version) I've had plenty of opportunities to see this bug in action (does it every time). I'm lazy and haven't gone back to 1.45.7 yet. Suppose I should, though it's already becoming habit to manually renew my WAN IP before doing anything major like downloading a big file or playing a game online.  |
|
| reply to RUdude0884a
Re: Firmware 1.45.11 for BEFSR41 (v1 and v2) I flashed to a BEFSR41 v2 from firmware 1.45.7 to 1.45.11 a couple days ago prior to going to work in the morning. When I returned from work that evening the internet was working for about 30 minutes. I had WallWatcher running and noticed all these incoming alerts in the log from Websites (Port 80) that I did not browse to. I then checked the status of the WAN IP from my ISP in the status field of the Linksys and it showed that the WAN lease time was at 00:00:00 and had not automatically renewed. My ISP WAN lease time is set for 3 hours and should have renewed the lease halfway through this time but did not. I think the reason that I had the incoming alerts in WallWatcher was probably someone had come home and powered on their computer and had got the same WAN ip from my ISP and they were the ones surfing to those Websites.
I have returned to Firmware version 1.45.7 and have been running ok for the past days. I did not have any problems with this for past months and will wait to see if Linksys will fix the problem with version 1.45.11. I do not use the default IP settings in the Linksys and I think this is a workaround for the BootP problem I think I saw mentioned here. |
|
| reply to RUdude0884a
The Inquirer Cool, thread made it onto The Inquirer:
»www.theinquirer.net/?article=16496
Maybe now Linksys will pay more attention to us now that this is getting media coverage, lol. |
|
| reply to Bogus551
Re: Firmware 1.45.11 for BEFSR41 (v1 and v2) said by Bogus551:
I installed the 1.45.11 firmware this morning on a BEFSR41 V1 and DHCP lease doesn't work automatically. When the lease expires,I have to renew it manually. On the previous drivers I would get an occasional,about every 2-3 months,lockup where my reset led would stay lit. Does anyone know anything about this?
I have the same problem too. |
|
 griff99Premium
join:2002-12-29
Merrimack, NH | I am curious, did the people that are having problems just do a simple upgrade or did they reset to manufacturer's defaults before they did the upgrade?
In my testing of these boxes I have found that "weird" symptoms occur when I do these in place upgrades. I generally start the upgrade process with the power-off, hold down the reset button, power on while holding down for about 10 seconds. Log into the router and make sure that the unit has actually been reset, perform the upgrade, log in and make sure it is the new version, and then repeat the reset process.
The BEFSR41 v2 that I am using for testing right now has not experienced these weird DHCP issues.
As of yesterday (I am not in the office today) I had completed the security scans on the 1.44.2 firmware and although as I posted earlier Nessus showed port 1900/udp (UPnP) as being open, Nmap did not, Nmap however did show 113 as closed which was completely expected. I performed the upgrade as I described above, the only thing I changed in the settings was I disabled Multicast Passthrough and enabled the Filter port 113 options. The Nmap scan was still going when I left for the day yesterday, so I will post my results tomorrow. |
|
| reply to Sharingan
where can I get an older version of the firmware, I can't find it on Linksys' site ANYWHERE. |
|
| reply to griff99
I did the upgrade the dumb way. I simply downloaded it and installed it without doing anything to the router first. I have been running for two days with no problems whatsoever. |
|
| reply to HamHamHam
»ftp://ftp.linksys.com/pub/befsr41/
I had to dig around there last night, since this new firmware is not ready for primetime. |
|
| reply to RUdude0884a
With some testing, it is 50/50 if any problems occur if one updates the firmware and does not do a hard reboot on the router while a hard reboot ensures that the update takes completely.
Hard rebooting then making sure it has resetted to factory defaults before updating could not hurt either. |
|
| yes yes and yes, i get the same problem after my new Firmware update, in CS i get the Host_Error: userMsg: Mesage not present on client xxx
i was going nuts here because of it, now at leat i know what to do, switch to old firmware, thnx guys |
|
