 blohner join:2002-06-26 Cortlandt Manor, NY Reviews:
·Optimum Online
·Verizon FiOS
·Google Voice
·ooma
·Vonage
| reply to Flogator
Re: BEFSX41 Firmware 1.52.3 - POST YOUR RESULTS HERE I am up and running with 1.52.3 for a week now and it behaving good. I was using 1.45.7 before but the router crashed twice recently (it didn't crash for a long time before) while having over 100 open TCP connections. It also used to slow down quite a bit with lot's of open connections. 1.52.3 seems to be more stable in that respect - and I don't get the slowdowns... Extranet VPN software clients also stay connected properly for 10+ hours... I don't use loggin, filtering or SPI so I can't speak for those features - but for now for me 1.52.3 is a go... -- I am addicted to speed --- OOL speed that is --- ~Help find a cure for cancer~Proud Member Team Discovery |
|
 | reply to Flogator
Re: BEFSX41 Firmware 1.52.3 - POST YOUR RESULTS HE I just switched to this version due to lag problems playing BF 1942. This seems much faster. Been on several hours now without a hitch. I hope i just didn't jinx myself! |
|
 | reply to Flogator I saw that hidden page info prior to removing the newer F/W, but couldn't access it. I got "Page Not Found" error. And I also corrected the typo on the original post. (.hlm, I believe it was.) |
|
 FlogatorPremium,MVM join:2003-01-19 Cantley, QC kudos:1 | I'm assuming you are using 1.52.3 right now. In this firmware, the logging hidden page is most definitively the one below:
"http://192.168.1.1/Log4Manage.htm"
You should be getting a screen that offers four check box. The one you want to add is called "System hid_log4Manage". If you are still having problem accessing the page, let us know. Obviously, you you are using a LAN IP address different from the defaults, you should adjust the above address accordingly . |
|
 | reply to Flogator
Re: BEFSX41 Firmware 1.52.3 - POST YOUR RESULTS HERE I am currently switched back to 1.45.7. I am going to either trade in my antique cable modem Saturday, or tell them to shove it. I can't deal with constantly having to reboot the darn thing. But back to the subject, I will switch back to the 1.52.3 when I have a little more time to fool with it. |
|
|
|
 | reply to Flogator OK- have switched back to 1.52.3. I got the Log4Manage page to come up. I have logginf function again. I did notice with the 1.45.7, that the logging function kept dropping, and I would have to re-start Wallwatcher to restore logging. I don't like losing logging as it doesn't tell me what is going on with my system. |
|
 Reviews:
·Comcast
·AT&T Midwest
| said by DelawareDave:OK- have switched back to 1.52.3. I got the Log4Manage page to come up. I have logginf function again. I did notice with the 1.45.7, that the logging function kept dropping, and I would have to re-start Wallwatcher to restore logging. I don't like losing logging as it doesn't tell me what is going on with my system. I'm ok with V1.45.7 and Wallwatcher, but when I tried 1.52.3 I had way too many strangeness in my logs. No matter what Log4Manage I used. (DSL use here) -- Looking for 1939 Indian Motocycle |
|
 | reply to Flogator Well, I am not happy now. The 1.52.3 F/W is also dropping the logging function after 2 or 3 minutes. I have to re-start Wallwatcher to get logs again. Internal logs are working, tho, but I don't want to log into the router to view. I do have the latest version of WW running. |
|
 Reviews:
·Comcast
·AT&T Midwest
1 edit | I was seeing V1.52.3 logs drop off over time, too.
But never had a problem with V1.45.7.
How are you gettting the logs to the wallwatcher's computer? Is the computer a fixed IP and you are directing to that specific IP, or are you DHCP and router is broadcasting logs to all?
Fixed IP on computers here, and never had an issue with WW getting logs. -- Looking for 1939 Indian Motocycle |
|
 1 edit | reply to Flogator Well, I have a record- WW logging ran for 13 minutes before cr***ing out again. I never had this issue with the original F/W. 1.44.11t. The 1.45.7 was also dropping out after a few minutes as well. I have static IP on all 6 machines on my network. I may go to Linksys web site and try to find original F/W and reinstall that. |
|
 | reply to Flogator All right- I tried another ploy. I switched firmware again! I tried 1.50.18 from Linksys site. Absolutely worthless! Most of the settings returned errors when trying to save. SOOOOOO...... I re-installed 1.45.7. I also un-installed Wall Watcher. I then downloaded the current WW and the library file from their website. I reinstalled, and so far so good. Over 1/2 hour, and still logging! We shall see. |
|
 | Some new info- In the WW help files, I discovered that the new version I downloaded today (3.2.19, rel 4-1-05) is different than the version I d/l a couple days ago (3.2.18, rel 3-22-05). It seems an issue was fixed- WW would stop logging on it's own. That may explain the problem I was having. |
|
 FlogatorPremium,MVM join:2003-01-19 Cantley, QC kudos:1 | Re: BEFSX41 Firmware 1.52.3 - POST YOUR RESULTS HE Seems that the Log4Manage.htm thingy does not reliably do the trick for logging . I have already reported the logging problem to Linksys. I will add that the above mentioned workaround does not always work. For now on, I can only recommend you to use 1.45.7 or 1.51.00. |
|
 redblkjckPremium join:2001-11-07 Millersville, MD | Got to briefly test this with a SpeedStream 5200 DSL modem. No luck on getting that SB4200 cable modem to work with this firmware. Logged on fine and browsed surfed the internet fine. VPN connected and speed test were the same. The logging was an issue with WallWatcher. When using the trick posted here, it did pick up the outgoing packets but it also logged every other ppp log, which fills up rather quickly. See below. Either me changing the settings for the log or the firmware it self got my DynDNS account locked out. Once I flashed back to 1.51 I got the blocked account message from DynDNS. Is the frequent VPN drop a common problem with the other firmwares also? Every time I have a PC that boots behind the linksys (PCs are static and DHCP) my VPN drops and reconnects. My BEFSX41, uses FQDN, IKE Preshare key, Main Mode with Username. Ohter BEFSX41 End point the same except for accepts from any host rather than FQDN. There is a Win2K box that will accept MS VPN ipsec running behind the linksys.
jack 2005/04/12 23:03:59.10 M [0:01:00] real_free=418(418),free=418,alloc=181,rel=0,wt=1 2005/04/12 23:03:59.10 M uiCorpCurCtrs=8(1300),uiExtCurCtrs=0(1100) 2005/04/12 23:03:59.10 M PPP Tx: [1], proto=c021 code=9 sid=314f, state=255 2005/04/12 23:03:59.13 M PPP Rx: [1], proto=c021 code=10 sid=314f, state=255 |
|
 Reviews:
·SONIC.NET
| The next version of WallWatcher (v 3.2.20) supports the SpeedStream 5100, and it should be released by April 20th, 2005.
If you want to send me samples from the 5200, either turn on "Capture" on WW's "SPECIAL" menu for a while, or download and run the Log Capture utility: www.wallwatcher.com/LogCapture.zip . After collecting samples, send "RAW yyyy-mm-dd.DAT" to WW's "support" address and identify the router that was sampled. I'll either confirm that the 5100 support covers the 5200, or will add support for the 5200.
You can reduce the size of the logs by using various filters in WW. -- Dan Tseng (WallWatcher author) |
|
 redblkjckPremium join:2001-11-07 Millersville, MD | Dan Tseng, I think it is Linksys issue, since I have the Linksys handle the PPPoE and the 5200 is set to bridged. Rolling back the firmware on the Linksys Wallwatcher works fine. I can give it a try when I get the time but I don't think the Linksys was broadcasting out the full log, could be wrong. RATM I need the VPN running of the Linksys. But when I get a chance I will flash it again, do a capture. I'll drop it out of bridged mode and capture some 5200 traffic if you need it to compare with for the next release. I'll send them both to the support address posted on the bottom of your website.
jack |
|
 | reply to Flogator Is 1.51 better or 1.52? There seems to be mixed reviews. I could care less about logs. |
|
 scarneyBbr Team Discovery - Bbr Team Rc5Premium join:2001-02-18 Madison, WI | said by SquareSlinky:Is 1.51 better or 1.52? There seems to be mixed reviews. I could care less about logs. 1.52.3 has been working great for me. i dont use any of the major features, just the firewall and browse and game. i do get the occasional disconnect/boot to desktop when in a game. other than that its a nice firmware. im on SBC DSL btw. -- "I have come here to chew bubblegum and kick ass, and I'm all out of bubblegum" |
|
 | reply to Flogator The BEFSX41 seems to be slower than the DLink I was given from Verizon using PPOE. I thought it might be a firmware issue, but it doesnt seem to be. My speed tests are ranging from 9 down to 4 down with the SX and 15 down with the DLink. I would prefer not to use the DLink.
Anybody have any ideas why this might be? Is PPOE better with some versions of firmware than others? If so, please let me know what is better. |
|
 FlogatorPremium,MVM join:2003-01-19 Cantley, QC kudos:1 | Some are luckier than others for their pipes . If you are willing to experiment a little, you might want to give 1.45.7 a try. That firmware is using the old style GUI to configure the router, but the speed benchmark was in the 16Mbps range when using firmware 1.43.3. Firmware 1.45.7 is the closer to that firmware with the stability and most of the functionality working. Look at the review below for more information.
»www.tomsnetworking.com/Reviews-1···SX41.php
And don't worry about the UPnP cons mentioned in the summary. UPnP is working in 1.45.7 along with many other features. Happy reading. |
|