Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
 ·Acanac
 ·Videotron
| [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RESULTS HERE
As many of you have found out, there is currently a new beta firmware available for the BEFSX41. It is called 1.52.0 and dated Oct 28 2004. For the keener, you should thank c0de for posting the firmware which you can find at the link below:
»[general] BEFSX41 Firmware 1.50.18 v. 1.50.9
Since this is beta material, use this firmware at your own risk. Linksys will not be providing support for this firmware. This thread was created to properly document the user's finding about this firmware. Please post all of what you find here. |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
1 edit | So far, my findings are listed below. Keep in mind that this is not an exhaustive list and that I have not tried it yet on a unit on DSL. The VPN end-point has only been exercised as a client (originating the IPSec tunnel). I will post more information as I find them.
Overall, this firmware as performed well on a unit attached to a cable modem. It is as good if not better than on 1.51.00. Let's see if we have some DSL users keen enough to run tests on their BEFSX41 on DSL.
Feature introduced by 1.52.0
- QoS
Bugs present in 1.51.00 and that have been fixed in 1.52.0
- The bug called "SNMP walk fails when DDNS is enabled" is now fixed
Bugs introduced by 1.52.0
- Some DDNS glitches exits where DynDNS.org does not always get updated (hard to diagnose)
- The new QoS feature does not seem to work reliably for me
Bugs or limitations present in 1.51.00 and that are still present in 1.52.0
- The bug called "Strange logs with VPN passthrough" is still present
- The limitation called "VPN shared secret limited to 24 characters" is still present
- The bug called "VPN broken when remote gateway set to Any" is still present
- The bug called "No connect button in manual keying" is still present
- The bug called "Some router's web page items take forever to load" is still present
- The bug called "Access to router's web pages sometimes return a blank page" is still present
- The limitation called "The 'All PCs' check box has disappeared from 'Edit List' filter dialog" is still present
- The bug called "Filter URL/KeyWord match logs are corrupted when SPI firewall is enabled" is still present
- The limitation called "Filter logs do not indicate which filter number was hit" is still present
- The bug called "Web filters causing the router to randomly reboot" is still present
- The bug called "Accessing a long URL string cause reboots" is still present
[EDIT]: As I was reminded by another user about something. I must admit I had many glitches when I upgraded from 1.51.00 to 1.52.0 even after doing a restore to factory defaults. It actually took me a few restore to factory defaults before I got this firmware stable. So be prepare to go through that pain if you are willing to give this firmware a shot. Once I was able to stabilize the firmware, it was running fine for me. |
|
ercm03
join:2004-11-21
UK
| Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RE
Well, it doesn't fix my problem in 1.51.00 with outgoing H.323 (eg, netmeeting) calls.
»[wired] BEFSX41 consistent crash
It still restarts every time 
Web login successfully from 192.168.1.3
[192.168.1.1] : System is ready.
System is warm start
Firmware Version : 1.52.0, Oct 28 2004.
WAN(DHCP) IP is X.X.X.X
Get current time from NTP server : Nov. 23 2004 Tue. 20:06:08
TCP from 192.168.1.3:3231 to Y.Y.Y.Y:1720.
[NM] H255.SETUP: lan invite wan.
[NM] H255.CONNECT: lan invite wan, .
- router now restarts
Firmware Version : 1.52.0, Oct 28 2004.
WAN(DHCP) IP is X.X.X.X
Get current time from NTP server : Nov. 23 2004 Tue. 20:08:36
TCP from Y.Y.Y.Y:1720 to 192.168.1.3:3231.
TCP from 192.168.1.3:3231 to Y.Y.Y.Y:1720.
[192.168.1.1] : System is ready.
System is warm start |
|
spsoft
join:2004-09-29
| reply to Flogator
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RESULTS HERE
Thanks for the efforts to support this firmware. But even with FW 1.52.0 it keeps giving me constantly "Invalid gateway address!" when I am tring to set Static IP internet connection type, although it is a valid. I was also have tested with v.1.51.0 and 1.50.18 and it was the same, but not with v.1.45.x, where this works!
Unfortunalely, I should revert back to my favorite firmware v.1.45.7 |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RE
Would you mind sharing with us the first two bytes of your static IP? Reason I ask is I am curious to see if that static IP you've got is a routable IP or a non-routable IP. We can deduce this information from the first two bytes of the IP address. |
|
spsoft
join:2004-09-29
| Thanks for your fast response, here is my settings for Static IP configuration:
IP address: 83.228.XXX.XXX
Subnet mask: 255.255.255.0
Default gateway: 192.168.1.1
I am using ADSL, and 192.168.1.1 is the internal IP of the ADSL. I also have tried to set to use automatic IP configuration, but the router get for default gateway the same external IP - 83.228.XXX.XXX, and probably tries to route to itself, so automatic configuration does not work for me, and the only way to get the router to work is to configurate the Default gateway manually to 192.168.1.1, that is to use Static IP configuration.
Thanks in advance! |
|
TuscanRaider
join:1999-08-14
Fountain, CO
clubs:
1 edit | reply to Flogator
quote:
Default gateway: 192.168.1.1
It appears you are using a router behind a router; your DSL "modem" is also a router. If you wish to use your current setup, change the LAN IP address on the Linksys to something totally different from 192.168.1.1. I personally use 10.0.0.1 as my Linksys' LAN IP.
You could also either remove the Linksys, or set your modem to bridged mode. |
|
spsoft
join:2004-09-29
| reply to Flogator
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RESULTS HERE
Yes, I forgot to note also that as the LAN IP of the router by default is also 192.168.1.1, I have changed it to 192.168.10.1, to avoid conflicts with the network between router and modem. I also have no control over the modem settings, as they are presetted by my ISP.
As for the above error "Invalid gateway address" which means probably that the IP of the gateway is invalid, I have also tried with other IP addresses for the gateway and it gives me constantly the same error, even I have tried to set the same configuration that the router would get through automatic IP configuration, but it won't to accept. |
|
waynebike
join:2002-07-29
Naperville, IL | reply to Flogator
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RE
anyone know if counter-strike is playable on this firmware now? |
|
drip
join:2003-04-08
Richmond, VA
4 edits | should qos packet tagging (802.1p) be enabled on the nic as well as the router to take advantage or only the router and it will handle qos itself?
edit: i tried counter strike (css) and it did not work. unreal and basic usage have been fine. no reboots and other issues as of yet. loading of the configuration pages are still slow or time out.
as for qos, it is working. the dl bit rate was more stable and had an increase in throughput (minor). |
|
Eko
Premium
join:2004-05-04
Slovenia
2 edits | reply to spsoft
said by spsoft  :As for the above error "Invalid gateway address" which means probably that the IP of the gateway is invalid, I have also tried with other IP addresses for the gateway and it gives me constantly the same error, even I have tried to set the same configuration that the router would get through automatic IP configuration, but it won't to accept. Since fw. 1.50.x Linksys introduced Java script checking of "default gateway" address against IP and network mask. Their logic is very restrictive.
The only way to set non-standard gateway is "manual" procedure. (To bypass java)
- Log into router
- Edit to your needs and copy-paste this line into your browser address line and hit Enter. (WARNING - NO ASTERISK!!)
http://192.168.10.1/Gozila.cgi?index.htm=255&txt_routerIP0=192&txt_routerIP1=168&txt_route
*rIP2=1&txt_routerIP3=1
(*) WARNING 1 long line(s) split
AliM |
|
spsoft
join:2004-09-29 | Great !!! It works now!!! Thanks  |
|
c0de
join:2004-10-14
Richmond, VA
| reply to Flogator
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RESULTS HERE
Thanks so much for the GREAT post flogator!
I have basically found that the buggiest part about the recent releases has been the VPN and I get some harsh reboots when certian Web Filtering options are selected.
Some of these "bugs" are also ISP specific from what I understand.
But only one "Crash" in my log files from what I can see. and looks like it was related to The wan dropping out to change IPs. not sure?!? |
|
Eko
Premium
join:2004-05-04
Slovenia
| reply to Flogator
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RE
Running 1.52 for 3 days without any hiccup so far. I did make some extra "restore to factory defaults" before and after upgrade, just to be sure (and following Flogator advice).
But I'm afraid there is a new bug introduced in this firmware:
Monitoring the traffic load on router with SNMP is broken, i.e. it reports traffic 10 times less then it should be.
(Flogator - please check and add this bug to your comprehensive bug list)
AliM |
|
THE_MICK
join:2004-08-22
Arroyo Grande, CA
| reply to Flogator
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RESULTS HERE
I installed 1.52 in one of my SX41's and tested it for port address translation. This is where in the UPnP menu, an incoming request on a WAN port can be translated to a different port number on the LAN side. This feature does not work in this firmware, as well as all of the 1.5xx versions. It does work in 1.45.7 however. This capability also does work in the versions of BEFSR41's I have tried.
Back to 1.45.7 for my Knoppix server use.
|
|
redblkjck
Premium
join:2001-11-07
Sanford, NC
| reply to Flogator
Ran 1.52 for 4 days.
Flashed from HTTP, all settings were stored except DDNS. It was disabled on reboot but on enabling DDNS the old settings were still there. Set Obtain IP behind Ambit cable modem, MTU 1500, SPI enabled, no filters, no QOS, DHCP enabled.
I still have failed MS OS CMD line tracerts. Other 3rd party tracert work fine. Anyone else notice this? XP Win2K all the same result. It was working without the router but I have not re-verified that since installing. It didn’t work for me with DSL or Cable.
VPN still breaks while remote set in Any, seems renew request is blocked.
IRC problem went away when I switched to cable from DSL, can't test this anymore.
No noticeable problems with DynDNS but my IP has not changed.
1.52 worked fine right away but I noticed it was blocking lots of packets, noticeable when trying to request web pages and transfers, failure. Wallwatcher was filled with red entries. This was off and on. I thought this was with my cable modem as it is having problems staying online with an IP. Rather than unhooking the router and testing the cable modem directly with a PC, I downgraded the firmware back to 1.51. After the soft reset from the flash it’s up and running again. 12 hours now and no packets are being blocked that my PCs requested. Web pages seem to be loading up fine again.
Blocked Inbound entries were followed after an Outbound request to a web site. Several DNS return entries blocked. It’s strange that I did not have any noticeable problems the first 2 days. Every few days the router seems to lock up, no response or partial response. I’ll see packets from the internal LAN IP of the cable modem being blocked Inbound port 80 in the Wallwatcher log. A hard router reset and everything is working again. If the problem is still present while using 1.51 with the packets; I’ll flash it back to 1.52 and reset the defaults for more testing.
jack |
|
hananz
join:2003-11-19
israel | had 1.52 for a week or so
worked great until started emule and nothing worked (parallel to the emule) until shutting down the emule
after downgrading to 1.45.7
using emule and everything is pefect...(allmost) |
|
st0rm82
Premium
join:2002-11-13
Quebec, QC
| reply to Flogator
im on 1.52 for about a week now..
everything seems to work fine exept MSN..
i dunno if its really related to 1.52 but my problem
started the day i flashed the firmware....
theres alot of message i send that doesnt work right away
"The following message could not be delivered to all recipients"..
tried turning uPnP off and on... same thing..
i did 3 reset/restore default, didnt help either
cant wait till linksys finally release a firmware that
will work good and be able to keep for at least 1 year..
my old netgear router seemed to have much better quality
firmware.. im thinking of changing this one if we keep
gettin wierd firmwares
how can it be so hard to test all features in a router for
them? i mean we can find the bugs so fast here, why cant they do the same? |
|
Eko
Premium
join:2004-05-04
Slovenia
2 edits | reply to Eko
Re: [wired] BEFSX41 Firmware 1.52.0 - POST YOUR RE
said by Eko :But I'm afraid there is a new bug introduced in this firmware: Monitoring the traffic load on router with SNMP is broken, i.e. it reports traffic 10 times less then it should be. Update on "SNMP sysUpTime bug":
Problem is related to router's internal timer (sysUpTime - .1.3.6.1.2.1.1.3). It runs exactly 10 times faster than normal. I found this by checking router up-time; it was surprisingly high. Over night it could be more than 5 days. Hence the low reported traffic rate; program divides "bytes transferred" by "timer difference".
This might affect QoS functionality as well. So far I couldn't make it work at all.
AliM |
|
Eko
Premium
join:2004-05-04
Slovenia
| reply to THE_MICK
said by THE_MICK :.... port address translation. This is where in the UPnP menu, an incoming request on a WAN port can be translated to a different port number on the LAN side. This feature does not work in this firmware, as well as all of the 1.5xx versions. ... It works OK for me (I have tested it on 1.51.00, 1.51.00_hb and 1.52) |
|
