how-to block ads
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
 ·Acanac
 ·Videotron
| Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE Guys, I am currently chasing an old bug that might have resurface. The old bug is about long URL strings. Could some of you using 1.50.18 try the URL below and indicate to this thread whether it crashes the BEFSX41 or not?
»linksys-befsx41-etherfast-cable-···ter.html | |
|  
CrazyM
Premium
join:2001-05-16
BC Canada
| Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE said by Flogator  :
Guys, I am currently chasing an old bug that might have resurface. The old bug is about long URL strings. Could some of you using 1.50.18 try the URL below and indicate to this thread whether it crashes the BEFSX41 or not?
Crashed right away and seemed to take it's time coming back on it's own.
Regards,
CrazyM
--
"The best thing we can do in cyberspace is exactly what we do in the real world: do our best to manage the risks."- Bruce Schneier | |
| Eko
Premium
join:2004-05-04
Slovenia
4 edits | Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R I tried your loooong link, flogator, can you explain this, it's fw. 1.45.7, the WW log is funny. Check the first one. TCP request is coming from 49.50.46.49; not from 192.168.1.10 as normal. Then there is a UDP 137 request from my comp.
06:53:38,13 O tcp 212.100.242.195 linksys-befsx41-etherfast-cable-dsl-firewall-router.home-spot. 80 49.50.46.49 3450
06:53:42,78 O udp 49.50.46.49 137 192.168.1.10 137
Seems like a bug also. AliM
Edit: I got the 2nd: It was WW attempt to resolve local IP to name. If you need Etherreal capture let me know.
Edit2: Another one: »citroen-commercial-price-used-ve···cle.html
TCP from 50.46.49.57
and »motorola-mobile-phone-accessorie···ies.html
TCP from 53.41.0.10 | |
| |
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R AliM, as you said, the second log entry is an attempt by Windows to resolve the name to an IP address. Not much you can do about that one other to upgrade to Windows XP which this can be disabled.
As for the strange log entry. That is part of the bug. If you look at 49.50.46.49, it would translate to the following string: 12.1 which looks to me a portion of the string 212.100.242.195 which is the destination IP address.
My question though is, aside of this strange log, does it reboots the router in 1.45.7? For everyone else, I would like to know if it reboots their router on 1.50.18. | |
| | | Eko
Premium
join:2004-05-04
Slovenia
3 edits | Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R Flogator, no, they don't reboot the router (1.45.7). I tried some more of them, all works (SPI on or off; the same). What do you mean by "it translate to 12.1"? How?
Edit: Got it, ASCII. I will check the other ones.
50.46.49.57 = 2.19 = 212.100.242.195
53.41.0.10 = 5)?? = I don't know, any idea?
AliM | |
| | | | | | | | | pratttech
join:2004-03-17
Attleboro, MA
|  Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R
I am a residential ADSL subscriber, with a dhcp assigned address over PPoE. Most of my settings are default-- SPI is on, nothing is filtered, PPTP and PPoE passthrough is off-- IPSec is on (I use a VPN client to access work LAN). Time server is user defined. I also use the dyndns.org service to follow my dynamic IP so that I can access my LAN remotely. With the exception of some gaming port triggers, the only static port forward is 22 (ssh) to my BSD box. The main reason I upgraded my FW was to get the option to totally stealth identd instead of the leaving it shown as closed like it did under 1.43. Now when I run an nmap against my router only port 22 shows open, and that is only when run with the -P0 switch.
I have had no issues with the router dropping connections or spontaneously resetting. I have been very happy with its stability-- right now it is reporting an uptime of 90 days (which is pretty weird since it lost all its other settings when I updated the FW). The Linksys did not cause the only connectivity problem that I ever had; it was an overactive dhcp lease from my ISP, which would change my IP too frequently. It was a hassle because it would cause a TCP reset in my SW every time that happened—and X apps get really upset when their tunnel collapses 
I just ssh'd to my box and then tried the trace out to a site and had no problems (except the ICMP filtering at the endpoint, but that's all too common nowadays): Mine is BSD traceroute, while the thread seems to indicate a Microsoft tracert. Maybe that could be the difference? Only other problems I ever have is due to my particular remote maintenance method (I don't enable remote access on the router, but instead tunnel my BSD box’s Netscape through ssh to whatever X server I'm at and then even though I am at a remote location; I am still actually accessing the Linksys locally). The problem is that the connection gets reset if I make any changes because the router apparently resets everything, not just the particular change I made.
So overall I am very happy with my cheap router. Only thing I haven't enabled yet that I intend to someday is the VPN endpoint functionality. What I really want to do is use the Linksys like the PIX I have at work and run a VPN client to get remote access to my home LAN. Haven't seen any one commenting on having done this yet, and as my current method of ssh and tunnels pretty much functions as a VPN except that I have to manually configure each service I need to run (which isn’t many); it's not a high priority for me.
Anyway the only other comment I have to make is now that Cisco owns Linksys, when the heck are they going to put out a Linksys CLI similar to the Cisco IOS so I can ditch the n00b web GUI and get all my configs listed on one screen? | |
| | | | | | 
gho5t
@cox.net
| Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R Using 1.50.18 try disabling the 113 filter under the Security tab and forward port 113 to your computer. See if it works correctly. I can almost promise you it won't. If you use windows, try running kazaa lite. The router will instantly reboot. I like to chat with my friends when I'm on my winblows box so I use mIRC and AIM, neither of which under 1.50.18 will hold a constant connection, when before using a Linksys router I was able to idle for weeks and never drop the connection unless the server went down. As for 1.45.3 or 1.45.7 try uploading 'anything' to 'any' server and the router will instantly reboot. | |
|
gho5t
@cox.net | Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE It didn't crash my BEFSX41. I'm using 1.50.18 firmware | |
| arclight9
join:2004-05-22
Vienna, VA
| Flogator
I was using FW v1.45.7 and can view the long link page without any problems. SX41 settings under v1.45.7 are default, except for port 113 forwarding for stealth.
Loaded v1.50.18 using the factory default settings. Clicking the long link causes router to reset every time. ISP is Cox Cable, basic LAN set-up is 3-5 PCs w/Windows 2000/XP (1 connected directly to router, others via switch), an XBOX (via switch) and a Linksys WAP 54G (connected directly to router port). Not sure why, but my observation is that web pages load noticeably faster using w/v1.50.18. The very short, but noticeable lag with the previous FW versions seems to be gone. Security check on grc.com comes up "passed". Also ran security tests at »scan.sygatetech.com/quickscan.html and everything looks good there too. Will probably stick with this version for a while to see how it goes. | |
| | 
griff99
Premium
join:2002-12-29
Merrimack, NH
| Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R 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. | |
| | | Darmichar
join:2003-04-10
Benton, IL
| Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R I just stumbled onto this trying to track down my connectivity problems. I too started having problems after upgrading the firmware to 1.50.18.
Those of you having the router reset problems, try doing a tracert in a command prompt without any switches.(All I typed was tracert www.google.com) Kazaa, a download manager from Gamespot and I have just discovered tracert all cause the router to immediately reset.
This is really getting annoying, as I am new to broadband, and don't know a whole lot about troubleshooting networking problems.
If it helps here are the connection stats:
ADSL 768/128 with a dynamic IP
2 Computers connected to the router
One is a Win2K Pro machine and the other is WinXP Home
I also have an Xbox connected. | |
| | | | Darmichar
join:2003-04-10
Benton, IL | Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R I didn't realize before my previous post just how long this thread was. After reading through the thread in its entirety, I have since reverted to FV 1.45.7_001 (one of Flogator's?) and all problems have ceased as far as I can tell. | |
| | | |
|
