Equipment Support > Hardware By Brand > Linksys > BEFSX41 Firmware 1.52.3 - POST YOUR RESULTS HERE

reply to Flogator

Re: BEFSX41 Firmware 1.52.3 - POST YOUR RESULTS HE

• The bug called "SNMP walk fails when DDNS is enabled" is now fixed.
  
• The bug called "Strange logs with VPN passthrough" is now fixed.
  
• The bug called "Some router's web page items take forever to load" is now fixed.
  

• A new bug called "Filter don't work or crash the router" has been introduced.
  
• A new bug called "Intrusion logs don't show up" has been introduced.
  
• The feature "UPnP" does not work.
  

• The bug called "MIB sysUpTime updated 10 times too fast" is still present.
  
• The bug called "Idle TCP NAT entry gets removed after 10 minutes" is still present.
  
• The feature "QoS" does not work
  
• The limitation called "VPN shared secret limited to 24 characters" is still present.
  
• The bug called "No connect button in manual keying" 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" could not be tested because of a new bug.
  
• The limitation called "Filter logs do not indicate which filter number was hit" could not be tested because of a new bug.
  
• 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.
  

reply to Flogator
Well,
the new firmware doesn't work in Germany with DSL service.
Reboots is all you get when there's traffic on the WAN interface.
The 'old' firmware befsx41_v1.51.01_000_0909_code.bin does work, however.
Further on, you /have/ to use MS-Internet Explorer to fill in the config data. Firefox wasn't able to even input my DSL user name or password (took quite some time to figure out why the user name field was still blank after 'safe')

But it was fast with displaying local pages and with turning on all front panel lights

Cheers from over here

jahonix

Oh great!?! Now I'm getting this report from my Log viewer:

2005-03-11 20:02:31 1447/TCP from 24.42.40.217:61681 to 192.168.1.10:1447 Invalid TCP packet received, dropping packet
2005-03-11 20:03:55 3/ICMP from 62.35.58.185 to 210.213.230.234 Dropping ICMP error message. Original UDP from 210.213.230.234:6346 to 62.35.58.185:6346
2005-03-11 20:04:38 3/ICMP from 206.74.22.87 to 210.213.230.234 Dropping ICMP error message. Original UDP from 210.213.230.234:6346 to 210.213.230.234:6230
2005-03-11 20:06:45 6346/TCP from 68.6.104.78:3231 to 192.168.1.10:6346 Invalid TCP packet received, dropping packet
2005-03-11 20:07:35 3/ICMP from 213.227.33.14 to 210.213.230.234 Dropping ICMP error message. Original UDP from 210.213.230.234:6346 to 213.227.33.14:6346
2005-03-11 20:08:55 3/ICMP from 200.140.89.184 to 210.213.230.234 Dropping ICMP error message. Original UDP from 210.213.230.234:6346 to 200.140.89.184:6346


* only a part of the log report I got.

Should I worry? Anything to resolve this?

Thanks!

About those strange logs, I would not worry. This simply indicate that the router did its job by dropping those packets. I get some of those every once in a while.

reply to PARC
I believe those ICMP type 3 packets are a response to one of your local PCs (hosts).

ICMP type 3 are IP error messages. Type 3 code 4 is used as part of PMTU (Path Maximum Transmission Unit) discovery and should be considered normal. XP will send test packets to determine how large to make its MTU when booting. Unfortunately the log doesn't enumerate the code along with the ICMP type.

see
»www.networksorcery.com/enp/proto···msg3.htm

I forgot to mention this:
/FLAMEON
the router drops response packets destined for your host that may influence its behaviour. For instance, when these RESPONSE packets are dropped, your PC is waiting for a response to one (or more) of its probes that will NEVER arrive and probably incur a timeout and/or fallback to a default setting. What setting, you might wonder? Who knows, only the ICMP type (and not the code) appears on the log! ICMP Type 3 indicates "Host Unreachable" but the CODE tells you WHY the host was unreachable. I wish the code would also be listed in the log (so you could really determine why the packet was dropped) and possibly an option to allow these packets through rather than depend on the dubious competency of the Linksys programmer(s).
/FLAMEOFF

Thanks guys!

Atleast now i can relax . BTW Running this firmware almost 2 Days now, no problem what so ever. Even the Filter is running properly.

PARC

reply to ronholla

quote:

---

depend on the dubious competency of the Linksys programmer(s).

---