 Flogator
Premium Member
join:2003-01-19
Cantley, QC |
Flogator
Premium Member
2006-May-10 9:41 pm
BEFSX41 Firmware 1.52.10 - Post your findings hereLinksys has released BEFSX41 firmware 1.52.10. If you have flashed your router with this firmware, please post your findings in this thread. Although the firmware was posted today (May 10th), the firmware is dated April 29th. As for my part, I have only verified the MSN/UPnP problem and it is still present  . MSN users will not get voice conferencing to work in this firmware. |
|
| Flogator |
Flogator
Premium Member
2006-May-10 9:43 pm
Sadly enough, whatever they fixed in UPnP isn't fixing the MSN/UPnP issue. Linksys- A Division of Cisco System, Inc.
Firmware Date : May 10, 2006
Current Firmware : Version 1.52.10
Product Part No. : BEFSX41 v1/v2/v2.1
Ver #. Date Description
--------------------------------------------------------------------------------
1.52.10 May 10, 2006 1. Fixed some online games issue.
2. Fixed for stability
3. Fixed UPnP forwarding issue.
|
|
| |
VIIV
Anon
2006-May-11 1:30 am
What about the MSN disconnection issue with the router dropping connections? I won't get a chance to flash till later next week but I'd love to know if this has indeed been fixed. |
|
| |
Lgeoff to Flogator
Anon
2006-May-11 9:29 am
to Flogator
I am having a problem with DHCP... 2 computers connected but not showing up in the DHCP Clients Table... have done a long reset, power-cycled, etc, etc. (v1 router) |
|
|
 ·Carolina Mountai..
Synology RT2600ac
Linksys E2000
1 edit |
to Flogator
Who needs Sleep? OK, running V1.52.10 as main router. PPPoE (DSL).
Am finding that Blocking by keywords/url are not reporting correctly in logs (doesn't matter if firewall is turned on or off....)
Haven't done any other tests other that to test keywords/url's and post here... Maybe tonight...
Submitted to Linksys with picture of Wallwatcher Logs |
|
Jan Janowski
3 edits |
to Flogator
Turned on all reporting...
Free memory presently 419.
Rebooted 9:02 CDST 5/11/06
Free memory 421
8:30 later 416
11 hours 44 min later 411 !!! |
|
| |
VIIV to Lgeoff
Anon
2006-May-11 11:40 am
to Lgeoff
Legoff, did you notice that DHCP bug in the previous release 1.52.9 or is it new to this firmware? Thanks, |
|
| |
Lgeoff
Anon
2006-May-11 12:15 pm
I don't know-I switched back to 1.45.7 when I had problems with Azureus/UPnP..
I can try it to see but I can't find the 1.52.9 fw anywhere |
|
| Lgeoff |
Lgeoff
Anon
2006-May-11 12:42 pm
If I disable the connection and then enable it, the computers show up right away in the Clients Table.
Here is the error I am receiving from the event log:
Your computer was not able to renew its address from the network (from the DHCP Server) ...
The following error occurred:
The semaphore timeout period has expired. . Your computer will continue to try and obtain an address on its own from the network address (DHCP) server. |
|
1 edit |
to Flogator
Initial impressions of this firmware is that it is great, P2P and other connection intensive applications that onced caused problems for me do not cause a reboot of the router. |
|
·Carolina Mountai..
Synology RT2600ac
Linksys E2000
|
to Flogator
There was someone who, when a new version of firmware came out, always did a test of the new firmware's throughput....
Anybody have the capability to do that?
No problems yet other than blocking by keyword/url as posted above). Other than re-directing to a different time server, and port forwarding UDP Port 162 for Wallwatcher, (to get through next linksys device on different IP) and PPPoE, (Using fixed IP's here) General DSL use, so far, so good. |
|
| |
VIIV
Anon
2006-May-12 1:50 am
What about dropping connections with apps like MSN, AOL IM, etc... |
|
·Carolina Mountai..
Synology RT2600ac
Linksys E2000
|
to Flogator
Response to my post and picture to Support earlier this week. Reply: Thank you for contacting Linksys Technical Support. Please accept our apology for any inconvenience this may have caused you. I was able to check your record and the last firmware you have tries is version 1.52.03. Please confirm if this is still the firmware loaded on your router or if you already tried the latest version which is 1.52.10. The latest firmware includes the fixes of the previous firmware 1.52.9 which addresses the problems with the website blocking. Just incase you are already using the latest firmware and you are still getting the same results, please provide us the following information: Hardware version: Firmware version: Network setup: Operating system: 3rd party software or hardware used: Full name: Phone number: Thank you. If you have any further questions, feel free to visit our knowledge base at » www.linksys.com/kb or send us an e-mail at support@linksys.com so that we can assist you. Once you get to the Knowledge Base section, either type in the Answer ID or the keywords under Search Text and click Search. Sincerely, Christian Lara C. Diamante Badge ID 13285 Linksys – A Division of Cisco Systems, Inc. Website: » www.linksys.comNetwork Setup: » www.linksys.com/eduThis correspondence is considered confidential and any reproduction for the purpose of public disclosure is forbidden without written permission by the author signed above. If you are not the intended recipient, please immediately notify the sender and delete any copies. Customer (Jan & Eileen) 05/11/2006 06:38 AM THe only BEFSX41 firmware that ever logged Blocking by Keyword/Url correctly was V1.45.7, and then you had to turn off the firewall in order for it to log correcly. All Versions since then just logged that something was blocked, but there is no verbose-ness to the log entry. I've been reporting this to you folks ever since V1.45.7 firmware.. Please fix this problem!!! I've replied with more information.... I hope they understand it!!! |
|
| |
to VIIV
VIIV,
The firmware seems to have fixed the dropping connections problem on my side, but throughput hasn't improved. |
|
| |
to VIIV
My Xfire still keeps dropping...
Alister |
|
| |
VIIV to zartan0
Anon
2006-May-12 3:09 pm
to zartan0
Hey Zartan0, what programs were dropping with you but have now been fixed? Is MSN one of them? Thanks, |
|
| |
to Flogator
Have tried the new firmware and it still has a memory leak that causes the router to hang every 2-3 hours when using UPnP.
Here are the stripped down logs for wallwatcher
[192.168.0.1] : System is ready
Invalid TCP packet received, dropping packet
System is warm start
Invalid TCP packet received, dropping packet
Firmware Version : 1.52.10, Apr 29 2006
sizeof( NV_data ) = 32764
[versoin] : 1.52.10(0xd507d1), Apr 29 2006
MTU = 1500
[0:00:00] real_free=421(421),free=421,alloc=179,rel=0,wt=0
uiCorpCurCtrs=0(1300),uiExtCurCtrs=0(1100)
HB default connection(-12) and port(1050)
--> UPnP_flag Port 5678 => 27922 SYN
--> UPnP_flag Port 5678 => 63762 SYN
--> UPnP_flag Port 5678 reject!!
--> UPnP_flag Port 5678 => 64018 SYN
--> UPnP_flag Port 5678 => 64274 SYN
--> UPnP_flag Port 5678 => 64530 SYN
--> UPnP_flag Port 5678 => 64786 SYN
--> UPnP_flag Port 5678 => 65042 SYN
--> UPnP_flag Port 5678 reject!!
HB to dhcp server connection(-12) and port(1050)
--> UPnP_flag Port 5678 => 65298 SYN
--> UPnP_flag Port 5678 => 19 SYN
HB connection(-12) and port(1050)
[0:00:30] real_free=415(415),free=415,alloc=182,rel=0,wt=3
UPnPAdvertise!!continue
--> UPnP_flag Port 5678 reject!!
--> UPnP_flag Port 5678 reject!!
WAN IP= xx.xx.xx.xx
WAN LeaseTime=15397 sec
WAN(HBS) IP is xx.xx.xx.xx
Get IP= xx.xx.xx.xx
--> UPnP_flag Port 5678 reject!!
HB default connection(12) and port(1052)
HB: Tx protocol negotiation(7).
HB: Rx protocol negotiation(15).
[0:01:00] real_free=412(412),free=412,alloc=182,rel=0,wt=6
[0:01:30] real_free=410(410),free=410,alloc=184,rel=0,wt=6
[0:02:00] real_free=409(409),free=409,alloc=185,rel=0,wt=6
[0:02:30] real_free=407(407),free=407,alloc=187,rel=0,wt=6
[0:03:00] real_free=406(406),free=406,alloc=188,rel=0,wt=6
[0:03:30] real_free=405(405),free=405,alloc=189,rel=0,wt=6
[0:04:00] real_free=403(403),free=403,alloc=191,rel=0,wt=6
[1:40:00] real_free=118(118),free=118,alloc=476,rel=0,wt=6
[1:40:30] real_free=115(115),free=115,alloc=479,rel=0,wt=6
[1:41:30] real_free=112(112),free=112,alloc=482,rel=0,wt=6
[1:42:00] real_free=112(112),free=112,alloc=482,rel=0,wt=6
[1:42:30] real_free=109(109),free=109,alloc=485,rel=0,wt=6
[1:43:00] real_free=109(109),free=109,alloc=485,rel=0,wt=6
[1:43:30] real_free=106(106),free=105,alloc=488,rel=1,wt=6
[1:44:00] real_free=106(106),free=106,alloc=488,rel=0,wt=6
[1:53:30] real_free=76(76),free=76,alloc=518,rel=0,wt=6
[1:54:00] real_free=76(76),free=76,alloc=518,rel=0,wt=6
Note: that after 1 hour 54 minutes the free resource has dropped from 421 to 76. The resource is being consumed at a rate around 1-2 per 30 seconds.
This behaviour can be seen if UPnP clients such as MSN are active.
Cheers
Peter |
|
 Dustyn
Premium Member
join:2003-02-26
Ontario, CAN
3 edits |
to Flogator
Damn. The UPnP memory leak is still present when UPnP is enabled in the router and with XP UPnP Framework enabled in Windows XP SP2. |
|
| |
to Flogator
maybe we should ALL submit support emails to At least it would make us feel better! |
|
| |
to VIIV
Viiv, yea MSN was one of them. That, IRC, and AIM. |
|
| |
linksysguy2 to Flogator
Anon
2006-May-13 9:45 pm
to Flogator
Hi,
I just installed the version 10. So for it fixes the it seems to work OK. I at least get the traps. |
|
 jansm38Vn800-B
Premium Member
join:2003-05-19
Blackwood, NJ |
to Flogator
I installed 1.52.10 tonight and found that there is still a problem that I saw in 1.52.9
It seems that certain filter rules based on port blocking causes the router to reboot and go into the flashing red light syndrome. This seems to happen most if I have a rule that blocks 2 IP's from using port 80 and any other rule set up. Just the port 80 block alone does not seem to cause the problem.
I want to downgrade to 1.45.7 but can't seem to find the link anywhere here, I know it's posted somewhere, I just can't find it. Can someone (Flogator?) point me in the right direction?
The version I liked best was 1.44.3, this was the last version that had any semblence of real filter rules. You could block incoming traffic as well as outbound.
Thanks. |
|
Dustyn
Premium Member
join:2003-02-26
Ontario, CAN  ·Carry Telecom
·TekSavvy Cable
Asus GT-AX11000
Technicolor TC4400
|
Dustyn
Premium Member
2006-May-14 12:46 am
|
|
| |
to jansm38
Jansm3, I had to downgrade to 1.51.00_HB, however during the downgrade the router crashed. @%$#... Fortunately I had read other post and I had a copy of the befsx41_Tftp.exe file which I had to use to install the older firmware. The file is available at » ftp:// ftp.linksys.com/pub/network/NOTE: I had to do several loooong resets (hold the reset button on the back for 30-40 seconds until the red light blinks once). I also had to try it several times. Remember the factory admin password is adminIn the end I had to go all the way back to 1.45.7 then upgrade using befsx41_Tftp.exe to 1.51.00_HB. Make sure you have all these files before you attempt a downgrade. Good luck, and may the Force be with you [because Linksys support, may not] Peter |
|
jansm38Vn800-B
Premium Member
join:2003-05-19
Blackwood, NJ |
jansm38
Premium Member
2006-May-14 2:55 am
Thanks for the heads up and thank you Dustyn for the link. In the end I found that port blocking in the filters does not work at all in 1.45.7 so now I'm back to 1.44.8. I like the filtering in 1.44.8 much better than newer versions because it allows you to setup incoming filter rules and not just outbound rules. (in my previous post I mistakenly said 1.44.3). The reason I need to block port 80 outbound on certain IP's is so that I can force my kids computers to have to use my proxy machine. The proxy is running Proxomitron and does heavy duty web filtering for me. To echo the sentiments of most SX41 users, I really wish Linksys would finally get the code right or just build a new firewall router from scratch rather than just keep patching this bug riddled box. said by peterjbrock:Jansm3, I had to downgrade to 1.51.00_HB, however during the downgrade the router crashed. @%$#... Fortunately I had read other post and I had a copy of the befsx41_Tftp.exe file which I had to use to install the older firmware. The file is available at » ftp:// ftp.linksys.com/pub/network/NOTE: I had to do several loooong resets (hold the reset button on the back for 30-40 seconds until the red light blinks once). I also had to try it several times. Remember the factory admin password is adminIn the end I had to go all the way back to 1.45.7 then upgrade using befsx41_Tftp.exe to 1.51.00_HB. Make sure you have all these files before you attempt a downgrade. Good luck, and may the Force be with you [because Linksys support, may not] Peter |
|
·Carolina Mountai..
Synology RT2600ac
Linksys E2000
1 edit |
to Flogator
I've received multiple emails from Linksys indicating that I didn't put text in the correct location for their (Must Be 'Automated') "Incorrect Answer" response system...
I've put the answer at the top, in between the two "Enter reply here" areas; In both "Enter reply here" areas, in the bottom of the "Enter reply here" areas.... In ALL AREAS.......
Remember my first posting: "Ever Since V1.45.7 all Blocking by Keyword/urls are not verbose in the logs (Linksys or Wallwatcher) (Followed by list of ALL firmewares that is in between V1.45.7 and V1.52.10, including beta's....)
There answer:
"We want to verify that you have tried, V1.52.10, where blocking by keyword/url has been fixed from V1.52.9"
HUH? HELLO!!! ANYBODY THERE????
P.S. I particularly like the part where they politely try and pass the buck to Wallwatcher...
"Kindly confirm if you have tried using firmware version 1.52.10. With the attachment you have provided, you are using another log viewer software. Did you try using the Linksys log viewer as well and check if you will experience the same problem? If you happen to be using the latest firmware and have tried using the log viewer from Linksys, but still get the same results, please complete the requested information below:" (Yes, I replied with the information)..... |
|
| Jan Janowski |
to Flogator
Just re-submitted to Linksys, with more pictures of problem...
Ever since V1.45.7 (which needed Advanced Firewall to be turned off in order to work correctly) Blocking by Keyword/URL is NOT being logged correctly in Linksys or 3rd party Logging programs (For example: Wallwatcher). THIS HAS BEEN REPORTED TO LINKSYS MULTIPLE TIMES!!!!
I WOULD APPRECIATE IT IF THIS WOULD BE FIXED...
You have no idea WHICH Blocking by keyword entry has been triggered by the logs (SEE ATTACHMENTS)....
Seeing that this has gone on for YEARS now, and I, (and others) have been reporting this for YEARS now.... Do you think you can address this in your next firmware release?
It's been broke in EVERY Release & Beta Release for the BEFSX41 since V1.45.7 It is broke in EVERY RELEASE & BETA RELEASE FOR THE BEFSX41 SINCE V1.45.7
It's been broke in EVERY Release & Beta Release for the BEFSX41 since V1.45.7 It is broke in EVERY RELEASE & BETA RELEASE FOR THE BEFSX41 SINCE V1.45.7
It's been broke in EVERY Release & Beta Release for the BEFSX41 since V1.45.7 It is broke in EVERY RELEASE & BETA RELEASE FOR THE BEFSX41 SINCE V1.45.7
It's been broke in EVERY Release & Beta Release for the BEFSX41 since V1.45.7 It is broke in EVERY RELEASE & BETA RELEASE FOR THE BEFSX41 SINCE V1.45.7
Sinscerely
Jan Janowski |
|
| Jan Janowski |
to Flogator
Here's the pictures I included to Linksys. |
|
Jan Janowski
2 edits |
to Flogator
FYI:
Today I added the following two names into my blocking by keyword/url list in Linky router...
addynamix
ru4
Since then, can't get to ebay.
I'd be able to tell you which it was, if the entry in Logs was verbose enough to tell me!!!
I get the names by running Ad-Aware, and then examining the names of the spyware, and entering them into BEFSX41 in Blocking by Keyword/URL...
P.P.S.: I have 2 BEFSX41's in series (one just for NAT, and to increase the number of Spyware blocks) This second unit uses V1.45.7 and DOES report the spyware names...
I wish someone from Linksys would read these threads, like I believe they did a couple years ago!!! |
|
| |
VIIV to Flogator
Anon
2006-May-14 2:30 pm
to Flogator
Oh man, I just upgraded to the new 1.52.10 and MSN Messenger still drops the connection after 5 minutes. MAD |
|
. MSN users will not get voice conferencing to work in this firmware.
·
·
