spudrum
@ntl.c
| reply to KD_anon
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE
well hopefully i am not the only person experiencing the following problem with the linksys 1.50.18 firmware anyway here goes...
The problem i have is that i temporarily lose the connection/get timeouts when using various applications, such as Msn Messenger/ TeamSpeak/Raven Shield and my VPN Client.....
This problem only occurs when i have the router firewall set to 'enabled'....when i set it to 'disabled' i have no timeout or disconnect problems....i am using the built in DHCP server with the client lease time set to 0 (the default)
so just to clarify currently in order to maintain the connectino to a number of applicatinos i use i use the following firewall settings on the router...
Firewall: Disabled
Block Anonymous Internet Requests: Disabled
Filter Multicast:Enabled
Filter Internet NAT Redirection: Enabled
Filter IDENT(Port 113): Disabled
i have tried disabling both the 'Filter Multicast' and 'Filter NAT' but they don't make any difference....
i have read through the Linksys Knowledge Base FAQ Questions and none of the suggested answers apply to my situation
i also use the ZoneAlarm firewall and have tried turning it on/off and changing the various zone options but i still have the same problem... |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
 ·Acanac
 ·Videotron
| reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
For the users still having problem with firmware 1.50.18, may I ask you try latest firmware 1.51.00 and post your findings in its respective thread. You can find both a link to the 1.51.00 firmware as well as the actual discussion at the link below:
»[wired] BEFSX41 Firmware 1.51.00 - POST YOUR RESULTS HERE |
|
griff99
Premium
join:2002-12-29
Merrimack, NH
| reply to arclight9
I just installed 1.51 and no problems here. The management pages still seem to load very slowly but I guess I can live with that. In addition I have no problems with those long links. I am a DSL customer, perhaps this long link thing is only related to some types of ISPs or some type of interface hardware? Just for reference my DSL modem is a Paradyne 6371, this unit is actually a router too but my ISP doesn't let me configure it as such hence the Linksys. Thanks again Flogator. |
|
Mjah
@heima.is
| reply to spudrum
Spudrum,
I also experience that problem, but not only with the 1.50.18 firmware. It happens as well with the 1.45.7 firmware.
All is fine until I turn on SPI. After roughtly 10-20 minutes my connection idles out completely, no matter what app I use.
The connection to my dsl modem is still up according to the router pages.
As of yet I have not managed to find out why it happens either  |
|
Morbid Angel
Bitten By The Wolf
Premium
join:2002-12-12
Bethpage, NY
|  reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE
I had to downgrade the firmware to the 1.45.7.
I had nothing but disconnect problems like crazy like every 50 mins or so with the 1.50.18
Since I have downgraded the firmware my connection has not gone down yet, going on over a week so far. Until Linksys ever decides to test their firmware updates before releasing them, then I shall considering doing it. Thanks to this forum I can read up on updates before installing them, thanks guys.
--
Downtown, DEATH METAL SHOWS RULE \m/
Morbid Crap
Forum Posts:1685 |
|
Blue-Steel
@cable.rogers
| Check this out : i have the remote administration of my router disabled and yet ... i can access to it online.
another thing is that i think that ftp services are affected with this last firmware.also my downloads stop sometimes and this wan not happening before like this. |
|
redblkjck
Premium
join:2001-11-07
Sanford, NC
| reply to Flogator
I'll just add on to what some have stated, confirm the same issues.
IRC consistent drops connections (SSL). Try and tracert from cmd line router drops my connection and hangs for a bit before it connects again. I think it does a soft reboot. I can't connect to web consol for a few sec then the PPPoE hangs for a few trying to reconnect. DSL, MTU set greyed out to default 1492. Enable it, set manual to 1492 drops connection left and right. Leave it alone greyed out I stay somewhat connected, just no tracert. VPN IPSec pass thru works fine for me. Have not tested the hardware VPN side yet with this firmware. No need to yet.
jack |
|
kevdog9
join:2003-09-25
| reply to Flogator
I get router reboots when i do a trace route also. Also with AIM and MSN Messenger, i get a lot of dropped packets in the firewall. Kills My AIM connection quite a bit, sometimes from every 10-20 mins to every 1-2 hours. Also kills msn messenger connection, although, not quite as often. |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC | Firmware 1.51.00 fixes the trace route problem. Please try it out.
»[wired] BEFSX41 Firmware 1.51.00 - POST YOUR RESULTS HERE |
|
aaack
| reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
The first thing I did when I bought 2 of these was update to 1.50.18 (as available on Linksys' website). What a mistake. My IRC connections would drop in about five minutes unless I was speaking continuously (normally I idle on IRC 24/7). Behind the second router IRC connections got dropped even with that machine on DMZ (!) All the servers on that machine were working OK though...
Flogator, you have it right about tech support - First tech support person said to disable "Block WAN request". That did nothing. Second tech support person said to change MTU to 1472. Enabling MTU stopped all WAN routing no matter what number was used. The argument about opening port(s) for IRC was hilarious. At one point they told me to exchange the router (yeah right, I have two and they both do it). I asked if they were telling me to return it and go back to my SMC router that worked fine, or to buy a different brand. Heh.
The MTU clue led here where I found 1.45.7 which is working well and entirely stable.
Props to Flogator for making the good firmware available. |
|
magore
join:2004-05-30
Waterloo, ON |  reply to Flogator
I can confirm that 1.50.18 breaks pasv ftp. Reverting to 1.45.7 fixes the problem
Setting the MTU to a manual setting breaks DNS lookups |
|
WRainman
@verizon.ne
| reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE
I have had somewhat similar results. Have several computer behind the BEFSX41. One all of a sudden stopped browsing the internet. It had worked fine since March of 2003. I have verizon dsl w/ pppoe. All other PCs could still use the net. The broken one could ping, telnet, and use AOL IM.
Upgraded the firmware to the newest (.18) and reset to factory defaults. Still has the same issue. One PC doesn't work... all others do.
Linksys wouldn't admit it was thier problem. Even when the PC worked connected directly to the modem, or when i took it in to work, or when i used a dlink router.
I find it odd that it is only on 1 of my pc's not all of them.
I have formatted and reinstalled a clean w2k pro on that box... still doesn't work! |
|
bentright
@l-3com.com
| reply to Flogator
I just upgraded a BEFSX41 from 1.45.3 to 1.50.18. The new look was nice, but I started having troubles with video chat cams freezing intermittently on jmeeting and paltalk services. Also noted a date in one of the router logs as 06/32/2004 instead of 05/31/2004. No other problems were noted. When I replaced the upgraded router with one running the 1.45.x firmware, all back to normal (no intermittent cam freezes). |
|
MonkeyBoy666
join:2004-04-21
Palatine, IL
| reply to Mjah
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
When I upgraded to 1.50.18 my firmware settings were seriously off, particularly VPN settings. In addition, the router was problematic with SPI enabled. Only by resetting to factory defaults and inputting all new values was I able to get it working again.
I don't believe settings are transferring properly from 1.4, as this same thing has occurred with 2 other people who upgraded to 1.50.18 (one using the 1.4 web upgrade, the other using their upgrade utility). I would seriously recommend doing a factory reset before writing off 1.5 altogether.
On the plus side VPN is much more reliable. Instead of getting into a strange hung state where the BEFSX41 thinks the VPN tunnel is up when it's actually down (in effect all packets to/from the remote network are dropped by the BEFSX41), then rebooting when you manually disconnect/connect, it seems to reboot itself whenever instead of getting into that strange state. I think. Maybe it's just plain not getting into that state - I never notice it rebooting, and haven't had to futz with it since upgrading. Thank god. |
|
KevinCCNA
@verizon.net
| reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE
I updated two BEFSX41 routers with the 1.50.18 firmware. To put it in layman's terms, "they're really screwed up now." One passes traffic intermittently. The other allows pings by IP address, but not by FQDN. It won't let me do HTTP at all. I upgraded the first BEFSx41 because it had really old firmware. I upgraded the second BEFSX41 to see if the new firmware was causing problems. I tested the second BEFSX41 before I upgraded it, and it was working perfectly. |
|
bob-oh
@insightBB.com
| reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
I have had this installed for a week now and have not had any of the problems decribed here.
I updated from 1.44.3 to 1.50.18
I had a slight problem connecting to the net till I recloned the mac address.
I have four computers 2 xp 2 linux boxes connected via cable
I tried the traceroute with no problems, and the long urls with all the boxes no reboot... mric and aim work fine,
My son lives on aim and has reported no problems...
kazza lite++ works as usual maybe a little slower.. I dont use it much anymore...
the only problem I have discovered is using cuteftp to ftp to the linux boxes via ssh2 dosent work but that may be because I upgraded to fedora2 from rh9, I'm not done testing yet.
Sorry to hear so many have problems with this and thumbs up to those working very hard to help those that are having troubles...
I'm very new to the router scene and am just a monkey pushing buttons and got lucky I suppose. |
|
digrun2
@ntl.com | reply to BillRoland
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE
Did the same for me.. everytime I turned the WAP on or a wireless enabled PC either the router rebooted or the browsing was kaput. Disabling the nic and re-enabling it sometimes worked. A veritable crock of s**t |
|
homebrewmike
join:2004-06-05
Saint Paul, MN
| reply to Flogator
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
Flogator-
>After your upgrade, did you rebooted all of your PCs?
> One of the common problem is about DHCP leases conflicts
> in between router reboots.
All of the machines in the network use static IP's. After poking around here, I noticed that people were changing their MTUs - so I tried that (used 1492 per some link.)
No dice.
So, I ended up going to a previous version of the FW (what the thing shipped with.)
I'm now trying 1.51.00 - seems to be ok so far - the machines on my network all seem to be able to see the "blacked out" sites.
Thanks! |
|
Fenix1
@4.15.x.x
| reply to BillRoland
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE
It's this is all beginning to happen all of a sudden. I had used 1.50.18 with no problems what so ever (although I never tried a tracerout before with it.) Having exausted all avenues and gone nuts! Given the timing of it all, with the recent Sisco leak, I'm beginning to wonder if we have a 'new' class of 'viruses' now, router viruses? Only Linksys can tell, but will they? |
|
mike foobar
@verizon.n
| reply to Webmeisterus
Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
1.50.18 does not allow me to ftp to ftp.linksys.com/pub/network and do an ls. Also, can't access »www.nws.noaa.gov.
Fell back to 1.50.9 before reading this newsgroup. Perhaps should fall back more to 1.45.3 (don't have 1.45.7).
Traceroute fails to the wan in 1.50.9, but does NOT crash the router.
Good luck all.
-Mike |
|
