<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE in Linksys</title>
<link>http://www.dslreports.com/forum/r10311586</link>
<description></description>
<language>en</language>
<pubDate>Wed, 25 Nov 2009 06:17:46 EDT</pubDate>
<lastBuildDate>Wed, 25 Nov 2009 06:17:46 EDT</lastBuildDate>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10627261</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Read this post for more information:<br><br>&raquo;<A HREF="/forum/remark,10521002~mode=flat">Re: A MUST! Read For All Who Flash a BEFSX41</A><br><br>Additionally, if you like 1.50.18, In my mind, you will much prefer 1.51.00 where you can find below:<br><br>&raquo;<A HREF="/forum/remark,10339478~mode=flat">[wired] BEFSX41 Firmware 1.51.00 - POST YOUR RESULTS HERE</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10627261</guid>
<pubDate>Sun, 27 Jun 2004 23:26:33 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10627162</link>
<description><![CDATA[<A HREF="/useremail/u/972988"><b>alexansp</b></A> : FYI:  After much trying to solve this problem & reading many messages about this problem..... I found one person provided information that you need to make use of the "Restore Factory Defaults (yes)" function in the Linksys menu system.<br><br>I perform this task and all is working now!  What a great piece of information to find.<br><br>I have seen a few messages that you could upgrade to version 1.51 firmware level though the "web interface".  Where and how does one find and make use of the referenced solution?<br><br>Much Thanks,<br><br>BEFSX41 User]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10627162</guid>
<pubDate>Sun, 27 Jun 2004 23:15:44 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10626194</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : My method for packet sniffing on the WAN side is quite simple.  I simply insert a hub in between the BEFSX41 and the modem (and I really mean a hub, this will not work with a switch).  Then, I simply connect a spare NIC card to the hub and disable the IP stack on that PC.  Then using <A HREF="http://www.ethereal.com">Ethereal</A>, I can sniff packet flowing through the WAN interface without generating junk traffic (since the IP stack is disabled).  In my case, it just happen that the spare NIC is in my main PC (it has two NIC card, one for regular LAN and the other for WAN packet sniffing).  Having the two NIC in the same PC is kind of convenient since I can sniff on the LAN and WAN at the same time and figure out what's wrong in the BEFSX41 when it is doing it's NAT job ;).<br><br>As a side note, the reason why you really need a hub and not is switch is the following:  The switch is smart and only forward the traffic on the specific port where the destination MAC is located.  By inserting a switch in between, the router will only talk to the modem since the switch knows on which port these two devices are connected to.  The hub is dumb and that's why it is working.  Since the hub is not smart enough to detect on which port the device MAC are connected, it flood the traffic on all ports (except the port where the traffic is coming from of course ;)).  As such, all traffic destined to the router or modem will also be sent on the port where the spare NIC is connected.  Then that's why you can sniff on the spare NIC using a hub ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10626194</guid>
<pubDate>Sun, 27 Jun 2004 21:18:07 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10623828</link>
<description><![CDATA[<A HREF="/useremail/u/720445"><b>RobHam</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR><br><br>Packet sniffing on both the WAN and LAN side demonstrated that echo response with "Don't fragment" bit set is dropped by the router.<br><br><HR></BLOCKQUOTE><br><br>Hi Flogator<br>Just curious - What method are you using to packet sniff the WAN side of the router??]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10623828</guid>
<pubDate>Sun, 27 Jun 2004 15:45:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10589056</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : Well for all the problems it seems to point to several areas of interest:<br><br>1.  Provider induced issues<br>2.  Modem/router incompatabilities<br>3.  Internet exploits<br>4.  Improper flashing techniques/quidance/TFTP software<br>5.  Faulty firmware programming<br>6.  Any combination of these <br><br>This applies to SX and SR41 routers as well as others.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10589056</guid>
<pubDate>Wed, 23 Jun 2004 15:47:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10588835</link>
<description><![CDATA[<A HREF="/useremail/u/1029328"><b>rt3</b></A> : Not sure; but I&#146;m wondering if the only people having issues with the 1.50.18 firmware are using DSL. <br><br>REASON:<br><br> I have been using DSL for 3 years now and bought the SX41 to replace my old Ver.2 SR41. I get the SX41 home, set it up and works great but was disappointed port 113 was only closed. So I upgraded the firmware to the latest and greatest posted version from Linksys, well, let the nightmare begin. Thank you flogator! Many thanks for the 1.51, it saved the day and kept me away from a potentially really late night of pulling my hair out.<br><br> In the meantime, I&#146;ve been caressing the idea of going to cable as I&#146;ve always had distance issues with DSL and when everyone gets FREE upgrades I&#146;m always left at 1.5 MB. Cable in my area is 5MB for the same price. I went ahead and ordered cable and to say the least I love the speeds.<br><br> For no reason I decide to try the 1.50.18 firmware and what do you know it works great, absolutely no issues at all. I still have the DSL modem for the rest of the month so I plug that back in and whoa all the problems are back, I set the cable back up and all is fine once again. Rinse and repeat the above 2 more times, except this time I just didn&#146;t reset or reboot, I made the changes powered everything down and started up fresh. Same results every time, <br><br>DSL = all problems come back as mentioned in above posts<br>CABLE = No issues, works great!<br><br>Go figure, could it be the Modem&#146;s ages. The DSL is a 3-year-old SpeedStream (Sorry can&#146;t remember Model Number, if I had to guess 3600???) and the cable modem is a Motorola SB5100.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10588835</guid>
<pubDate>Wed, 23 Jun 2004 15:20:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10585813</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : toddcurry, two suggestions for your VPN tunnel.  Upgrade to 1.51.00 and enable IPSec Pass Through even if you don't need it.  That should help you out.  All my VPN tests succeeded using the above conditions.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10585813</guid>
<pubDate>Wed, 23 Jun 2004 09:30:35 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10584707</link>
<description><![CDATA[<A HREF="/useremail/u/616968"><b>sgkent</b></A> : I had trouble with 1.50.18 but that was due to not using current TFTP file when flashing.  My guess is that older web interface program and TFTP files don't allow full flash of 1.50.18.  Only other alternatives are issues where inbound or outbound traffic may be corrupting flash process.  Router's behavior with 1.50.18 after using new TFTP program was totally different than with older TFTP. Like night and day. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10584707</guid>
<pubDate>Wed, 23 Jun 2004 01:56:09 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10579318</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : I'm wondering if it would be a good idea to end this thread with a statement to NOT use this firmware release (1.50.18).  It simply has too many issues.  Either try the 1.45.7 or go to the 1.51.00.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10579318</guid>
<pubDate>Tue, 22 Jun 2004 15:30:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10574943</link>
<description><![CDATA[<A HREF="/useremail/u/797326"><b>Darmichar</b></A> : 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.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10574943</guid>
<pubDate>Tue, 22 Jun 2004 01:51:23 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10574544</link>
<description><![CDATA[<A HREF="/useremail/u/797326"><b>Darmichar</b></A> : 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.<br><br>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.<br><br>This is really getting annoying, as I am new to broadband, and don't know a whole lot about troubleshooting networking problems.<br><br>If it helps here are the connection stats:<br><br>ADSL 768/128 with a dynamic IP<br>2 Computers connected to the router<br>One is a Win2K Pro machine and the other is WinXP Home<br>I also have an Xbox connected. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10574544</guid>
<pubDate>Tue, 22 Jun 2004 00:38:51 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10548080</link>
<description><![CDATA[<A HREF="/useremail/u/1026729"><b>theduderog</b></A> : I'm having the same problem as homebrewmike. Two of my three PC's can get to all sites while one gets "blocked" on some.  If I try to ping, I get no response.  I tried reseting the router, recycling the DSL box, recycling the PC's, releasing + renewing their IP's, etc. with no luck.  Would be very interested if there is a fix.<br><br>Also, tracert seems to make the router go berserk. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10548080</guid>
<pubDate>Fri, 18 Jun 2004 18:56:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10541980</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Bless you. I upgraded my firmware last night and SPI stopped working. (Ofoto image uploads were crashing the router hence the upgrade!) After the upgrade, I found nothing was working until I disabled the the firewall.<br><br>I have spent HOURS searching linksys and the web in general trying to find out what was going on. I finally found a log message showing the filter drop. With that I found this thread and the fix. This solved the problem.<br><br>Mucho thanks.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10541980</guid>
<pubDate>Fri, 18 Jun 2004 01:54:10 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10529984</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : forget 1.50.8,<br><br>after i applied the firmware to the router i wasn't able to display the EBAY webpage and something other. Went back to 1.45.7 and it works so.....<br><br>Ciao fizelsche, Germany]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10529984</guid>
<pubDate>Wed, 16 Jun 2004 20:22:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10520924</link>
<description><![CDATA[<A HREF="/useremail/u/616968"><b>sgkent</b></A> : See my notes on flashing a BEFSX41 before using 1.50.18 or 1.51.0.  The correct TFTP program must be used and the old one doesn't appear to upload all the binary even though it will say Ok. That may be an issue with other in the BEF series as well and why some have issues and others don't.<br><br>Steve]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10520924</guid>
<pubDate>Tue, 15 Jun 2004 21:17:23 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10518303</link>
<description><![CDATA[<A HREF="/useremail/u/576486"><b>TomLe8</b></A> : Hmm, to add a bit more confusion. I just upgraded my BEFSR41 v.1 to firmware v1.45.11. And it contains the new feature "Filter Internet NAT Redirection". It doesn't matter if I enable or disable it, I can get to my router login screen using my WAN IP in my browser either way.<br><br>Maybe this feature isn't working correctly with the v1's, or maybe it is.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10518303</guid>
<pubDate>Tue, 15 Jun 2004 16:26:57 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10508878</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Find all of the useful BEFSX41 old firmware (including 1.44.3) at the link below:<br><br>&raquo;<A HREF="/forum/remark,9155542~mode=flat">Re: Advanced Filtering in BEFSX41 fw 1.45 - YUK</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10508878</guid>
<pubDate>Mon, 14 Jun 2004 17:31:20 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10508291</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : J_E_B, where did you get version 1.44.3 for your BEFSX41?  Could you send an e-mail to me at cliffyincalgary@hotmail.com with the information?  I need it really bad.  Thank you.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10508291</guid>
<pubDate>Mon, 14 Jun 2004 16:17:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10505341</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Here you go: &raquo;<A HREF="/forum/remark,9086151~mode=flat?hilite=befsx41+1.45.7">[wired] BEFSX41 firmware 1.45.7</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10505341</guid>
<pubDate>Mon, 14 Jun 2004 09:45:23 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10505036</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : would anyone like to send me 1.45.7 or link me to a download. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10505036</guid>
<pubDate>Mon, 14 Jun 2004 08:50:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10482685</link>
<description><![CDATA[<A HREF="/useremail/u/744589"><b>toddcurry</b></A> : This is also a problem if you have anything in the domain field -- VPN won't come up, no matter how many times you click.  <br><br>Linksys, please fix!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10482685</guid>
<pubDate>Fri, 11 Jun 2004 15:00:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10472291</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : eljay001, I totally understand your concern.  Unfortunately for now, your only alternatives using the BEFSX41 are:<br><br>1- Deny ActiveX in the router and live with random reboots<br>2- Allow ActiveX in the router and configure your web browser to deny ActiveX]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10472291</guid>
<pubDate>Thu, 10 Jun 2004 14:31:38 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10472240</link>
<description><![CDATA[<A HREF="/useremail/u/972855"><b>ElJay</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>The irony here, is if you really want to deny ActiveX, you should know that you can do the very same thing by configuring your web browser. <HR></BLOCKQUOTE><br><br>Given the various security exploits that come out time to time that get around the IE "security" settings, I thought filtering these at the router would provide better protection.  I don't use IE for anything but Windows Update, but there are others in my household who are stuck on it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10472240</guid>
<pubDate>Thu, 10 Jun 2004 14:25:52 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10472098</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : For people have trouble with tracert, it is working perfectly in 1.45.7 and 1.51.00.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10472098</guid>
<pubDate>Thu, 10 Jun 2004 14:11:46 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10472068</link>
<description><![CDATA[<A HREF="/useremail/u/597373"><b>silentsnow</b></A> : - tracert crashes router<br><br>- everything else works (Overnet, eMule, surfing)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10472068</guid>
<pubDate>Thu, 10 Jun 2004 14:08:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10471901</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Perhaps the BEFSR41 is buggy when it comes to local loopback.  However, on the BEFSX41, it works as I have described earlier.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10471901</guid>
<pubDate>Thu, 10 Jun 2004 13:53:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10471848</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : On my v2 BEFSR41, if I *enable* "Filter Internet NAT Redirection" then local loopback works and I can access<br>the login screen from the LAN side using the WAN IP in<br>the browser. If I *disable* "Filter Internet NAT <br>Redirection" then local loopback does not work and I<br>cannot access the login screen from the LAN side when<br>using the WAN IP in the browser. :huh:<br><br>This filtering protocol seems to talk backwards.<br><br>-- <br>blackjack]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10471848</guid>
<pubDate>Thu, 10 Jun 2004 13:48:05 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10471651</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : F-117, in my mind, the feature is up-side-down.  If it would have only be me, I would have called the feature <B>Local Loopback</B> and provide the ability to enable or disable it.  However, Linksys decided to use inverse logic by naming the feature "Filter Internet NAT Redirection" where enabling it means you filter out NAT redirection thus disabling local loopback.  If you disable the feature, you effectively disable the filter thus letting NAT redirection through and thereof enabling local loopback.  This is just another way for Linksys to make a small and simple feature into a complex and confusing configuration.<br><br>In the first statement you quoted me on, I was referring to local loopback and I still say I don't understand why someone would want to disable local loopback (at least if I am quoted again, the statement should be more clear).<br><br>In the second statement, I was referring to disabling the "Filter Internet NAT Redirection" feature so that you gain access to local loopback.  This simple feature has been over complicated for no reasons.  That's why I may let go confusing statement.<br><br>Thank you for the note.  I'll make sure next time I post that I am clear like crystal on my statements.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10471651</guid>
<pubDate>Thu, 10 Jun 2004 13:25:10 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10471139</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Assuming you want local loopback, haven't you just made <br>two opposite statements?<br><br>"(still don't understand why you would want to disable it though)"<br><br>"If you disable the feature you gain local loopback."<br><br>-- <br>blackjack]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10471139</guid>
<pubDate>Thu, 10 Jun 2004 12:01:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10470315</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : We have started discussion on this topic in about the 1.44.8 time.  In other words, this problem exists at least since 1.44.8 and was likely present before.<br><br>The irony here, is if you really want to deny ActiveX, you should know that you can do the very same thing by configuring your web browser.  For example, with IE, you can disable ActiveX by going in the "Tools"-&gt;"Internet Options..." and clicking on the "Security" tab and clicking on the "Custom Level..." button.  You will see many option related to ActiveX.  If you disable those all out, then your browser will no longer respond to ActiveX.  This should have the same effect than what Linksys wanted to do with the web filters.  Unfortunately, it reboots the router whereas the tweaking in your web browser is not ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10470315</guid>
<pubDate>Thu, 10 Jun 2004 10:09:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10468662</link>
<description><![CDATA[<A HREF="/useremail/u/972855"><b>ElJay</b></A> :  <BLOCKQUOTE><SMALL>said by BBMAC:</SMALL><HR>I was hoping Cisco would really help to get all the bugs out.  The interface is much nicer to look at but man... who likes having their router crash?<br> <HR></BLOCKQUOTE><br><br>How long have the four "web filters" been broken? I know they cause problems in 1.45.3 and I'm wondering if this is this a flaw in the design of this unit or just more neglected code? The ActiveX filter would be really great if it had a small white list (so I can add windowsupdate.microsoft.com) and didn't cause the router to reboot at various times.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10468662</guid>
<pubDate>Thu, 10 Jun 2004 01:36:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10466489</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I just got this update (Firmware Version: 1.50.18) from Linksys tech support, but I'm still having the same FTP (WS-FTP client) issue as before... <br><br>It seems that I can connect to a ftp server but it freezes on "150 Opening ASCII mode data connection for /bin/ls."  I can connect to the server directly when I bypass the router.<br><br>I've searched and read several post on several boards... some say use passive, some active mode. other say to set up port forwarding on the router (model BEFSX41 BTW).<br><br>I was on the phone with Linksys for 2 hours trying to get the thing to work... eventually the tech gave up and said I should return it if it was in warranty, which it is not.<br><br>Basically I'm at the WTF stage!  <br><br>Any help would be greatly appreciated.<br><br>sg]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10466489</guid>
<pubDate>Wed, 09 Jun 2004 21:19:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10464939</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I'm having issues with the upgrade too, if I turn on the firewall it blocks everything.<br><br>Does anyone know where to get older versions of the firmware?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10464939</guid>
<pubDate>Wed, 09 Jun 2004 18:37:49 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10447738</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : BBMAC, crash on speed test is <B>well known</B> when using the web filters.  Try allowing all four web filters and run a speed test.  Then, you should not have any problems.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10447738</guid>
<pubDate>Mon, 07 Jun 2004 21:54:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10447642</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Yeah, my BEFSX41 just crashed doing a speed test using 1.50.18.  The only "Security" filter I have on is Filter ActiveX.  Well, Filter Multicast and Filter IDENT(Port 113) are on as well but I have a feeling it's more about the ActiveX one since that alone seems to have crashed my router in the past with previous firmwares.  I was hoping Cisco would really help to get all the bugs out.  The interface is much nicer to look at but man... who likes having their router crash?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10447642</guid>
<pubDate>Mon, 07 Jun 2004 21:45:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10445218</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : Actually them seem to still have a few things that needs fixing in 1.51 so hopefully an official release of 1.51 won't happen.  Perhaps a later revision number with all the fixed in place!  "knock on wood"]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10445218</guid>
<pubDate>Mon, 07 Jun 2004 17:23:57 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10444971</link>
<description><![CDATA[<A HREF="/useremail/u/992498"><b>tonyellard5</b></A> : The problems I experienced were limited to slow internet connectivity along with the inability to access web pages like Hotmail, movietickets.com, with no ryhme or reason.  I tried forwarding every allowable port to one machine with no effect.  Only with the firewall off would I be able to access these sites.<br><br>I downloaded and upgraded to the 1.51 version posted here and everything seems to work like a charm now.  I can only hope that when they officially release this version they don't break it as badly as they did 1.50.  How could they have possibly thought that 1.50.18 was a public quality release??!!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10444971</guid>
<pubDate>Mon, 07 Jun 2004 16:51:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10438939</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Figured out how to set mtu on Linux boxes to 1492 as suggested by Frogolator and now works fine.  Avoiding traceroute -I etc...<br><br>Will wait until official release of 1.51.00 to try it out.<br><br>-Mike]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10438939</guid>
<pubDate>Sun, 06 Jun 2004 22:04:10 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10436429</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : 1.50.18 does not allow me to ftp to ftp.linksys.com/pub/network and do an ls.  Also, can't access &raquo;<A HREF="http://www.nws.noaa.gov" >www.nws.noaa.gov</A>.<br><br>Fell back to 1.50.9 before reading this newsgroup.  Perhaps should fall back more to 1.45.3 (don't have 1.45.7).<br><br>Traceroute fails to the wan in 1.50.9, but does NOT crash the router.<br><br>Good luck all.<br><br>-Mike]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10436429</guid>
<pubDate>Sun, 06 Jun 2004 16:17:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10432409</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : It's this is all beginning to happen all of a sudden. I had used 1.50.18 with no problems what so ever (although I never tried a tracerout before with it.)  Having exausted all avenues and gone nuts! Given the timing of it all, with the recent Sisco leak, I'm beginning to wonder if we have a 'new' class of 'viruses' now, router viruses? Only Linksys can tell, but will they?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10432409</guid>
<pubDate>Sat, 05 Jun 2004 23:55:29 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10430051</link>
<description><![CDATA[<A HREF="/useremail/u/1019577"><b>homebrewmike</b></A> : Flogator-<br><br>>After your upgrade, did you rebooted all of your PCs? <br>> One of the common problem is about DHCP leases conflicts<br>> in between router reboots.<br>All of the machines in the network use static IP's.  After poking around here, I noticed that people were changing their MTUs - so I tried that (used 1492 per some link.) <br><br>No dice.<br><br>So, I ended up going to a previous version of the FW (what the thing shipped with.)<br><br>I'm now trying 1.51.00 - seems to be ok so far - the machines on my network all seem to be able to see the "blacked out" sites.<br><br>Thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10430051</guid>
<pubDate>Sat, 05 Jun 2004 18:02:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10418259</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Did the same for me.. everytime I turned the WAP on or a wireless enabled PC either the router rebooted or the browsing was kaput. Disabling the nic and re-enabling it sometimes worked. A veritable crock of s**t]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10418259</guid>
<pubDate>Fri, 04 Jun 2004 08:53:29 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10416693</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have had this installed for a week now and have not had any of the problems decribed here.<br><br>I updated from 1.44.3 to 1.50.18<br>I had a slight problem connecting to the net till I recloned the mac address. <br><br>I have four computers 2 xp 2 linux boxes connected via cable<br><br>I tried the traceroute with no problems, and the long urls with all the boxes no reboot... mric and aim work fine,<br>My son lives on aim and has reported no problems...<br><br>kazza lite++ works as usual maybe a little slower.. I dont use it much anymore...<br><br>the only problem I have discovered is using cuteftp to ftp to the linux boxes via ssh2 dosent work but that may be because I upgraded to fedora2 from rh9, I'm not done testing yet.<br><br>Sorry to hear so many have problems with this and thumbs up to those working very hard to help those that are having troubles...<br><br>I'm very new to the router scene and am just a monkey pushing buttons and got lucky I suppose.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10416693</guid>
<pubDate>Fri, 04 Jun 2004 00:15:07 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10405781</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I updated two BEFSX41 routers with the 1.50.18 firmware.  To put it in layman's terms, "they're really screwed up now."    One passes traffic intermittently.  The other allows pings by IP address, but not by FQDN. It won't let me do HTTP at all.  I upgraded the first BEFSx41 because it had really old firmware.  I upgraded the second BEFSX41 to see if the new firmware was causing problems.  I tested the second BEFSX41 before I upgraded it, and it was working perfectly. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10405781</guid>
<pubDate>Wed, 02 Jun 2004 20:01:29 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10405755</link>
<description><![CDATA[<A HREF="/useremail/u/993682"><b>MonkeyBoy666</b></A> : When I upgraded to 1.50.18 my firmware settings were seriously off, particularly VPN settings. In addition, the router was problematic with SPI enabled. Only by resetting to factory defaults and inputting all new values was I able to get it working again.<br><br>I don't believe settings are transferring properly from 1.4, as this same thing has occurred with 2 other people who upgraded to 1.50.18 (one using the 1.4 web upgrade, the other using their upgrade utility). I would seriously recommend doing a factory reset before writing off 1.5 altogether.<br><br>On the plus side VPN is much more reliable. Instead of getting into a strange hung state where the BEFSX41 thinks the VPN tunnel is up when it's actually down (in effect all packets to/from the remote network are dropped by the BEFSX41), then rebooting when you manually disconnect/connect, it seems to reboot itself whenever instead of getting into that strange state. I think. Maybe it's just plain not getting into that state - I never notice it rebooting, and haven't had to futz with it since upgrading. Thank god.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10405755</guid>
<pubDate>Wed, 02 Jun 2004 19:58:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10403333</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I just upgraded a BEFSX41 from 1.45.3 to 1.50.18.  The new look was nice, but I started having troubles with video chat cams freezing intermittently on jmeeting and paltalk services.  Also noted a date in one of the router logs as 06/32/2004 instead of 05/31/2004.  No other problems were noted.  When I replaced the upgraded router with one running the 1.45.x firmware, all back to normal (no intermittent cam freezes).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10403333</guid>
<pubDate>Wed, 02 Jun 2004 14:57:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10394156</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have had somewhat similar results.  Have several computer behind the BEFSX41.  One all of a sudden stopped browsing the internet.  It had worked fine since March of 2003.  I have verizon dsl w/ pppoe.  All other PCs could still use the net. The broken one could ping, telnet, and use AOL IM.<br><br>Upgraded the firmware to the newest (.18) and reset to factory defaults.  Still has the same issue.  One PC doesn't work... all others do.<br><br>Linksys wouldn't admit it was thier problem.  Even when the PC worked connected directly to the modem, or when i took it in to work, or when i used a dlink router.  <br><br>I find it odd that it is only on 1 of my pc's not all of them.<br><br>I have formatted and reinstalled a clean w2k pro on that box... still doesn't work!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10394156</guid>
<pubDate>Tue, 01 Jun 2004 15:33:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10374333</link>
<description><![CDATA[<A HREF="/useremail/u/1015794"><b>magore</b></A> : I can confirm that 1.50.18 breaks pasv ftp. Reverting to 1.45.7 fixes the problem<br>Setting the MTU to a manual setting breaks DNS lookups]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10374333</guid>
<pubDate>Sun, 30 May 2004 00:07:50 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10369227</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : The first thing I did when I bought 2 of these was update to 1.50.18 (as available on Linksys' website).  What a mistake.  My IRC connections would drop in about five minutes unless I was speaking continuously (normally I idle on IRC 24/7).  Behind the second router IRC connections got dropped even with that machine on DMZ (!)  All the servers on that machine were working OK though...<br><br>Flogator, you have it right about tech support - First tech support person said to disable "Block WAN request".  That did nothing.  Second tech support person said to change MTU to 1472.  Enabling MTU stopped all WAN routing no matter what number was used.  The argument about opening port(s) for IRC was hilarious.  At one point they told me to exchange the router (yeah right, I have two and they both do it).  I asked if they were telling me to return it and go back to my SMC router that worked fine, or to buy a different brand.  Heh.<br><br>The MTU clue led here where I found 1.45.7 which is working well and entirely stable.<br><br>Props to Flogator for making the good firmware available.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10369227</guid>
<pubDate>Sat, 29 May 2004 09:27:19 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10368126</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Firmware 1.51.00 fixes the trace route problem.  Please try it out.<br><br>&raquo;<A HREF="/forum/remark,10339478~mode=flat">[wired] BEFSX41 Firmware 1.51.00 - POST YOUR RESULTS HERE</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10368126</guid>
<pubDate>Sat, 29 May 2004 01:33:59 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10367948</link>
<description><![CDATA[<A HREF="/useremail/u/879430"><b>kevdog9</b></A> : I get router reboots when i do a trace route also. Also with AIM and MSN Messenger, i get a lot of dropped packets in the firewall. Kills My AIM connection quite a bit, sometimes from every 10-20 mins to every 1-2 hours. Also kills msn messenger connection, although, not quite as often.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10367948</guid>
<pubDate>Sat, 29 May 2004 01:00:20 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10360275</link>
<description><![CDATA[<A HREF="/useremail/u/511533"><b>redblkjck</b></A> : I'll just add on to what some have stated, confirm the same issues.<br>IRC consistent drops connections (SSL).  Try and tracert from cmd line router drops my connection and hangs for a bit before it connects again.  I think it does a soft reboot.  I can't connect to web consol for a few sec then the PPPoE hangs for a few trying to reconnect.  DSL, MTU set greyed out to default 1492.  Enable it, set manual to 1492 drops connection left and right.  Leave it alone greyed out I stay somewhat connected, just no tracert.  VPN IPSec pass thru works fine for me.  Have not tested the hardware VPN side yet with this firmware.  No need to yet.<br><br>jack]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10360275</guid>
<pubDate>Fri, 28 May 2004 04:12:37 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10359983</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Check this out : i have the remote administration of my router disabled and yet ... i can access  to it  online.<br>another thing is that i think that ftp services  are affected with this last firmware.also my downloads stop sometimes and this wan not happening before like this.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10359983</guid>
<pubDate>Fri, 28 May 2004 02:21:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10354183</link>
<description><![CDATA[<A HREF="/useremail/u/735478"><b>Morbid Angel</b></A> : I had to downgrade the firmware to the 1.45.7.<br>I had nothing but disconnect problems like crazy like every 50 mins or so with the 1.50.18<br>Since I have downgraded the firmware my connection has not gone down yet, going on over a week so far. Until Linksys ever decides to test their firmware updates before releasing them, then I shall considering doing it. Thanks to this forum I can read up on updates before installing them, thanks guys.<br><SMALL>--<br><A HREF="http://www.thedowntown.com/calendar.htm">Downtown, DEATH METAL SHOWS RULE \m/</A><BR><A HREF="http://www.geocities.com/liquidalloymetal/Morbid.html">Morbid Crap</A><BR>Forum Posts:<A HREF="/tracker/735478">1685</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10354183</guid>
<pubDate>Thu, 27 May 2004 14:35:40 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10353995</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Spudrum,<br><br>I also experience that problem, but not only with the 1.50.18 firmware. It happens as well with the 1.45.7 firmware.<br>All is fine until I turn on SPI. After roughtly 10-20 minutes my connection idles out completely, no matter what app I use.<br>The connection to my dsl modem is still up according to the router pages.<br>As of yet I have not managed to find out why it happens either :huh:]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10353995</guid>
<pubDate>Thu, 27 May 2004 14:15:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10348394</link>
<description><![CDATA[<A HREF="/useremail/u/744078"><b>griff99</b></A> : 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.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10348394</guid>
<pubDate>Wed, 26 May 2004 21:56:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10345080</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : For the users still having problem with firmware 1.50.18, may I ask you try latest firmware 1.51.00 and post your findings in its respective thread.  You can find both a link to the 1.51.00 firmware as well as the actual discussion at the link below:<br><br>&raquo;<A HREF="/forum/remark,10339478~mode=flat">[wired] BEFSX41 Firmware 1.51.00 - POST YOUR RESULTS HERE</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10345080</guid>
<pubDate>Wed, 26 May 2004 16:03:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10344732</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : well hopefully i am not the only person experiencing the following problem with the linksys 1.50.18 firmware anyway here goes...<br><br>The problem i have is that i temporarily lose the connection/get timeouts when using various applications, such as Msn Messenger/ TeamSpeak/Raven Shield and my VPN Client.....<br><br>This problem only occurs when i have the router firewall set to 'enabled'....when i set it to 'disabled' i have no timeout or disconnect problems....i am using the built in DHCP server with the client lease time set to 0 (the default)<br><br>so just to clarify currently in order to maintain the connectino to a number of applicatinos i use i use the following firewall settings on the router...<br><br>Firewall: Disabled<br>Block Anonymous Internet Requests: Disabled   <br>Filter Multicast:Enabled   <br>Filter Internet NAT Redirection: Enabled   <br>Filter IDENT(Port 113): Disabled <br><br>i have tried disabling both the 'Filter Multicast' and 'Filter NAT' but they don't make any difference....<br><br>i have read through the Linksys Knowledge Base FAQ Questions and none of the suggested answers apply to my situation<br><br>i also use the ZoneAlarm firewall and have tried turning it on/off and changing the various zone options but i still have the same problem...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10344732</guid>
<pubDate>Wed, 26 May 2004 15:25:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10342570</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Upgraded to 1.50.18 and a tracert from Windows would reset the router.  Went back to 1.45.7.<br><br>KD]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10342570</guid>
<pubDate>Wed, 26 May 2004 10:58:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10332439</link>
<description><![CDATA[<A HREF="/useremail/u/718453"><b>slomotion</b></A> : I am sorry to say that the new firmware completely hosed my router. I could not connect to the internet, slow to load the linksys GUI or not at all. Whats up with Linksys? Back to 1.45.7 for me. :(<br><SMALL>--<br>Did you ever stop to think, and forget to start again?</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10332439</guid>
<pubDate>Tue, 25 May 2004 09:31:54 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10331893</link>
<description><![CDATA[<A HREF="/useremail/u/820408"><b>gdcastro</b></A> : I noticed something odd on this firmware...<br><br>When i first upgraded via the tftp tool.  It was initially successful then I made my changes to WAN and DHCP, saved settings and the router was now useless.  I had it replaced by my vendor.  But i did try everything to try to revive it... reset, cold start, static IP...nothing worked.<br><br>I had the replacement flashed by the techguy himself on the new router so that he can see my problem.  He did it by using the firmware upgrade on the router page.  I was successful.  Then i asked him to do the necessary changes and it was all fine.  Then an ODD thing happened.  I was editting the filters on the restrict access page, saved settings, then i was brought back to the main setup page where you input connection type, lan settings etc.<br><br>Im using static IP btw.  The settings were somehow on Obtain IP automatically WITH the DHCP Disabled.  I figure, this is what happened to my first sx41, before it went dead on me.  What i did when i saw this was close the page and reentered the router page.  It was back to my correct settings.  Be careful about this.  btw, has anyone else noticed this or did this just happen on my 2 routers, because my other sx41, in another location went dead also, so the vendor is replacing it again.<br><br>Thanks]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10331893</guid>
<pubDate>Tue, 25 May 2004 07:01:59 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10331367</link>
<description><![CDATA[<A HREF="/useremail/u/760751"><b>PARC</b></A> : I don't experience any reboot under the 1.45.7 firmware but instead a drastic slow down on uploading using WS_FTP PRO.<br><br>Does any one using the 1.50.18 having this problem too?<br><br>Thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10331367</guid>
<pubDate>Tue, 25 May 2004 02:54:52 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10331132</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : does anyone else have trouble with the router rebooting while trying to upload files when using the 1.45.7 firmware version?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10331132</guid>
<pubDate>Tue, 25 May 2004 01:48:40 EDT</pubDate>
</item>

<item>
<title>re</title>
<link>http://www.dslreports.com/forum/remark,10324007</link>
<description><![CDATA[<A HREF="/useremail/u/901578"><b>hananz</b></A> : At the end of the day does linksys/cisco will make<br>the necessary changes on their firmware 1.5.18??]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10324007</guid>
<pubDate>Mon, 24 May 2004 12:00:23 EDT</pubDate>
</item>

<item>
<title>Re: VPN, UPnP</title>
<link>http://www.dslreports.com/forum/remark,10320724</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Something is not right with the UPnP or VPN in this firmware.  All I know is that it does not maintain my VPN connection.  Whenever it loses it, I also notice that the Internet Gateway icon disapears, which is presented by the router's UPnP service.  After I warm reboot the router the icon reappears in my icon tray and my VPNs reconnect.<br><br>I don't know which is the culprit here, the VPN or the UPnP.  All I know is, I can't tolerate this, so I've reverted back to 1.45.7, which maintains my VPN connections (and UPnP icon) for days on end without a problem.<br><br>I have 2 VPNs set up, both using FQDN both ways; both obviously set for Keep Alive.<br><br>This router is how old now?  How long has it gone without fully working as advertised?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10320724</guid>
<pubDate>Sun, 23 May 2004 23:20:39 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10319609</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I tried 1.5.018 and spent several days trying ot get the thing to work again.  I went back to the original 1.44.3, and it worked for about an hour, then re-boots every minute or so.  Tried 1.45.7 and it seems stable (for more than an hour, at least).<br><br>As a retired hardware engineer, it is my thinking that the design of this box is so close to the edge that operation probably depends on code patterns, power supply voltage, operating temperature (and lunar phase).  It's the only way I explain the inconsistent results I'm seeing.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10319609</guid>
<pubDate>Sun, 23 May 2004 21:16:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10317286</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Actually,<br>I had same problem<br>I reset to factory default and all is working now 100%:)<br>Probably there was a conflict from my previous setup of the olf firmware.<br>firmware 1.50.18 is the best!!!<br>p.s. be careful on filtering java and cookies and ALWAYS check your log<br>Good Luck!!!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10317286</guid>
<pubDate>Sun, 23 May 2004 16:07:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10315669</link>
<description><![CDATA[<A HREF="/useremail/u/1010345"><b>fandang0</b></A> : Hi Everyone<br><br>At the begining of the thread it was suggested that the PPTP problem is fixed. I'm trying to get hosting of PPTP server on my home LAN behind BEFSX41. I get the impression from the broadband forum that no-one has got this to work. I have upgraded firmware to 1.50.18 and I have the usual 742 timed out message. i.e. there is still a significant PPTP problem on this version. Have applied necessary microsoft fixes to XP SP1 and tried a range of firmware now each with PPTP server in DMZ on correct ethernet socket.<br><br>The other basic functions I'm using appear to work OK as long as you leave the MTU disabled on this new version.<br><br>If I've missed something on the previous posts I'm sorry. There were some suggestions that users of other linksys products had got this working but I could find no definitive statement on configuration. Any help would be much appreciated or definitive statement explaining why PPTP pass through won't work.<br><br>thanks Carl]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10315669</guid>
<pubDate>Sun, 23 May 2004 12:36:05 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10314543</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Ok, for the DYNDNS thingy i came up with a "solution". As i only need POP3 connectivity when my server gets up, i have installed one of those DynDNS client, so now, when my server is running i have the MX record updated. The trick here is 'cause the router do the update before the client, so i can leave both of them running in parallel and guarantee that the MX will always be there and the server is up. Tricky, crappy but it is working....<br><br>Anyway, i just would like say that I'm very glad to see how this forum has helped so many plp, it is indeed very important that everyone not only fires against Linksys (as i did :-) )but also propose solutions and ideas. For the DynDNS thingy i have just received and email from LinkSys Support Team  saying that this bug will be fixed on the next firmware release. I also would like to leave an idea, since i have seen so many qualified professionals and top quality discussions over this forum, I think that Linksys should give more attention and open a Beta-testing program or even open the firmware source code (or at least part of it) for its own improvement and community satisfaction. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10314543</guid>
<pubDate>Sun, 23 May 2004 10:02:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10311586</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : For what it's worth, the neat little trick suggested by Esteban2k about the long URL thingy seems to help but DOES NOT solve the problem.  I have attempted to reduce the MTU from 1500 down to 1498 and I was able to access the long URL twice without a reboot.  However on the third attempt, the router crashed again.  This new observation seems to align with my previous observations where I stated that my DSL connection was only crashing once every three attempts :).  DSL uses MTU of 1492 and seems to behave the same (with regards to the long URL thingy) as my cable connection after reducing the MTU.  This post is just to brain storm on that long URL thingy.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10311586</guid>
<pubDate>Sat, 22 May 2004 21:58:44 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10310956</link>
<description><![CDATA[<A HREF="/useremail/u/1010855"><b>zealex</b></A> : For all that i've seen, it seems that 1.45.7 is the way to go. I'll hold on to 1.50.18 since I do not use mIRC a lot, and everything else I need is working... But if this thing starts rebooting while i'm the middle of a gamming session, then is trash time for it.<br><br>By the way, can anyone point out a similar router from a good brand, with similar functionality, that WORKS as expected?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10310956</guid>
<pubDate>Sat, 22 May 2004 20:30:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10309749</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I ve solved all my problem of deconnexion with 1.50.18:<br><br>- I ve downgraded firmware to 1.45.7 (solve deconnexion IRC,ICQ,AIM)<br>- i ve made a factory reset<br>- Configure WAN and LAN setting<br>- fixed MTU to 1498 (solve probleme of long URL)<br><br>Thats all, look like it s pretty reliable now , with SPI enable ...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10309749</guid>
<pubDate>Sat, 22 May 2004 17:31:46 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10306431</link>
<description><![CDATA[<A HREF="/useremail/u/1011405"><b>arclight9</b></A> : Flogator<br><br>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.  <br><br>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 &raquo;<A HREF="http://scan.sygatetech.com/quickscan.html" >scan.sygatetech.com/quickscan.html</A> and everything looks good there too.  Will probably stick with this version for a while to see how it goes.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10306431</guid>
<pubDate>Sat, 22 May 2004 09:07:49 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10306424</link>
<description><![CDATA[<A HREF="/useremail/u/711557"><b>kelmcw</b></A> : I upgrade the firmware from 1.45.3 to 1.50.18 and notice that it keeps on rebooting every now and then. I notice this will only happened when I do a tracert to my ISP or any internet addresses. Please let me know if anyone manage to resolve this.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10306424</guid>
<pubDate>Sat, 22 May 2004 09:06:35 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10306103</link>
<description><![CDATA[<A HREF="/useremail/u/1010855"><b>zealex</b></A> : I confirm that mIRC after being iddle for a while stops working with "[10053] Software caused connection abort" error. Ping/pong dialogs are also not there. Could this be due to mIRC server not being able to ping client?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10306103</guid>
<pubDate>Sat, 22 May 2004 07:57:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10305791</link>
<description><![CDATA[<A HREF="/useremail/u/700900"><b>Tyreman</b></A> : home spot comp. uk. with '43 firmware here and pop up stopper on aggressive.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10305791</guid>
<pubDate>Sat, 22 May 2004 05:13:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10304858</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : After your upgrade, did you rebooted all of your PCs?  One of the common problem is about DHCP leases conflicts in between router reboots.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10304858</guid>
<pubDate>Sat, 22 May 2004 00:39:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10304489</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I just had a weird result, and I was wondering if other's saw it to.<br><br>I'm running a small network with mostly linux machines and one Windows XP machine.   I'm also using AT&T for my ISP.<br><br>I bought the BEFSX41 - and had wonderful results with the 1.45.3, Sep 26 2003 firmware.  All the machines connected, throughput was pretty decent.   In short, it worked like a champ.  However, I hate running old code, so I decided to upgrade to 1.50.18.  (I know, if's it's working, don't fix it.  Tell that to Microsoft Smart Update...)<br><br>Then the weirdness hit.  Only 1 machine could access the net seemlessly - the other machines (1 windows and 1 linux) couldn't get to www.weather.com and our bank.  I double checked everything - the "disable cookies," etc on the firewall.  All looked pretty vanilla.   I futzed with everything, and finally gave up, and backed out 1.50.18 to 1.43.<br><br>Has anyone else experienced this?<br><br>Thanks-<br>  -Mike]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10304489</guid>
<pubDate>Fri, 21 May 2004 23:46:36 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10304467</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : Flogator:<br><br>Crashed mine on first attempt.  Comcast cable here.  Don't think I need to try again.  SPI "ON".  No other special settings.  Oh and for what it's worth mine is pretty rock solid except for the known issues(ie tracert).  No trouble so far with any web sites that I can tell.  My son has been having some online gaming issues with a few very new games but not sure if it is the router though.<br><br>I am probably gonna go back to 1.45.7 to see if I see any changes in web browsing and my sons gaming issues. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10304467</guid>
<pubDate>Fri, 21 May 2004 23:44:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10303728</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Sounds like I'm the only one who's router is crashing when accessing the site below.  I am currently at one of my remote sites on DSL and I can cause this BEFSX41 to crash.  Mind you, interestingly enough, I have more trouble reproducing the problem here than at my main site (on cable).  I'd say that at the DSL site, the router crashes every three attempts where as it does occur pretty much instantaneously at the cable site.<br><br>For the DSL and cable users on BEFSX41 firmware 1.50.18, could any of you guys try a couple of times accessing the site below.  For example, try accessing the site, then close the browser, rerun the browser, try accessing this site again.  If after five attempts you still can't crash the router, then never mind.<br><br>&raquo;<A HREF="http://linksys-befsx41-etherfast-cable-dsl-firewall-router.home-spot.co.uk/terms/linksys-befsx41-etherfast-cable-dsl-firewall-router.html" >linksys-befsx41-etherfast-cable-&middot;&middot;&middot;ter.html</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10303728</guid>
<pubDate>Fri, 21 May 2004 22:15:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - VPN</title>
<link>http://www.dslreports.com/forum/remark,10300870</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I just spent 2 days pulling hair over this same issue - should have looked here first.  After upgrading, my connection went from flaky to worse.  Only a few sites were accessible, DNS failures, ...  My setup is pretty simple: No VPN, Nothing in DMZ, only one connected PC, not using IRC etc.  Still lots of problems.  As mentioned earlier, I also found that manually setting MTU was a bad idea - nothing made it through.  One thing I haven't seen mentioned:  When on the phone w/ Linksys support people, they mentioned at least 2 versions of BEFSX41 hardware.  Mine is apparently the older(oldest?) one.  Maybe they didn't bother to fully test against all HW versions.  No excuses for this - just bad quality or attention to detail IMHO.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10300870</guid>
<pubDate>Fri, 21 May 2004 16:19:46 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - VPN</title>
<link>http://www.dslreports.com/forum/remark,10300483</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : VPN doesn't maintain connection.  I generally have to do a warm reboot (save settings) 3 or 4 times per day.  1.45.7 was the best for VPN.  It did a very good job of maintaining a rock solid VPN tunnel connection.<br><br>What I don't understand is how does Linksys manage to screw up each firmware update.  Most often they fix two things while they screw up two other things.  I just don't get it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10300483</guid>
<pubDate>Fri, 21 May 2004 15:34:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10300385</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : 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. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10300385</guid>
<pubDate>Fri, 21 May 2004 15:21:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10300280</link>
<description><![CDATA[<A HREF="/useremail/u/972788"><b>pratttech</b></A> : I have been reviewing this thread and I was surprised at all of the errors people seem to be having with the release firmware.  I ran the FW that shipped with my router for only a few weeks till I went to 1.43.something.  That I ran for months without any errors until I recently upgraded to 1.50.18 (last week sometime).  Excepting that my router lost all of its configs and reset to default settings with this update (something that did not happen when I updated to 1.43), I have had no problems (knock on wood) at all with this router.<br><br>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.<br><br>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&#151;and X apps get really upset when their tunnel collapses ;)<br><br>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&#146;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. <br><br>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&#146;t many); it's not a high priority for me.<br><br>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?  ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10300280</guid>
<pubDate>Fri, 21 May 2004 15:08:51 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10300279</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : It didn't crash my BEFSX41. I'm using 1.50.18 firmware]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10300279</guid>
<pubDate>Fri, 21 May 2004 15:08:27 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10299886</link>
<description><![CDATA[<A HREF="/useremail/u/1010855"><b>zealex</b></A> : OK, since Flogator asked for my setup, here it is. But this is a loooooooong post<br><br>My settings:<br><br>SETUP TAB<br><br>  Basic setup sub-tab<br>    Internet Setup<br>      Internet Connection Type - PPPoE<br>    PPPoE Settings           <br>      User Name: blablabla     <br>      Password: **************     <br>      Service Name: (blank)     <br>      Connection: Keep Alive: Redial Period 30 Sec.    <br>    Optional Settings (required by some ISPs)<br>      Host Name: (blank)<br>      Domain Name: (blank)     <br>      MTU: Disable Size: 1492 (greyed out)     <br>    Network Setup            <br>      Router IP <br>      Local IP Address:   192.168.1.1     <br>      Subnet Mask:  255.255.255.0<br>    Network Address Server Settings (DHCP)<br>      Local DHCP Server: Enable<br>      Start IP Address: 192.168.1.100<br>      Number  of  Address: 50     <br>      DHCP Address Range: 192.168.1.100 to 192.168.1.149    <br>      Client Lease Time: 0 minutes (0 means one day)    <br>      DNS 1: 0.0.0.0<br>      DNS 2: 0.0.0.0<br>      DNS 3: 0.0.0.0<br>      WINS: 0.0.0.0 <br>    Time Settings<br>      Time Zone: (GMT)England<br>      Default NTP Server<br><br>  DDNS sub-tab<br>    DDNS service: Disable<br><br>  Mac address clone sub-tab<br>    Mac Clone Service: Disable<br>    Mac Address: 00-00-00-00-00-00 (greyed out)<br><br>  Advanced Routing sub-tab<br>    Advanced Routing                <br>      NAT: Enable<br>    Dynamic Routing: Disable    <br>      Transmit RIP Version: RIP1 (greyed out)<br>      Receive RIP Version: RIP1 (greyed out)<br>    Static Routing<br>      Select Entry: 1 <br>      Destination IP Address: 0.0.0.0 <br>      Subnet Mask: 0.0.0.0    <br>      Gateway: 0.0.0.0 <br>      Hop Count: 0    <br>      Interface: LAN<br><br>SECURITY TAB<br><br>  Firewall sub-tab<br>    Firewall Protection: Enabled<br>    Additional Filters<br>      Filter Proxy (not selected)<br>      Filter Cookies (not selected)  <br>      Filter Java Applets (not selected)<br>      Filter ActiveX (not selected)<br>    Block WAN Requests<br>      Block Anonymous Internet Requests: Enabled<br>      Filter Multicast: Disabled   <br>      Filter Internet NAT Redirection: Disabled   <br>      Filter IDENT(Port 113): Enabled<br><br>  VPN sub-tab (not used)<br>    VPN Passthrough<br>      IPSec Pass-Through: Enabled<br>      PPPoE Pass-Through: Enabled<br>      PPTP Pass-Through: Enabled<br>    VPN Tunnel<br>      Select Tunnel Entry: Tunnel 1<br>      VPN Tunnel: Disabled    <br>      Tunnel Name: blank<br>    <br>RESTRICT ACCESS TAB<br><br>  NOT USED<br> <br>APPLICATIONS AND GAMING TAB<br><br>  Port range forwarding sub-tab<br>    NOT USED<br>  Port Triggering sub-tab<br>    NOT USED<br>  uPnP Forwarding sub-tab<br>    All disabled; <br>      added 2 new entries for eMule program:<br>      eMule 4662 TCP 4662 192.168.1.100 enabled  <br>      eMule 4672 UDP 4672 192.168.1.100 enabled  <br>  DMZ sub-tab<br>    DMZ port: disable<br><br>ADMINISTRATION TAB<br><br>  Management sub-tab<br>    Local Router Access:<br>      Router Password: ************<br>      Re-enter to confirm:<br>    Remote Router Access<br>      Remote Upgrade: Disabled    <br>      Remote Administration: Disabled    <br>      Administration Port: 8080<br>    SNMP<br>      Disabled    <br>    Identification<br>      Device Name: Linksys BEFSX41<br>      Get Community: Public (grey)<br>      Set Community: Private (grey)<br>    UPnP<br>      UPnP: Enabled<br>      Allow users to make Configuration Changes: Enabled<br>      Allow users to Disable Internet Access: Disabled <br><br>  Log sub-tab<br>    NOT USED<br>  Diagnostics<br>    NOT USED<br>  Factory Defaults<br>    NOT USED<br>  Firmware upgrade<br>    Used to upgrade<br><br>STATUS TAB<br><br>Information<br>                <br>     Firmware Version: 1.50.18, Apr 30 2004<br>     MAC Address: ??-??-??-??-??-?? (hidden for privacy)<br>    <br>Status<br>    <br>     Login Type: PPPoE  Connected     <br>     Internet Address: XXX.XXX.XXX.XXX (hidden for privacy)<br>     Subnet Mask: 255.255.255.0    <br>     Default Gateway: 213.13.135.14    <br>     DNS 1: 194.65.100.117    <br>     DNS 2: 194.65.5.2    <br>     DNS 3: 0.0.0.0    <br>     Current Time: May 21 2004 Fri. 19:16:02 <br><br>And, like I've said before, changed MTU in XP to 1492 or some sites take forever to open or do not work at all.<br><br>Notice that I enabled uPnP in router and also enabled uPnP in XP. This enabled file sending and receiving with ICQ4 ("using firewall" option checked) and MS Messenger 6.2, and this with several friends that also use NAT routers (this is good, usually it doesn't work between two users behind NAT). <br><br>eMule works ok, All Seeing Eye (ASE) and Unreal Tournament 2003, 2004, Battlefield 1942, Battlefield Vietnam, Call of Duty and many more, all working ok (tested several continued hours of online gaming with BF and UT, some minutes with other games).<br><br>The long URL posted here by Flogator DOES NOT crash the router. It works flawlessly (and it is quick).<br><br>Trace route inside a "cmd" window using tracert CRASHES the router instantaneously.<br><br>I will stay with 1.50.18 unless I find more bugs when I start to use VPN functionality (near future). As for me, the major bug is the MTU one. If you do not set MTU in XP browsing experience is painfull.<br><br>I also tweaked <br>[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]<br>"MaxConnectionsPer1_0Server"=dword:0000000a<br>"MaxConnectionsPerServer"=dword:0000000a<br>So that internet explorer can have 10 (more than the 2 default) connections opened simultaneously, and this also helps to speed things up.<br><br>Do not know what to add more, please ask if I forgot something. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10299886</guid>
<pubDate>Fri, 21 May 2004 14:19:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10297276</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : 53.41.0.10 -&gt; 5) as in (212.100.242.19<B>5)</B> ;).<br><br>[EDIT]: If you look in the router's log, you will notice sometimes the URL is in parenthesis and some other times it is the IP address that is.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10297276</guid>
<pubDate>Fri, 21 May 2004 08:14:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10297257</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I think that my problem is that :<br><br>DHCP Remaining Time: 0:09:39<br><br>every 10 min !!! ...<br><br>someone could help me<br>i m going crazy]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10297257</guid>
<pubDate>Fri, 21 May 2004 08:08:26 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10297120</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : 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?<br>Edit: Got it, ASCII. I will check the other ones.<br>50.46.49.57 = 2.19  = 212.100.24<B>2.19</B>5<br>53.41.0.10 = 5)?? = I don't know, any idea?<br>AliM]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10297120</guid>
<pubDate>Fri, 21 May 2004 07:23:41 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10297069</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : zexalex, so you say that in 1.50.18, this link does not crash your router?  If so, can you give us some information about your setup?  Things like cable vs DSL, SPI enabled/disable, filters or not, etc would help.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10297069</guid>
<pubDate>Fri, 21 May 2004 07:03:38 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10297059</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : 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.<br><br>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 2<B>12.1</B>00.242.195 which is the destination IP address.<br><br>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.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10297059</guid>
<pubDate>Fri, 21 May 2004 07:02:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10297055</link>
<description><![CDATA[<A HREF="/useremail/u/700900"><b>Tyreman</b></A> : Tried the new 'ware(1.50.18) Didn't even get on 'net or e-mail.Yes at defaults,hard reset you name it.Tried even different mtu.Played tinkered cussed,cried. Tried back to '47 and '43 no trouble.<br>moronic isn't it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10297055</guid>
<pubDate>Fri, 21 May 2004 07:00:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10296933</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hi<br>i would like to know if someone else got this bug<br><br>I ve just buy my new befsx41 and upgraded it to 1.50.18 so i don't know if this bug is from 1.50.18 or before<br><br>I m in mode : <br>- Obtain automatically ip from ISP<br>- DHCP local Disabled<br>- DMZ on 10.0.0.1 behind DMZ port (Befsx41 in 10.0.0.138)<br>- port forwarding everything to 10.0.0.1 (lol)<br><br>my probleme is that i m disconnect every 10 min i think , i ve put the secret page Log4Manage to see the lease time of the DHCP client and it s  set to 600sec !!!<br><br>so What does it mean ?? my connexion Cut every 600sec to check the lease ?<br><br>thanks to tell me i ve you have the same problem and if you ve found a solutions <br><br>:(:(:(:(]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10296933</guid>
<pubDate>Fri, 21 May 2004 05:59:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10296831</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Please note that I also use eMule and it has NOT crashed befsx41 (had to manually open 2 ports, though).<br><br>I also use ASE (all seeing eye) for online gaming (a lot). It DOESN'T crash the router.<br><br>And yes, it crashes with tracert instantaneoulsly.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10296831</guid>
<pubDate>Fri, 21 May 2004 04:41:27 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10296825</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : NOTE: this is in response to the post by Flogator <br>About the bug-free firmware, I'm afraid that will never exists in the price range of appliances we are playing with. At best, we could eventually get a firmware with less bugs than others but don't hold your breath for bug-free.<br><br>My old Micronet router worked flawlessly for 2 years. Did not support uPnP, but it NEVER crashed. I had to have my main PC in DMZ for several things to work. Not anymore with linksys.<br><br>NOTE: this is in response to the post by Flogator <br>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?<br><br>The "long" link does NOT crash befsx41 and it responds instantly. it opens a page in Home Spot Directory with several results. Very quick.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10296825</guid>
<pubDate>Fri, 21 May 2004 04:36:17 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10296575</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : 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. <br><TT><SMALL>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<br>06:53:42,78 O udp 49.50.46.49 137 192.168.1.10 137</TT></SMALL><br>Seems like a bug also.  AliM<br><br>Edit: I got the 2nd: It was WW attempt to resolve local IP to name. If you need Etherreal capture let me know. <br><br>Edit2: Another one: &raquo;<A HREF="http://citroen-commercial-price-used-vehicle.home-spot.co.uk/terms/citroen-commercial-price-used-vehicle.html" >citroen-commercial-price-used-ve&middot;&middot;&middot;cle.html</A><br>TCP from 50.46.49.57<br><br>and &raquo;<A HREF="http://motorola-mobile-phone-accessories.home-spot.co.uk/terms/motorola-mobile-phone-accessories.html" >motorola-mobile-phone-accessorie&middot;&middot;&middot;ies.html</A><br>TCP from 53.41.0.10]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10296575</guid>
<pubDate>Fri, 21 May 2004 02:27:54 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10296470</link>
<description><![CDATA[<A HREF="/useremail/u/103636"><b>TuscanRaider</b></A> : I had 1.50.18 on for a while. A few days ago, the router started rebooting every time I did a "refresh" in All Seeing Eye. Back to 1.45.7.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10296470</guid>
<pubDate>Fri, 21 May 2004 01:56:44 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10296441</link>
<description><![CDATA[<A HREF="/useremail/u/391326"><b>CrazyM</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>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?<HR></BLOCKQUOTE><br><br>Crashed right away and seemed to take it's time coming back on it's own.<br><br>Regards,<br><br>CrazyM<br><SMALL>--<br>"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</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10296441</guid>
<pubDate>Fri, 21 May 2004 01:49:50 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10295328</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : 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?<br><br>&raquo;<A HREF="http://linksys-befsx41-etherfast-cable-dsl-firewall-router.home-spot.co.uk/terms/linksys-befsx41-etherfast-cable-dsl-firewall-router.html" >linksys-befsx41-etherfast-cable-&middot;&middot;&middot;ter.html</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10295328</guid>
<pubDate>Thu, 20 May 2004 22:51:21 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10295041</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : About the UPnP thingy.  That really depend on what you are using MSN Messenger for.  If you are simply chatting using your keyboard, you do not need to do anything.  However, if you are using the voice, video and/or file sharing, you've got to enable UPnP in the router in order for MSN Messenger to dynamically open the appropriate ports in the BEFSX41.  As stated in my previous post, you've got to enable the UPnP feature in the Administration/Management tab of the router's configuration web page (at the bottom of that page).  Also ensure that both "<I>Allow users to make Configuration Changes</I>" and "<I>Allow users to Disable Internet Access</I>" options are also enabled.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10295041</guid>
<pubDate>Thu, 20 May 2004 22:21:17 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10294794</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : JUST FOUND THE MAIL SENT BY THE DYNDNS SUPPORT TEAM, HERE IT IS:<br><br>------<br>Even after the latest firmware updates (at least the ones<br>we have seen) the DDNS client in the BEFSX41 does not work<br>correctly with our services.<br><br>In addition to not providing an option to set the Wildcard<br>and Mail Exchanger options, the DDNS client in this router<br>often fails to open and close HTTP sessions correctly,<br>resulting in update failures.<br><br>None of this is anything we can solve on our end. We can<br>not modify the update syntax to accommodate a single<br>broken update client since there are dozens of properly<br>configured update clients out there on hundreds of<br>thousands of customers machines, all or which are designed<br>to expect the current behavior.<br><br>Only Linksys can resolve this issue.<br><br>Or, disable the DDNS client in the router and use one of<br>these:<br><br>&raquo;<A HREF="http://www.dyndns.org/services/custom/clients.html" >www.dyndns.org/services/custom/clients.html</A><br><br>-- <br>Customer Support Technician<br>Dynamic Network Services, Inc.<br>&raquo;<A HREF="http://www.dyndns.org/" >www.dyndns.org/</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10294794</guid>
<pubDate>Thu, 20 May 2004 21:54:44 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10294759</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : sorry...<br><br>From Linksys:<br>We are not aware of this issue.<br><br>From DynDNS:<br>Only because they don't wish to be aware of them.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10294759</guid>
<pubDate>Thu, 20 May 2004 21:50:36 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10294736</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Well, after a long chat with Linksys and DynDNS support teams that's what i got:<br><br>: We are not aware of this issue.<br>: Only because they don't wish to be aware of them.<br><br>Linksys also asked me to replace the equipament, but since i've got the same behavior on 2 other routers i don't think i got a faulty one. But yes, i will replace it, but probably for an old SonicWall SOHO2 which seems to be far more stable, secure and reliable.<br><br>About the MSN, there are no UPnP slots configured. Am i missing something here? Do i need to manually set the msn ports?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10294736</guid>
<pubDate>Thu, 20 May 2004 21:48:59 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10294063</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : The information about the embedded DDNS not keeping the wild card and MX is very good.  Thanks for this update.  Don't know if Linksys is aware of this one but I will sure forward them that information.<br><br>About your MSN.  I guess you are referring to voice/video/files feature requiring UPnP isn't?  Assuming you have enabled UPnP in the Administration/Management tab, the only thing that comes to mind right now is the number of available UPnP entries.  The BEFSX41 currently supports only a total of five of those entries.  The UPnP agent on each computer chew up one entry each.  In your case, since you've got three PCs, it means there is only two entries left for applications.  Therefore, if you do voice on one PC, you will likely run out of UPnP resources for another PC join a conversation (each application such as voice or video chew up two entries per session).<br><br>About the bug-free firmware, I'm afraid that will never exists in the price range of appliances we are playing with.  At best, we could eventually get a firmware with less bugs than others but don't hold your breath for bug-free ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10294063</guid>
<pubDate>Thu, 20 May 2004 20:29:26 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10293845</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : One more bug to the list guys. Dunno if its newer or not!<br><br>If you're subscribing DynDNS to update a dynamic dns name be sure that you do not need "Enable Wildcard" and "Mail Exchanger" options. Since BEFSX41's firmware doesn't support those two options, every-time the router updates the WAN IP onto the DynDNS.org servers it will erase those options making impossible, specially in my case, to keep a MX record for POP3 hosting purposes over the Net.<br><br>Wanna know what linksys said about that? <br><br>Also, i could get MSN to work only in one of my 3 pcs. Any ideas?<br><br>Still looking for a bug-free firmware.<br><br>Cya,<br>Arley Silveira.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10293845</guid>
<pubDate>Thu, 20 May 2004 20:05:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10290205</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by zaqplm:</SMALL><HR>No!!! 1.50.18 does not work properly. <br><br>1. Cannot browse Internet even though I made sure all settings are according to my old 1.45.7.<br> <HR></BLOCKQUOTE><br><br>Let Me guess.... You're on DSL !!<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10290205</guid>
<pubDate>Thu, 20 May 2004 12:33:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10289977</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : No!!! 1.50.18 does not work properly. <br><br>1. Cannot browse Internet even though I made sure all settings are according to my old 1.45.7.<br>2. Run tracert will immediately crash the router.<br><br>Everytime Linksys release a firmware with all the fixes, they will also break some other functionality, especially critical ones!!!<br><br>Why? Cisco cannot afford quality programmers?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10289977</guid>
<pubDate>Thu, 20 May 2004 12:06:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10279747</link>
<description><![CDATA[<A HREF="/useremail/u/558908"><b>HaloBox</b></A> : I had mine setup that way and the extra heat would make it lock up.  After I moved things around and placed it off by itself, it ran cooler and hasn't locked up since (8 months I think).<br><br>I'm also on the 1.45.3 firmware.  I thought it was 1.45.7.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10279747</guid>
<pubDate>Wed, 19 May 2004 10:16:29 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10278604</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Can anyone explain a little bit more the "heat sensitive" question with befsx41? Mine is on top of cable modem, and this is on top of pc case, PSU below. All this gear gets very hot and I am not experiencing random reboots.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10278604</guid>
<pubDate>Wed, 19 May 2004 04:56:26 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10278578</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : gho5t, could you provide more details on "upload a file" or "webcam", coz I'm doing all of this without problems. (fw.1.45.7 - the same"). Are you on cable or DSL?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10278578</guid>
<pubDate>Wed, 19 May 2004 04:35:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10278557</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : 1.45.7 Still reboots the router whenever I try to upload a file, or run a webcam, or anything like that. Lowering MTU doesn't work. I'm not having that problem with 1.50.18 but I am having trouble with forwarding port 113, the router rebooting when I run kazaa lite and AIM disconnecting every 5 minutes. So, I guess if I need to upload something to somewhere I'll flash to 1.50.18, and if I want to chat on AIM or use IdentD for any reason I'll flash to 1.45.7. LOL! Linksys is driving me crazy. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10278557</guid>
<pubDate>Wed, 19 May 2004 04:27:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10278424</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I can't use the 1.45.7 version, considering the router reboots whenever I try to upload a file.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10278424</guid>
<pubDate>Wed, 19 May 2004 03:27:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10278381</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I've just tested kazaa lite. It DOES crash the router, INSTANTLY making it reboot. This is total crap. How can these people release such crap? I paid a lot of money for this router and it's not worth a penny in my opinion.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10278381</guid>
<pubDate>Wed, 19 May 2004 02:54:51 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10276605</link>
<description><![CDATA[<A HREF="/useremail/u/558908"><b>HaloBox</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>You can find old BEFSX41 firmware <A HREF="http://www.broadbandreports.com/forum/remark,9155542">here</A>.  Then choose your battles from all these versions.  My recommendation is still firmware 1.45.7.<br> <HR></BLOCKQUOTE><br><br>I'm sticking with the 1.45.7 code myself.  It's really a shame we can't get a well tested stable set of code.<br><br>For those of you that experience reboots or locks without doing the tracert/MTU stuff, make sure your SX41 is properly cooled.  They are known to be sensitive to heat.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10276605</guid>
<pubDate>Tue, 18 May 2004 22:17:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10272129</link>
<description><![CDATA[<A HREF="/useremail/u/807431"><b>Anub1s</b></A> : Launching Kazaa Lite crashes the router with this firmware!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10272129</guid>
<pubDate>Tue, 18 May 2004 13:47:38 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10270570</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : As pointed out earlier in this thread, I was debugging a VPN problem.  I have just concluded that the bug called <B><I>VPN broken when remote gateway set to Any</I></B> is back in firmware 1.50.18 :(.<br><br>As a bit of history, back in firmware 1.45.3, a bug was introduced.  Such bug is preventing the BEFSX41 to act as a VPN server when configured as PPPoE (xDSL).  After pushing hard to get the issue fixed, Linksys generated firmware 1.45.3_t1 that fixed the problem.  Fortunately, this fix is still present in 1.45.7 ;).  However, in firmware 1.50.18, the problem is back (not 100% sure but likely back in 1.50.9 as well).<br><br>Bottom line, for xDSL users that needs VPN, your best bet is to stay with BEFSX41 firmware 1.45.7 at the moment.  As you may guess, this means that the remote site on xDSL I had upgraded to 1.50.18...  I have downgraded it back to 1.45.7.  I will keep 1.50.18 on my cable site for few more weeks since I am now chasing another bug :(.  Meanwhile, I have notified Linksys about this.  I'll keep you all posted.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10270570</guid>
<pubDate>Tue, 18 May 2004 10:16:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10260962</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I got to 1492 after experimenting as described in the guide elesewhere in this forum. As for the ie 10 open sessions, my setup pages open ok, just one small delay in the logo in the bottom.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10260962</guid>
<pubDate>Mon, 17 May 2004 04:46:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10260477</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : aktrader, yes Netscape or Mozilla will prompt for chinese fonts. Ignore it. It's "wrong" code in a part of html:<br>"<TT>Content-Language content=zh-tw.</TT>" It should be =en-us. At Linksys are very sloppy programmers.<br>AliM]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10260477</guid>
<pubDate>Mon, 17 May 2004 01:27:39 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10260397</link>
<description><![CDATA[<A HREF="/useremail/u/1008464"><b>aktrader</b></A> : Not sure if anyone else noticed it, but by clicking on the Administration tab using NN7.1, I got prompted to download chineese fonts.  Not sure whether this was due to the UPnp option being enabled or others, but found that somewhat strange.<br><br>Also, Router had 1.45.6 firmware out of the box. Which now seems strange given 1.45.3 was the official release at the time. Unable to locate this firmware to flush back.  <br><br>AK]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10260397</guid>
<pubDate>Mon, 17 May 2004 01:09:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10259946</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : You can find old BEFSX41 firmware <A HREF="http://www.broadbandreports.com/forum/remark,9155542">here</A>.  Then choose your battles from all these versions.  My recommendation is still firmware 1.45.7.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10259946</guid>
<pubDate>Sun, 16 May 2004 23:48:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10259930</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : In my mind, BEFSX41 firmware 1.45.7 is still the best one available so far.  You can find this firmware <A HREF="http://www.broadbandreports.com/forum/remark,9155542">here</A>.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10259930</guid>
<pubDate>Sun, 16 May 2004 23:46:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10258621</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I downloaded the 1.50.18 upgrade yesterday and installed it, tested that it was communicating with my home LAN and with Google, everything seemed fine, then I went out.  This morning, I discovered that I could ping any site on the Internet, but I could only browse to a handful of sites (Google and PayPal worked; can't think of others off the top of my head; this site did NOT work). :o  Called Linksys tech support and talked to some nimrod who tried to blame it on my system. :P  Then he hung up on me. :mad: Talked to some other nimrod and convinced him that the problem was the flash, but he indicated that my router was now fried and I would have to get a new one.  :mad:  I managed to talk him into sending me a downgrade to the flash, and he said he would, but he never did. :mad: Finally, I connected directly to my modem and found this discussion.  Nice to know I'm not the only one experiencing this problem; from the reaction at Linksys, you'd think they never heard it before. :huh:<br><br>Anyway... I found the downgrade to 1.45.7 in the discussion groups here, downgraded the firmware using the tool built into the router, did a long reset, fixed all my settings, and it looks like it's working now!!! :D  Thanks to all who contributed ideas in this forum.  For what it's worth to anyone else that may be having this problem: I'm connecting to the Internet through Verizon DSL using PPPOE on this router.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10258621</guid>
<pubDate>Sun, 16 May 2004 21:00:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10258567</link>
<description><![CDATA[<A HREF="/useremail/u/653870"><b>thongsai</b></A> : pppoe doesnt work!! any 1 know where i can get old firmware??<br><SMALL>--<br>&raquo;<A HREF="http://thongsai-roms.shorturl.com/" >thongsai-roms.shorturl.com/</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10258567</guid>
<pubDate>Sun, 16 May 2004 20:52:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10257756</link>
<description><![CDATA[<A HREF="/useremail/u/1008326"><b>d12342</b></A> : hi all,<br>i just bought this sx41 router. it keeps reboot itself when i have a large download or use certain other dowload programs.  I upgraded to 1.50.18 directly once i have the router installed, so did not try the old firmware. <br>Anyway, i called linksys support many times.  They said this is not a known problem and they don't get complaints about this problem. they said it is my router problem.  i told them that i exchange it 2 times and still the same problem.  It is just very strange to me that how come they said it is not a known problem when all of us here suffer with this new firmware and have to roll back.  Anyway, any suggestion of which firmware is most stable as of now? and where do i download it?<br>THanks all.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10257756</guid>
<pubDate>Sun, 16 May 2004 19:02:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10255820</link>
<description><![CDATA[<A HREF="/useremail/u/826521"><b>sauce</b></A> : I've been missing the action so I went straight from 1.45.7 or whatever to 1.50.18.  Immediatley I noticed port fwding did not work, and the router rebooted itself a few hours later.  I went to 1.50.9 after that.  Worked fine for a day, then port fwding stopped working no matter what I did.  I am now back at 1.45.7.  Reason for upgrading was, I was hoping to fix a problem I have with 1.45.7 where port fwding stops working about once a week and the router needs a soft reboot to fix it.<br><br>I LOVE LINKSYS.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10255820</guid>
<pubDate>Sun, 16 May 2004 13:52:08 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10254965</link>
<description><![CDATA[<A HREF="/useremail/u/1007211"><b>Papa_Gulf</b></A> :  <BLOCKQUOTE><SMALL>said by  Eko <A HREF="/useremail/u/1001203"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Just a side note, Papa_Gulf. Did you reboot the computer after  you set static IP? You need to.<br>If you can get to the router but not to the net, it must be DNS issue.<br>Again: <br>IP      : 192.168.1.71<br>Sub.mask: 255.255.255.0<br>Def.gate: 192.168.1.1<br><br>DNS1:  your dns1  (alternatively put 192.168.1.1 and try)<br>DNS2:  your dns2  (alternatively don't put anything)<br><br>And again REBOOT!<br>AliM<br> <HR></BLOCKQUOTE><br>Worked like a champ thanks!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10254965</guid>
<pubDate>Sun, 16 May 2004 10:48:37 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10254573</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  ticker5 <A HREF="/useremail/u/286760"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Its beginning to look more and more like the thread:<br>&raquo;<A HREF="/forum/remark,10000597~mode=flat">BEFSX41- Its the year 2010 and FW 20.50.9 is out</A><br> <HR></BLOCKQUOTE><br><br>If it wasn't so scary, it would be funny!!<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10254573</guid>
<pubDate>Sun, 16 May 2004 09:32:24 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10254563</link>
<description><![CDATA[<A HREF="/useremail/u/286760"><b>ticker5</b></A> : Its beginning to look more and more like the thread:<br>&raquo;<A HREF="/forum/remark,10000597~mode=flat">BEFSX41- Its the year 2010 and FW 20.50.9 is out</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10254563</guid>
<pubDate>Sun, 16 May 2004 09:29:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10254446</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : I've been trading emails with what might be an automated response generator at Linksys Tech support.<br><br>A couple pages back, I typed in my list of problems... Well, I cut & pasted that to Linksys (Regarding V1.50.18).<br><br>They replied with V1.45.7 firmware, and an appology.<br><br>I responded that V1.45.7 had much the same problems as V1.50.18, and documented the differences that I was able to discern from the good people in this thread.<br><br>They responded with V1.50.18 firmware... and an appology.<br><br>So I responded with a link to this thread...<br><br>(Sighs deeply)!<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10254446</guid>
<pubDate>Sun, 16 May 2004 08:55:55 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10252228</link>
<description><![CDATA[<A HREF="/useremail/u/905323"><b>NJim</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>NJim, aside the trace route that you claim is working in 1.50.9, there are lots of other bugs in it that are fixed in 1.50.18.  I guess it is just a matter of opinion as which one is best.  My opinion is if you like 1.50.9, you will like 1.50.18 better.  Then again, this is just my opinion ;).<br> <HR></BLOCKQUOTE><br>I upgraded this afternoon. After 4 (unsolicited) reboots in 15 minutes, I went back to 1.50.9. <br><br>I guess I'm a poster child for "YMMV." :hmm:]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10252228</guid>
<pubDate>Sat, 15 May 2004 21:51:01 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10251661</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : No, that's not his site OR one of all the new TLD's. That belongs to old TLD, com. <br>Didn't even know that address existed :P]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10251661</guid>
<pubDate>Sat, 15 May 2004 20:37:43 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10251481</link>
<description><![CDATA[<A HREF="/useremail/u/286760"><b>ticker5</b></A> : Isn't www.baptisa.god.com]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10251481</guid>
<pubDate>Sat, 15 May 2004 20:11:27 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10250545</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : Milltek, check your messages<br><SMALL>--<br>.·´¯`·-·´¯`WayuU´¯`·-·´¯`·.</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10250545</guid>
<pubDate>Sat, 15 May 2004 17:43:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10250229</link>
<description><![CDATA[<A HREF="/useremail/u/1006769"><b>Hertzman</b></A> :  <BLOCKQUOTE><SMALL>said by  NJim <A HREF="/useremail/u/905323"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>I was thinking of somthing on the serverside like HttpResponse.Redirect().<br> <HR></BLOCKQUOTE><br><br>That's the same thing, it just tells the browser which page to fetch. (scratches head).<br>Are you thinking of something like Server.Transfer()?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10250229</guid>
<pubDate>Sat, 15 May 2004 16:59:23 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10249885</link>
<description><![CDATA[<A HREF="/useremail/u/905323"><b>NJim</b></A> :  <BLOCKQUOTE><SMALL>said by  Hertzman <A HREF="/useremail/u/1006769"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR> <br><br>A redirect just tells the browser which page to fetch so a direct link or redirect should be the same :o<br> <HR></BLOCKQUOTE><br><br>I was thinking of somthing on the serverside like <br>HttpResponse.Redirect(). <br><br>The point is moot as I did some checking, and when you click, say, Security, all that is behind it is an href:<br><br>&lt;A href='Firewall.htm'&gt;Security&lt;/A&gt;<br><br>I have no idea why it has trouble with that, while a shortcut on my toolbar works perfectly.<br><br>I hate having to reverse engineer and debug code I paid for anyway.:(]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10249885</guid>
<pubDate>Sat, 15 May 2004 16:05:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10246860</link>
<description><![CDATA[<A HREF="/useremail/u/1006769"><b>Hertzman</b></A> :  <BLOCKQUOTE><SMALL>said by  NJim <A HREF="/useremail/u/905323"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>This would seem to indicate that they are using some kind of redirect rather than a simple link.<br><HR></BLOCKQUOTE><br><br>A redirect just tells the browser which page to fetch so a direct link or redirect should be the same :o]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10246860</guid>
<pubDate>Sat, 15 May 2004 05:44:43 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10246203</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : racinmustang, good catch.  It is very likely that NetMeeting uses ICMP-based trace route.  If it does, then it will crash the router in 1.50.18 like every body else.  I must admit I do not know NetMeeting well enough to say whether it uses such ICMP-based trace route or not.  From the description you are providing, it is possible.<br><br>In such case, you have to downgrade to 1.45.7 to keep your existing applications running.  Thanks again for this update.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10246203</guid>
<pubDate>Sat, 15 May 2004 01:27:26 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10246184</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : sympatico01, it is normal the keys do not exist.  In order to tweak IE, you've got to create the keys manually and assigning the values.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10246184</guid>
<pubDate>Sat, 15 May 2004 01:23:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10244546</link>
<description><![CDATA[<A HREF="/useremail/u/910469"><b>MillTek</b></A> : QUOTE}  <br><br>One such URL is a site of one of the founders of Internet, Joe Baptista. Try surfing to his site www.baptisa.god. If you can reach it you are not controlled.<br><br>If help is needed for you to get access to all of Internet then just ask me or any other here who knows about it.<br><br>Regards<br><br>{ENDQUOTE<br><br>Ok, I tried the site (baptista.god) and can't get there. What gives???????????????<br><br>Jim]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10244546</guid>
<pubDate>Fri, 14 May 2004 21:32:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10244220</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : <B>Just some info on simultaneous HTTP sessions</B><br><br>The defaults are:<br>HTTP 1.0 Servers = 4 connections<br>HTTP 1.1 Servers = 2 connections<br><br>The HTTP 1.0 restriction is not a mandated specification.<br>The HTTP 1.1 is a mandated specification.<br>___________<br><br>I've always set both to 10 myself too and it works fine. First thing I do after fresh Win install :)<br>___________<br><br>And now for some fun, and quite serious too.<br>All the talk here about people having trouble accessing Internet just made me remember my own not too normal settings.<br>I guess lots of you here already know this and have it changed but for the ones who don't know:<br>Most Internet users are not allowed to the whole Internet, ie government controlled. <br>The idea of a totally free internet is not quite working. There is a so called Internet2 that most can't access. Lots of addresses are not surfable for you then.<br>Most ISPs either don't care or don't know about this.<br><br>One such URL is a site of one of the founders of Internet, Joe Baptista. Try surfing to his site www.baptisa.god. If you can reach it you are not controlled.<br><br>If help is needed for you to get access to all of Internet then just ask me or any other here who knows about it.<br><br>Regards<br><SMALL>--<br>.·´¯`·-·´¯`WayuU´¯`·-·´¯`·. [img]&raquo;<A HREF="http://www.danasoft.com/sig/WayuU.jpg[/img]" >www.danasoft.com/sig/WayuU.jpg[/img]</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10244220</guid>
<pubDate>Fri, 14 May 2004 20:49:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10244128</link>
<description><![CDATA[<A HREF="/useremail/u/990099"><b>racinmustang</b></A> : Hi all,<br><br>While this thread seems to have been run into the ground, I was surprised that NOBODY noticed that Microsoft NETMEETING fails on this firmware 1.50.18 and in fact causes the router to reboot!  Certainly this is a side-effect of the ICMP problem, right Flogator?<br><br>I so badly hoped to stay on 1.50.18 for the duration, but can not do so because I use MS NETMEETING remote desktop sharing in one situation.  It's back to 1.45.7 for reliability.<br><br>(Note that Windows XP DOES include Netmeeting hidden away, but you must first configure it with START > RUN > CONF.EXE    You can not however download NETMEETING to install on XP separately.)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10244128</guid>
<pubDate>Fri, 14 May 2004 20:34:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10243374</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : See the link below for tweaking options:<br><br>&raquo;<A HREF="http://www.speedguide.net/read_articles.php?id=157" >www.speedguide.net/read_articles.php?id=157</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10243374</guid>
<pubDate>Fri, 14 May 2004 18:59:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10243032</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : For this in Win2000<br><br>[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]<br><br>"MaxConnectionsPer1_0Server"=dword:0000000a<br>"MaxConnectionsPerServer"=dword:0000000a<br><br>Do I have to create a key, a string of dword, because the entries do not exist? Is it normal?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10243032</guid>
<pubDate>Fri, 14 May 2004 18:19:49 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10242462</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Papa_Gulf, I fully support AliM on this one.  Rebooting the PC is required.  Your setup is not unusual.  In fact, I've got one server on my cable site which is configured as static IP.  I can surf the web no problem.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10242462</guid>
<pubDate>Fri, 14 May 2004 17:11:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10242304</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Just a side note, Papa_Gulf. Did you reboot the computer after  you set static IP? You need to.<br>If you can get to the router but not to the net, it must be DNS issue.<br>Again: <br>IP      : 192.168.1.71<br>Sub.mask: 255.255.255.0<br>Def.gate: 192.168.1.1<br><br>DNS1:  your dns1  (alternatively put 192.168.1.1 and try)<br>DNS2:  your dns2  (alternatively don't put anything)<br><br>And again REBOOT!<br>AliM]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10242304</guid>
<pubDate>Fri, 14 May 2004 16:52:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10242194</link>
<description><![CDATA[<A HREF="/useremail/u/1007211"><b>Papa_Gulf</b></A> : About your 192.168.1.71 issues. One disadvantages of using static IP is you are stuck in manually configuring the default gateway as well as the DNS server. To gain internet access back, you will have to extract the DNS server information from the router (see the Status tab) and apply it to your PC. The default gateway MUST be the LAN IP address of the router (i.e. 192.168.1.1). That should solve your problems.<br><br>Did all that and it would see the router but nothing else worked :(  My LAN is 3 PC's ( XP PRO, XP Home, and W2K) and one ps2 (witch I can't seen to get to work) through the SX41 two PC 's on Port 1 and 2 the 3rd port to the EZXS16w to another PC PS2 on port 4 (DMZ where linksys said to put it and turn on DMZ). Took the XP Pro box installed the static IP installed the  (cox.net) dns on the PC and couldn't get any web IM email or anything until I went back to DHCP ( except &raquo;<A HREF="http://192.168.1.1" >192.168.1.1</A>) I thought the same thing.  Can I make the Xp pro box a DNS server and just point at cox.net  DNS?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10242194</guid>
<pubDate>Fri, 14 May 2004 16:42:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10241769</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Sympatico01, YES.  These settings are good for W2K as well.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10241769</guid>
<pubDate>Fri, 14 May 2004 15:49:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10241760</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Papa_Gulf, for your info (and perhaps for the benefit of everyone else), I will keep 1.50.18 for a little longer.  There are two rationales for doing this.  First, we will all have to switch to the new GUI eventually; may as well get use to it now.  Secondly, I haven't finish testing the firmware.  Not only I am debugging a VPN problem but most of other bugs show up after running the firmware for a while.<br><br>About your 192.168.1.71 issues.  One disadvantages of using static IP is you are stuck in manually configuring the default gateway as well as the DNS server.  To gain internet access back, you will have to extract the DNS server information from the router (see the Status tab) and apply it to your PC.  The default gateway MUST be the LAN IP address of the router (i.e. 192.168.1.1).  That should solve your problems.<br><br>Most importantly... Welcome to the DSLR/BBR forum Papa_Gulf ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10241760</guid>
<pubDate>Fri, 14 May 2004 15:48:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10241715</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : cghh, likelihood is that your TiVo is using short packets.  Therefore, MTU isn't an issue there.  You will start seeing problems when some packets are 1493 bytes or more.  Even without tweaking the MTU, when you go and visit some sites, if  the negotiated MSS value is 1492 or below, then you will not experience any problems.  Everything starts to fall apart when MSS is being negotiated above that value for DSL users ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10241715</guid>
<pubDate>Fri, 14 May 2004 15:43:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10241102</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : OFF TOPIC: <br><br><I> I use XP so I also tweaked <br><br>[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]<br><br>"MaxConnectionsPer1_0Server"=dword:0000000a<br>"MaxConnectionsPerServer"=dword:0000000a<br><br>So that internet explorer can have 10 (more than the 2 default) connections opened simultaneously, and this also helps to speed things up.<br></I><br><B> Is this setting good for Win2000 machine??? </B><br><br>Thanks Folgator for the shorcut, I will try it. By the way I am using 1.45.7 on both end. <br><br>With a previous version (I think it was 1.44.11t) I used to lost my VPN connection between the 2 routers and have to reset the one at the office (CABLE), because this one has a static IP address and wait for the tunnel for connection, as opposed to the one at home (DSL) I just configured it so I connect to the office. But in order to prevent the lost of connection, I have put a timer in the wall outlet and connect the router in its plug (both at the office and home) therefore every day at night the timer shut off (for 30 minutes the minimum I could get on this timer). It force the machine to reboot and the tunnel got reconnected. This is the way I found, and prevent me to go to the office for the reboot of the router. Anyone has others ideas???<br>  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10241102</guid>
<pubDate>Fri, 14 May 2004 14:26:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10241059</link>
<description><![CDATA[<A HREF="/useremail/u/1007211"><b>Papa_Gulf</b></A> : Flogator<br> Are u going to keep your router running 1.50.18 or go back to 1.45.7? The reason I ask is after reading this thread 1.50.18 has some problems but for my home network I don't think it will effect.  Here&#146;s some thing strange I tried to setup one static ip 192.168.1.71 but the computer couldn't get to the Internet with 1.45.7.  <br><br>I would like to take a min and thank everyone in this forum I got my first BEFX41 from newegg on 4 Nov 03 installed and had problems from day one after many hours of (useless) tech support from linksys and the EZXS16W crappin out I but in rma they were prompt to send the replacements got them two days ago. Came I think with firmware 1.44.3.  First thing I did was hit this forum to find out what I should do first. Downloaded 1.45.7 and its bee like a dream instead of a nightmare like before. Linksys would be well advised to hire this forum as tech support :)  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10241059</guid>
<pubDate>Fri, 14 May 2004 14:20:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10240669</link>
<description><![CDATA[<A HREF="/useremail/u/287036"><b>cghh</b></A> : I have DSL, and tweaked the MTU on my PCs to 1492, and they work fine with 1.50.18. But my TiVo is also getting its schedule updates just fine over this connection, even though I cannot tweak its MTU. (TiVo runs BSD Linux.)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10240669</guid>
<pubDate>Fri, 14 May 2004 13:34:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10240564</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : zexalex, I'm glad the MTU tweak is working for you as well.  Thanks for the update.  The magic value of 1492 will work with most DSL ISP.  However, don't be fooled!  Some DSL ISP uses a bigger PPPoE overhead thus leaving fewer bytes for payload.  It is find trying 1492.  If it does not work still, please follow the link I provided earlier to figure out which value is adequate for your ISP.<br><br>About Internet Explorer tweak.  I am glad you know about this tweak as well.  Since the very beginning I used this trick, I did noticed some considerable improvement in connecting to web servers.  On the other hand, this is precisely this tweak that causes the BEFSX41's configuration web page to take forever to load some images (as reported by other users).  For fun, if you decrease this value to 1, loading the router's web page will be quick and reliable.  However, surfing the rest of the web will not be as quick :(.  Since you are usually optimizing for net access (and not viewing the router's configuration web page that often anyways), The above tweak you suggested is wonderful ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10240564</guid>
<pubDate>Fri, 14 May 2004 13:21:55 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10240511</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : About the MTU settings in your W2K machines.  Simply follow these instructions:<br><br>&raquo;<A HREF="/faq/tweaks">Tweaking FAQ</A> &raquo;<A HREF="/faq/695">Max MTU: How do I find mine?</A><br>&raquo;<A HREF="/faq/tweaks">Tweaking FAQ</A> &raquo;<A HREF="/faq/578">DRTCP: How do I use it and what are all these settings?</A><br><br>About the VPN problems you are having.  I am currently debugging a VPN problem myself.  In firmware 1.45.3, Linksys introduced a VPN bug which prevent VPN tunnel from connecting if one end is cable and the other is DSL.  That bug was fixed in 1.45.7.  Last night, I was doing some experiment (since I have upgraded on of my DSL site to 1.50.18) but my VPN tunnel was not coming up between the two sites.  Can't say for sure, but is is very well possible that firmware 1.50.18 re-introduce this problem.  Please to not draw any conclusion yet but keep in mind you might be hit by this bug.  I'll do more experiment over the week-end and report my findings.  Meanwhile, you may try to downgrade your DSL site to 1.45.7 as I have proven in the past that as long as the DSL site is on 1.44.11t or earlier or 1.45.7, the VPN tunnel will come up independently which version is used on the cable site.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10240511</guid>
<pubDate>Fri, 14 May 2004 13:12:35 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10240504</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Reply to previous post: <br><br>MTU is disabled by default in in the first router setup page (1492 setting shows grey).<br><br>If not, disable it (and 1492 setting should show up grey).<br><br>If you are on DSL you will soon find out that some pages will not open (and some will take too long to open). <br><br>In order for things to work properly (due to some sort of bug in the BEFSX41 firmware) you need to set MTU in each PC. So you set MTU in the registry to 1492 - I used drtcp.exe and I changed JUST the MTU setting - did not touch the other settings, but you can also change this in the registry without a tool.<br><br>I'm on DSL and after fiddling with MTU as stated in another post, I found out that 1492 is the proper setting (not rocket science for this). If you are on cable the setting is 1500 (I think). Surfing and gaming are OK, maybe even faster than before (I had an old micronet router).<br><br>OFF TOPIC: <br><br>I use XP so I also tweaked <br><br>[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]<br><br>"MaxConnectionsPer1_0Server"=dword:0000000a<br>"MaxConnectionsPerServer"=dword:0000000a<br><br>So that internet explorer can have 10 (more than the 2 default) connections opened simultaneously, and this also helps to speed things up.<br><br>Now I'm trying to find out more about Universal PnP since some say it's a plague some say it works. <br><br>Everything is still working ok. As I said during next week I will have more time to play and do stuff and I will report accordingly.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10240504</guid>
<pubDate>Fri, 14 May 2004 13:11:54 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10240388</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Ok, Flogator.  Told you I was a newbie, so forgive if I don't answer correctly, and sound totally dense.  I have the router DHCP currently set to Local DHCP disabled. IPconfig shows the only info on subnet as being related to the router.  I am a single home user, Win XP. The pc is configured to find IP address and DNS automatically, and shows DHCP enabled. Don't know if that is sufficient for you. It is probably not worth bothering with, as long as I can get to the net now  I was previously having some of the problems listed in the other posts, along with some others, not related to this topic). But thanks for any help. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10240388</guid>
<pubDate>Fri, 14 May 2004 12:58:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10240127</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have win2000 and router BEFSX41. I am on DSL. I went to the link to setup the MTU. But it is difficult to understand. Can someone recapitulate what I need to do in order to have my MTU setting correctly in order to use the latest firmware. I have 2 computers running on Win2000 that are connected to the router. I also have the same router at the office and there I have 5 machine with Win2000. I am using a VPN tunnel to link the 2 routers. Note that at the office it is cable (I should not have any problem to upgrade to the latest firmware, but I am afraid that after nothing work anymore, interner or VPN).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10240127</guid>
<pubDate>Fri, 14 May 2004 12:31:37 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10239852</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Let's see if I have any suggestion...  First you'll have to tell me a bit more about your setup.  How many DHCP servers do you have (including the one on the BEFSX41)?  If more than one, could you please list the subnet of each of the server?<br><br>Normally, you only have one DHCP server.  You normally use the one of the router, however, you don't have to.  If you have a DHCP server on your LAN and prefer that one instead, then you can always disable the router one and keep using your other DHCP server.  If you do, you will still have to configure your other DHCP server such that it advertise the proper default gateway, DNS server, etc.  The beauty of using the router's DHCP server is it will figure it all out for you.  If you are using a separate DHCP server, then you've got to configure it to do what you want.<br><br>No matter what it is, the router's LAN side cannot acquire an address from a DHCP server.  Its address must be static period.  Once you provided additional information, I can formulate additional recommendation.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10239852</guid>
<pubDate>Fri, 14 May 2004 12:00:29 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10239716</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Thanks, Flogator.  <br>Any suggestions? When talking to Linksys they directed me to use a static IP to get to the internet.  I read somewhere, possibly in the original manual, that using DHCP on both pc and router, there may be a conflict, which apparently there were since I could not reach the internet.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10239716</guid>
<pubDate>Fri, 14 May 2004 11:44:15 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10239472</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : korat, if you can work without the router's embedded DHCP server, that's great.  However, if you really want to make use of it, I am sure that there will be some tweaking you can do to make it works.<br><br>I have four BEFSX41.  I now have two running 1.50.18 (one on DSL and one or cable).  Both of these are using the router's embedded DHCP server to distribute IP addresses on all PC on the LAN and it is working fine.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10239472</guid>
<pubDate>Fri, 14 May 2004 11:10:59 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10239458</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : NJim, aside the trace route that you claim is working in 1.50.9, there are lots of other bugs in it that are fixed in 1.50.18.  I guess it is just a matter of opinion as which one is best.  My opinion is if you like 1.50.9, you will like 1.50.18 better.  Then again, this is just my opinion ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10239458</guid>
<pubDate>Fri, 14 May 2004 11:08:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10239439</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Zexalex, thank you for your update.  That's actually refreshing to see positive feedback such as yours.  It further emphasis the importance little details.  Especially the MTU for DSL users ;).  Thanks again.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10239439</guid>
<pubDate>Fri, 14 May 2004 11:05:29 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10238897</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hi, I'm a newbie.  But I have been fiddling with the new firmware for two days.  I found that if I have DHCP enabled on both my pc and the router, I can't get to any web pages.  So I disabled it on the router.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10238897</guid>
<pubDate>Fri, 14 May 2004 09:37:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10238614</link>
<description><![CDATA[<A HREF="/useremail/u/905323"><b>NJim</b></A> :  <BLOCKQUOTE><SMALL>said by  WayuU <A HREF="/useremail/u/963087"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Is ver 1.50.9 ICMP tracert able?<br> <HR></BLOCKQUOTE><br><br>Yes, per an experiment I did a minute ago; no reboot and I got the tracert output.<br>--<br>Jim]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10238614</guid>
<pubDate>Fri, 14 May 2004 08:48:05 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10238548</link>
<description><![CDATA[<A HREF="/useremail/u/905323"><b>NJim</b></A> :  <BLOCKQUOTE><SMALL>said by Zexalex:</SMALL><HR><br><br>My 2 cents: upgrade to 1.50.18, set the MTU on PC side, do a full long >30sec reset before you start working. Or do not upgrade at all. Or buy something else (what?) - As someone said, Netgear is also not an option.<br><br>Thanks for all the good job done to everyone.<br> <HR></BLOCKQUOTE><br><br>I'm running 1.50.9. Does 1.50.18 do ANYTHING better than 1.50.9?<br>Thanks,<br>--<br>Jim]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10238548</guid>
<pubDate>Fri, 14 May 2004 08:37:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10238512</link>
<description><![CDATA[<A HREF="/useremail/u/905323"><b>NJim</b></A> :  <BLOCKQUOTE><SMALL>said by  WayuU <A HREF="/useremail/u/963087"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR> <br>I've had issues with the pages not showing up on earlier versions too. But now it is worse. <br>All I do to get them to show up is to hit the refresh button (without CTRL). Sometimes now I have to hit it up to, but not more than, 3 times to get the page to show up.<br> <HR></BLOCKQUOTE><br><br>I'm running the 1.50.9 FW and what I did was to create a link folder on my IE toolbar with 'Favorite' router pages, e.g. Administration, Restrict Access, etc. The shortcuts work flawlessly. <br><br>This would seem to indicate that they are using some kind of redirect rather than a simple link.<br>--<br>Jim]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10238512</guid>
<pubDate>Fri, 14 May 2004 08:30:40 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10237845</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hi everybody, bought the Linksys befsx41 last Sunday. I had an old micronet router and thought it was time to upgrade to the brand that everyone uses, Cisco owned, blablabla<br><br>Plugged it in and no problems. Saw the new web interface for the 1.50.18 and decided, well, why not?<br><br>Things were not smooth, and had to do a full 30sec reset in order to get it working (things were simply not working).<br><br>After browsing here... well... I still have my old micronet router sitting over there in its box... <br><br>Did the MTU trick on the PC side (i'm on DSL). Much better. Some sites that did not open immediatly started to open. Even router html setup pages seem to load faster.<br><br>Enabled the firewall. No file transfer with Messenger or ICQ. But this is always a pain whenever I'm chatting with someone that also has NAT. Yesterday I enabled the UPnP both in the router and in the PC. Messenger file transfer worked. This is an improvement from my previous setup.<br><br>Everything seems to be working, I would not even try to test tracert (no need for it anyway).<br><br>Next week (going out for the weekend) I will try to use eMule and Kazaa and check if heavy load crashes the router as some are saying here. <br><br>Tested online gaming. This also puts some load on the line. No problems while playing BF and BFV for some hours.<br><br>Anyone can comment on universal PnP usage in router / PC (with XP all patches, no s/w firewall).<br><br>My 2 cents: upgrade to 1.50.18, set the MTU on PC side, do a full long >30sec reset before you start working. Or do not upgrade at all. Or buy something else (what?) - As someone said, Netgear is also not an option.<br><br>Thanks for all the good job done to everyone.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10237845</guid>
<pubDate>Fri, 14 May 2004 03:38:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10237796</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : PARC, now even shows 06.05.2004  20:22:00. I compared this one with one Flogator provided, they are the same. You can do it yourself, the command in windows is "comp file1 file2".  AliM<br><br>EDIT: That's funny: Now (after 55 min.) it's again 05.05.2004 16:32:00.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10237796</guid>
<pubDate>Fri, 14 May 2004 03:15:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10237722</link>
<description><![CDATA[<A HREF="/useremail/u/760751"><b>PARC</b></A> : Hi guys.<br><br>I tried downloading this firmware last week and I noticed that the file <B>befsx41_v1.50.18_code.bin</B>  : Last Modified was <B>05/05/2004</B> did linksys change anything?<br><br>You can check it out here. ::    &raquo;<small>ftp</small>://<A HREF="ftp://ftp.linksys.com/pub/network/">ftp.linksys.com/pub/network/</A><br><br>Thanks!<br><br>PARC]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10237722</guid>
<pubDate>Fri, 14 May 2004 02:44:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10235112</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : One of my sites just got switched from cable to DSL.  Since I had to shut it down for the switch, I have decided to do some experiments ;).  Guess what I did?  I have just flashed 1.50.18 on this BEFSX41 and surprisingly, my internet access is working beautifully.<br><br>This site is currently on a low cost DSL service so throughput is not that great (but that's the ISP service this site is using, not the router).  Nevertheless, I am writing those lines on a laptop at that location hooked up to a BEFSX41 running 1.50.18 that is on DSL.<br><br>This site does not suffer from any of the problems that were reported before.  Mind you, <B>I HAVE TWEAKED THE MTU OF THE LAPTOP ACCORDINGLY</B>, so perhaps it makes a difference.  For the users experiencing problems, please try tweaking the MTU as I recommended earlier to see if your problems will be solved.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10235112</guid>
<pubDate>Thu, 13 May 2004 20:48:41 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10233590</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : Dear Mr. Wilson Coudon,<br> <br>Thank you for contacting Linksys Technical Support.<br><br>You indicated that you got BEFSX41 firewall router.  It seems that you are having technical difficulties after updating the firmware to 1.50.18.  I apologize for the inconvinience this has caused.  I would suggest to downgrade the firmware of the router to 1.45.7 to resolve on your concern.  I'l just email you the firmware that you need.<br><br>Hope this will solve the technical difficulty you're having.<br><br>If you have further questions, please contact us at (800) 326-7114 or send us an email at support@linksys.com so that we may further assist you.  Please use this phone number given as reference for future support calls.<br><br>Have a pleasant day!<br><br>Sincerely,<br><br>Jose R. Sarmiento<br>Linksys &#150; A Division of Cisco Systems, Inc.<br>Product Support Specialist<br>800-326-7114<br>support@linksys.com <br><br>This 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. <br><br>If you are responding to this e-mail, please append or attach all previous correspondence as a point of reference.<br><br>On Tue, 11 May 2004 18:49:17 -0700, wb9iph@ameritech.net wrote:<br>> I forgot one&#133;.. Sorry<br>> <br>>  <br>> <br>> I don&#146;t mean to be flippant, but here are some things you should consider<br>> fixing before your next Firmware for BEFSX41&#133;..   <br>> <br>>  <br>> <br>> Problems in V1.50.18<br>> <br>>  <br>> <br>>  <br>> <br>> Java Speedtests Should not reboot system Independent of Filters being <br>> enabled, or disabled.<br>> <br>> Tracerts, and the Pingplotter program should not reboot the system.<br>> <br>> Come to think of it, No Program should re-boot the Linky BEFSX41 !!<br>> <br>> Edit list of PC's In Filter area should contain an "All PC's" <br>> Selection, as in prior versions, (or explain in detail why not!).<br>> <br>> You should not encounter White screens while maneuvering through the <br>> setup menus... If you select a menu, it, and not a white screen, <br>> should display.<br>> <br>> No MTU Problems. You should be able to useV1.5.X (and Above) on DSL <br>> without jumping through hoops to get it to work... And Browse...<br>> <br>> A current User's Manual should accompany the next version of Firmware, <br>> with specifics in Filters, and all other new Setup selections, so we <br>> are not guessing,and can make 'educated' decisions, not wild guesses, <br>> on these new features, as we are not mind-readers.<br>> <br>> Backup & Restore should be able to restore all settings to their <br>> original state from which they were backed up..<br>> <br>> Filters should contain Input as well as Output blocking...<br>> <br>>  <br>> <br>>             When Filters are enabled, you should not have to Disable <br>> Advanced Hardware Firewall in order to get the Logs to display all the <br>> blocking information correctly (which filter).<br>> <br>> <br>> <br>> You should test the next version of software on BOTH DSL and Cable <br>> systems for all features, as intended, before tossing them out to the <br>> public...<br>> <br>>  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10233590</guid>
<pubDate>Thu, 13 May 2004 17:39:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10233567</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : So I made a list and sent it to Linksys.... Actually I sent two lists, separated by a couple hours.<br><br>EACH was answered:    Dear Mr. Wilson Coudon .... and attached to each was V1.45.7 firmware.<br><br>WHO?   I checked the bottom of the emails, both had my email, and my signature at the bottom.... <br><br>But I guess I'm no longer Jan Janowski, I'm Mr. Wilson Coudon...<br><br>I replied that I'm not Wilson Coudon, and suggested that not only does V1.45.7 have many of the problems that V1.50.18 had, they should browse here for more in-depth information on V1.50.18<br><br>??????????????????????????????<br><br>I won't say anything more, or I'll get in trouble.<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10233567</guid>
<pubDate>Thu, 13 May 2004 17:36:09 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10233057</link>
<description><![CDATA[<A HREF="/useremail/u/1006769"><b>Hertzman</b></A> : To balance all the negative posts I'd like to say that I've been using my BEFSX41 with the 1.44.3 it came with without any problems at all since last dec. Ethernet 10Mbit, one single PC.<br><br>You're doing a great job though and I'm following your findings with great interest. :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10233057</guid>
<pubDate>Thu, 13 May 2004 16:37:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10230726</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> :  <BLOCKQUOTE><SMALL>said by  jbob <A HREF="/useremail/u/996768"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR> I wonder if this is a hardware or driver issue?  Different drivers may or may not allow this.  Perhaps MS OS branded drivers have less functionality. <HR></BLOCKQUOTE><br><br>Though it is possible that different drivers allow different features, the card that linksyspains showed, and the card that I am using are different versions of the 3c905b. Linksyspains showed the XL version. <br><SMALL>--<br>DAMOX <B><A HREF="http://www.dslreports.com/forum/remark,1564398;root=disco;mode=flat#1564398"> Proud to be a member of Team Discovery</B></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10230726</guid>
<pubDate>Thu, 13 May 2004 12:02:43 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10230655</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> :  <BLOCKQUOTE><SMALL>said by  linksyspains <A HREF="/useremail/u/933782"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR> I find it frustrating that each new firmware seems to have had more work done on the WEB interface and the extraneous options than just making the product solid. It gets back to what sells, and apparently features sell over quality. <HR></BLOCKQUOTE><br><br>I can understand your frustration! I do agree that stability and performance come first!  <br><SMALL>--<br>DAMOX <B><A HREF="http://www.dslreports.com/forum/remark,1564398;root=disco;mode=flat#1564398"> Proud to be a member of Team Discovery</B></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10230655</guid>
<pubDate>Thu, 13 May 2004 11:52:54 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10230603</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : J_E_B, my PPPoE experience was similar only 1.44.3 doesn't work for me. The box resets itself every few hours - very annoying.<br><br>dpmox, good point on just pulling out the Linksys entirely, but that assumes your son knows your ISP password. I guess if you're using a cable modem you don't need a password - I hadn't thought of that.<br><br>I've heard rumors of boxes out there that require all clients to be authenticated by Norton Internet Security  to get access to the WAN. That combined with a version of "NIS" with remote administration would make for a good home solution.<br><br>Still, I have to agree that for most home applications, the approach Linksys uses today is probably the easiest, and covers 99% of needs. <br><br>I find it frustrating that each new firmware seems to have had more work done on the WEB interface and the extraneous options than just making the product solid. It gets back to what sells, and apparently features sell over quality.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10230603</guid>
<pubDate>Thu, 13 May 2004 11:43:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10230580</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : This is getting off thread.  Perhaps we should start another one as I am interested in this as well.  I wonder if this is a hardware or driver issue?  Different drivers may or may not allow this.  Perhaps MS OS branded drivers have less functionality.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10230580</guid>
<pubDate>Thu, 13 May 2004 11:40:13 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10230265</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> :  <BLOCKQUOTE><SMALL>said by  linksyspains <A HREF="/useremail/u/933782"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>I would rather see content filtering and WEB access pushed down to the clients. I don't think it belongs in the router box. At least not in these sub $100 boxes. <HR></BLOCKQUOTE><br><br>I personally appreciate the ability to block access at the router. It allows me to control internet access on the fly, without without having to visit my son's computer and make such adjustments. I don't care so much about content filtering on the router though. In the past I have used used content filtering/access control software, especially when my kids were younger, and I was always having to reload my boy's  system, I suspect because he was trying to hack the software. <br><br>As far as my son devising a way to get past the router when I am not home, there is nothing preventing him from simply unplugging the firewall from the cable modem, and plugging his connection in. Of course he'd be in a world of hurt if I found out . . . At this point though, I don't think he's figured out how he is being blocked. I think he thought it was because he domain account was disabled because he couldn't print, so I enabled his account. Before long he'll figure it out, and When he does it will be interesting to see what he will do! ;)     <br><SMALL>--<br>DAMOX <B><A HREF="http://www.dslreports.com/forum/remark,1564398;root=disco;mode=flat#1564398"> Proud to be a member of Team Discovery</B></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10230265</guid>
<pubDate>Thu, 13 May 2004 10:56:41 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10230071</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> : That's interesting. The cards I am using don't have that feature.<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10230071?c=593106&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG TITLE="40134 bytes" BORDER=0 WIDTH=427 HEIGHT=470 SRC="/r0/download/593106~8c4c3bc879d5333e0956b060497d1ce5/3com2.jpg"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10230071</guid>
<pubDate>Thu, 13 May 2004 10:30:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10229806</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : ftrace dwld links in old Flogator post are dead (r1ch.net). Site is up, dwlds not working.<br><br>Here are new, for now, working links:<br>ftrace  = &raquo;<A HREF="http://www.enetis.net/support/downloads/ftrace.exe" >www.enetis.net/support/downloads/ftrace.exe</A><br>wftrace = &raquo;<A HREF="http://www.enetis.net/support/downloads/wftrace.exe" >www.enetis.net/support/downloads/wftrace.exe</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10229806</guid>
<pubDate>Thu, 13 May 2004 09:51:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10227276</link>
<description><![CDATA[<A HREF="/useremail/u/799337"><b>gtyler</b></A> : And I thought that Optimum Online's DNS servers went down. The firmware seemed to work for a while, but it must have been the browser caching previous DNS entries before I upgraded. Let's try 1.50.09.........]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10227276</guid>
<pubDate>Wed, 12 May 2004 23:12:26 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10227271</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : <I>Oh well. If anyone has got a stable DSL/PPPoE experience (with the SPI firewall enabled), I'd love to hear about it.</I><br><br>I've been reading these posts with some interest.  I bought my BEFSX41 around a year ago, and it's DSL PPPoE performance was so rock solid I just assumed that was what was to be expected from a cheap router, and that all the technical problems had been solved long ago.  There was only one nagging problem -- if I left a telnet session idle I would lose it after precisely 10 minutes.  I wasn't even sure this was the router; it might have been my ISP.  (Note that when I say my DSL connection was solid I what mean is that whenever I tried to make a HTTP or telnet or FTP connection it always worked.  This is really all I want out of my router, that and the firewall functionality).<br><br>Then one day I noticed the 1.50.9 upgrade on the Linksys site, and I decided that it couldn't hurt to give it a try.    That's when everything went to hell.  At first the router wouldn't work at all.  But that was because I had tried do the upgrade while I was still connected to the Internet.  I reflashed several times and got my best result after poking at the reset button.  The router would actually stay up for an indeterminate period, and the telnet timeout was gone.  But the connection would eventually go bad, so that the only way I could reestablish Internet connectivity was by yanking the router's plug and restarting it.  (And even that didn't always work -- sometimes I would have to reboot my PC).  Not only that, but sometime even when telnet and my browser were working FTP would fail.  I could establish a connection, and even change directories, but I couldn't list directories or download anything.  Yanking the plug often fixed this too.<br><br>Eventually this got tiresome, so I tried the vaunted 1.45.7.  (Which I had read about here, and downloaded from here).  No good -- same problems.  So I went back to 1.44.3, which may be what I had originally, and now I'm right back where I started.  My DSL connection is rock solid, FTP works, but the goddamn telnet timeout is back.  If it weren't for that I'd be happy, since I never use VPN or tracert or the like.  I do use the SPI firewall though, which is what prompted this post.  I started out with stability, and I just assumed that was the norm.  I am truly amazed at all the problems I am seeing here!  Anyway, I don't think I'm even going to try flashing 1.50.18 -- it hardly looks worth it from what I'm reading in this thread.  I'm not poor, and unless Linksys comes up with the golden upgrade my next stop will probably be something from some other company.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10227271</guid>
<pubDate>Wed, 12 May 2004 23:12:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10226466</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Just for fun, I have tried the Email Alerts feature in the BEFSX41.  It seems to be working.  Though I am not too sure how useful it really is since it only monitor SPI events.  It does not monitor intrusion attempts dropped by the NAT firewall nor the outbound accesses.  Nevertheless, I tried it, it is working, I don't find it particularly useful so I have disabled it now.  You can read more about the experiment in the post below.<br><br>&raquo;<A HREF="/forum/remark,10226409">Re: [wired] Befsx41 1.50.18 SNMP email test</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10226466</guid>
<pubDate>Wed, 12 May 2004 21:58:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10226299</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : I used to use VisualRoute too, when I had IP filtering. Not working with URL filtering. Latest 8.0 vers keep getting remotely modified not to give results.<br><br>--------------<br><br>Thx Flogator. I'll find it. All I needed was a name.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10226299</guid>
<pubDate>Wed, 12 May 2004 21:45:35 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10224701</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> : I use VisualRoute.  It defaults to ICMP but has an option to use UDP.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10224701</guid>
<pubDate>Wed, 12 May 2004 18:47:37 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10224443</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Hmm... I guess I will double post again.  Please find in one of my posts about ICMP-based trace route, a link to an application called ftrace.  The link of the post is below:<br><br>&raquo;<A HREF="/forum/remark,10174949">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10224443</guid>
<pubDate>Wed, 12 May 2004 18:20:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10224362</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : Hmm...<br><br>So no one knows of an UDP traceroute app for Windows! ?<br><br>I know of Netscantools Pro 2004 and Ping Plotter 2.5 but they are impossible to get with p2p :(]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10224362</guid>
<pubDate>Wed, 12 May 2004 18:08:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10222086</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : dpmox,<br><br>Addendum: Oddly on my machine, its the 3c905b that does have the MAC address option:<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10222086?c=592536&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG TITLE="50156 bytes" BORDER=0 WIDTH=422 HEIGHT=473 SRC="/r0/download/592536~1648444cec77823d75e9c06af3f7ca81/3com.jpg"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10222086</guid>
<pubDate>Wed, 12 May 2004 13:45:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10222021</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : dpmox, my reply was aimed more at the Linksys and not so much your settings.<br><br>Since your reply, I checked the two Ethernet cards in my machine here. You are right in that only one of them (the older 3COM) has an option to change the MAC address. Perhaps that option is falling out of favor.<br><br>Now assuming he found a card where he can set the MAC address (like the 3COM), he could:<br>1. ping your machine, get your MAC address<br>2. Disconnect Ethernet cable on your machine<br>3. Program his machine with your machine's MAC address<br>4. Swap it all back before you come home :)<br><br>OK, I'm being a little silly. I push this because I would rather see content filtering and WEB access pushed down to the clients. I don't think it belongs in the router box. At least not in these sub $100 boxes.<br><br>Or let me put it this way. If Linksys is putting 33% of their time into Route/NAT, 33% into VPN, and 33% into access and content filtering, I'd rather see 70% Route/NAT, 30% VPN, and 0% access and content filtering - at least until they get Router/NAT working.<br><br>All these cutesy little time/day based access filters are worthless if no one can browse the web, or if the box resets itself every hour.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10222021</guid>
<pubDate>Wed, 12 May 2004 13:38:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10221012</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> : A good point! ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10221012</guid>
<pubDate>Wed, 12 May 2004 11:32:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10220954</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Good eye AliM ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10220954</guid>
<pubDate>Wed, 12 May 2004 11:25:13 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10220876</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : dpmox, that's why Flogator's two filters approach is more immune to changing IP or MAC, because you're only allowing some MAC access, all others are blocked. Whatever your son do, he's still blocked. My one filter approach is denying certain MAC or IP. If it's changed, it will pass thru.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10220876</guid>
<pubDate>Wed, 12 May 2004 11:16:24 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10220611</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> : [QUOTE= linksyspains <A HREF="/useremail/u/933782"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A> So now all he has to do is go to his Ethernet driver setup in Windows and change his MAC address to some random value and he's back online?? Not a very secure access filter .... [/QUOTE]<br><br>First of all, for the cards I have installed in these machines (3c905bs), there is no option for changing the macs that I can see. I've looked at all the settings, and I've been through the registry, and I've found nothing. However, he could download a tool like SMAC, and that would probably do the trick or he could swap his NIC out with one of the others I have laying around. However, all that would be futile because while my son can change both the IP and the mac, should he have the mind to do so, I check the Wallwatcher logs regularly, and I would notice if he was accessing the internet. Should he change the mac and IP, I would take away his local administrative privileges on his computer. I have his domain account disabled, and fixed is so he couldn't log on to any other computer in the house. I figure that's about as prohibitive as it gets. Of course I could always take away his computer.  <br><SMALL>--<br>DAMOX <B><A HREF="http://www.dslreports.com/forum/remark,1564398;root=disco;mode=flat#1564398"> Proud to be a member of Team Discovery</B></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10220611</guid>
<pubDate>Wed, 12 May 2004 10:41:37 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10220573</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : RE: Is Linksys all that bad?<br><br>Assuming you need a home router, I think you're stuck with one of these products. Take a look at the D-Link and Netgear forums and you'll see some pretty similar posts. I honestly don't know which is best.<br><br>If my Dad asked me what to do today, I would have told him to buy a BEFSR41 for $30 and put Norton Internet Security on all his machines.<br><br>However, I've been seeing a lot of posts saying that the BEFSR41's with upgraded firmware out there are now rebooting themselves frequently. <br><br>I'd like to say that I have a BEFSR41 with firmware that is at least 2 years old (I'd have to go check it if someone wants the version number), and it has no problems what so ever. Now I don't use it for anything but NAT, so I can't vouch for VPN tunnels, etc..<br><br>One thing you should realize is that the BEFSR41 offers relatively poor firewall protection. I frequently find Internet machines trying to connect "backwards" through established NAT sessions on my machine. These are currently being filtered by Norton Internet Security on each PC client.<br><br>What I would like is a SPI firewall to help prevent this (although I'll continue to run Norton). So I bought the BEFSX41 last year. <B>I have never been able to get the BEFSX41 stable on my PPPoE connection with any version of firmware!! They either don't forward traffic, or the router reboots every few hours.</B> So for now, the BEFSR41 is the family's connection to the internet, and the BEFSX41 is toy I tinker with whenever a new firmware is released. I should also note that I only try firmware either from the Linksys site, or e-mailed to me directly from Linksys. So perhaps one of these "beta" firmwares are OK.<br><br>I'm absolutely shocked by the poor quality of these routers. It goes to show you that name brand recognition, aggressive marketing, and predatory pricing with win out over product quality every time.<br><br>But in answer to the original question, I don't know if the D-Link or Netgear versions are any better.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10220573</guid>
<pubDate>Wed, 12 May 2004 10:36:29 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10220149</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : Is Linksys router AS bad as it appears in this Linksys forum, compared to other routers in same price range?<br>Or is this, as so often, just an exaggeration?<br><br>I would really like to know this, and to get some links too to information on tests of other routers being that much better and in same price range. That will help me in recommendations to others and to future acquisitions.<br><br>Also, anyone got a recommendation for a good network toolkit with alternatives to ICMP traceroute?<br>I have an ooold netscantools pro. Want recommendations on others.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10220149</guid>
<pubDate>Wed, 12 May 2004 09:37:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10219922</link>
<description><![CDATA[<A HREF="/useremail/u/641121"><b>MrMoke</b></A> : Tony- Yours is the only kind of feedback that Linksys is likely to respond to. Over the last two years Linksys products that require firmware, like the BEFSX41, have failed to fulfill their marketing promises in spite of brisk sales. The company's self-destructive nature regarding immature and malfunctioning firmware releases seems to have accelerated since the Cisco takeover, and we are now forced to use the least broken version, while some brave souls on this forum serve as the unpaid QA team.<br><br>If more people would read this forum "before" they purchase, rather than "after", I suspect Linksys sales would start to decline.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10219922</guid>
<pubDate>Wed, 12 May 2004 09:00:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10219657</link>
<description><![CDATA[<A HREF="/useremail/u/560501"><b>Tony</b></A> : I was ready to pull the trigger on one of these units but now I'm unsure.  Seems to be be a pile of problems.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10219657</guid>
<pubDate>Wed, 12 May 2004 08:00:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10219294</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : just thought i would add my 2 cents.<br><br>updated to 1.50.18, like everyone else, would not surf with mtu enabled, disabled i could surf fine.  tracert causes router to reboot, but i don't normally use that anyways.  However, it would seem that extreme loads on the router caused it to reboot as well or maybe the program i was using was exploiting the icmp vulnerability.  router would reboot after several minutes of using Azureus, a bittorrent client (a filesharing protocol for those who do not know).  It would reboot, reconnect and repeat every other minute or so afterwards.  this is after a total reset and painstakingly setting the router back up to the config i had with the older (1.44.xx i think) firmware i had before.  also it seems that port forwarding the appropriate port i needed for Azureus was not work, or as soon as a remote tcp connection was created, the router would reboot.  according to my logs, Azureus never successfully manage to create a remote tcp connection even with the correct port forwarded.  i am assuming that before it could create a remote tcp connection, or as soon as it did, the router would reboot.  flashed back to 1.50.9, reset and config router again.  same problem.  now back to the only other firmware i could find at ftp.linksys.com/pun/network, 1.45.3, and everything is working fine; at least no reboots and port forwarding is working as it should.  any news on the next firmware update or dare we hope for the next one?<br><br>AceXMachine<br><br>'double click on Internet Explorer'<br>'double click?  how many times is that?']]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10219294</guid>
<pubDate>Wed, 12 May 2004 04:59:09 EDT</pubDate>
</item>

<item>
<title>Another Filter Bug with 1.50.18</title>
<link>http://www.dslreports.com/forum/remark,10219283</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hi, <br>I have been testing the 1.50.18 firmware. I want to block a range of ports for internet access, but leave some open. <br>This works fine on the older 1.4x firmware, but on this firmware if you specify a range of ports it doesn't block it at all.<br>ie, setup a new filter to allow internet access, then add block http access with the dropdown (port 80 will appear), set the pc ip in the pc list, save and reboot = it blocks web.<br>Then add a new rule to block TCP port 80 to 81, set the filter to use that rule, save and reboot = web browsing is fine.<br><br>Does anyone else have this issue? Any known fixes?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10219283</guid>
<pubDate>Wed, 12 May 2004 04:43:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10218665</link>
<description><![CDATA[<A HREF="/useremail/u/996454"><b>humphreysa</b></A> : Too frequently the router stops send and/or receiving packets. The router doesn't crash, that is it keeps responding to HTTP so that I can warm reset it by re-saving the password. And that works for a few minutes or so, and then we're stuck again.<br><br>I got rid of the BEFSR41 and upgraded to the BEFSX41 for this very reason. I worked great for the past few months.<br>I tried the 1.50.9 and now the 1.50 18 firmware versions, and it started yesterday, after the 1.50.18 was loaded. I downgraded to the 1.50.9 version, but within a few hours it was evident that the issue was not addressed. And now I've gone back to 1.45.7. with the same behavior. :-(<br><br>Any ideas of where I could look, or what I should be looking for?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10218665</guid>
<pubDate>Wed, 12 May 2004 01:18:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10218557</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hi guys !<br>Here we are again with the same  old story .... <br>Mr flogator : clap clap : . your work  is priceless .<br><br>I dont understand how can a company like linksys do so many mistakes.<br>I do regret buying this router.<br><br>But anyway ... so far my router with the 1.50.18  firmware "seems" stable. <br>I havent touched the MTU option yet .. but í´ll be doing my testing later.<br><br>3 questions for now :<br><br>1: 1.45.7 or  1.50.18  ? <br>- i guess 1.50.18   is worth to keep or am i wrong.<br><br>2: Anyone here has been having problems with ftp server/client  with 1.50.18 ?<br>- I´m not sure if some options are enabled will cause  ftp problems.<br><br>3: what are the 3 best routers out there ? Brand/model. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10218557</guid>
<pubDate>Wed, 12 May 2004 01:00:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10218010</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : I should have mentioned one other detail. When PPPoE is selected, you can't select an MTU greater than 1492. So everyone that uses PPPoE is 1492 or less by default. Thus what I tested tonight is the same thing that didn't work last night.<br><br>I didn't set my PC side MTU down, but I did see the TCP session was negotiating 1492. I believe that the TCP standard states that both peers must use the lowest of the advertised MTU.<br><br>If someone else doesn't solve this one in the meantime, perhaps I can borrow a hub from the office tomorrow. By looking at the packet that isn't getting through, perhaps the "bug" will become obvious. I know now that "hotmail" always fails. Last night it seemed less consistent what worked and what didn't.<br><br>The family is back on the Internet, so I'm stuck for the night with the BEFSR41.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10218010</guid>
<pubDate>Tue, 11 May 2004 23:48:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10217848</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : linksyspains, that's a good starting point.  So you do see a difference?  Youhoo! Another problem partially explained.  So by manipulating the MTU settings, even though it stays disabled, seems to have some kind of effect.  So we now have to explain the other part which is why some sites are still inaccessible.<br><br>Could you please tell me if you have tweaked the MTU of your PCs on the LAN side?  I might be wrong but I suspect you haven't.  I am wondering if the combination of both this secret recipe plus the PC MTU tweak is the full explanation of the DSL users problems.  In any case, I would gratefully appreciate if you could try the PC MTU tweak described in this <A HREF="http://www.broadbandreports.com/faq/tweaks#4">Tweak FAQ</A> page.  Don't forget to reboot your PC for the tweak to take effect.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10217848</guid>
<pubDate>Tue, 11 May 2004 23:30:39 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10217524</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : RE: DSL USERS PLEASE READ<br><br>So what is the point of having the MTU check with the ability for "enable" and "disable" if its always on??? :)<br><br>Still, you appear to be correct. I'm experimenting with it now with the MTU "disabled" but set to 1492. The MTU is being knocked down appropriately.<br><br>I can do some browsing (like this site), but I can't get to any .NET sites, including "hotmail". Explorer starts sending SACK messages back to the HTTP server, meaning some packet hasn't made it through. Obviously, it never does. The Linksys log doesn't show any packet as being filtered, but I can see in Ethereal that the packet is indeed missing (at least from my PC's point of view).<br><br>So I think its a problem besides the MTU, but perhaps related. The connection did negotiate a TCP MSS of 1452, which seems correct.<br><br>I would need a second PC and a HUB to see traffic on both sides of the Linksys to know what's happening, and I don't have a hub - sorry.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10217524</guid>
<pubDate>Tue, 11 May 2004 22:55:57 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10217360</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : <HR><br>because by default, everyone who is not on the Deny List is Allowed! However, because that mac was entered in both places, it defaulted to Allow. Once I removed him from the Allowed list, my son's computer could not access the network. ...<br><HR><br><br>So now all he has to do is go to his Ethernet driver setup in Windows and change his MAC address to some random value and he's back online?? Not a very secure access filter ....]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10217360</guid>
<pubDate>Tue, 11 May 2004 22:40:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10217223</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> : Thanks for the response Alim and Flogator. Sorry for the misinformation guys! Actually, after you posted I went back and checked and found that the mac address for my son's computer was entered in the lists for both the "Allow" and the "Deny" Internet Access. You don't actually have to enter any mac addresses or IPs in the Allow, because by default, everyone who is not on the Deny List is Allowed! However, because that mac was entered in both places, it defaulted to Allow. Once I removed him from the Allowed list, my son's computer could not access the network. Not sure how that happened, I may have done that inadvertently.<br><br>So, for the record, "Restricted Access" does work after all. Again, I apologize for the misinformation! <br><SMALL>--<br>DAMOX <B><A HREF="http://www.dslreports.com/forum/remark,1564398;root=disco;mode=flat#1564398"> Proud to be a member of Team Discovery</B></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10217223</guid>
<pubDate>Tue, 11 May 2004 22:24:18 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10217204</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Ok, if you want the list of issues in 1.50.18 that I am currently tracking, here goes.  I am just providing the titles, hopefully these are obvious enough.  If not, IM me and I can explain each of them:<br><br><U>Bugs introduced by 1.50.18</U>:<br>- ICMP-based trace route utility crashes the router<br>- Enabling MTU blocks internet traffic<br>- Some router's configuration web page components takes forever to load<br>- Access to router's configuration web pages sometimes return a blank page<br>- The 'All PCs' check box has disappeared from 'Edit List' filter dialog<br>- <B><I>[currently investigating]</I></B> PPPoE issues related to MTU<br><br><U>Bugs or limitations present in 1.45.7 and that are still present in 1.50.18</U>:<br>- Strange logs with VPN passthrough<br>- VPN shared secret limited to 24 characters<br>- No VPN connect button in manual keying<br>- Filter URL/KeyWord match logs are corrupted when SPI is firewall enabled<br>- Filter logs do not indicate which filter number was hit<br>- Log date problem<br><br>My latest report to Linksys does contain all of these bugs except the one about PPPoE that we are currently investigating.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10217204</guid>
<pubDate>Tue, 11 May 2004 22:20:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10217065</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : linksyspains, your previous statement is not accurate.  You do not need the MTU option in the router in order to get PPPoE.  By definition, you will never see MTU problems on the WAN side as it is physically limited by the modem capability of delivering PPPoE.  On the LAN side, you could have such MTU problems.  However, if you follow my advice of tweaking the MTU on every PC on your LAN, then, you should be able to solve that later problem.<br><br>About the TCP comment.  When you establish a TCP connection, both end-points are negotiating the MSS by using TCP options in the first SYN packet exchange.  That value is derived by the MTU of the device (a PC in this case).  If you lower your PC's MTU, then when establishing connection, the MSS will be negotiated accordingly.<br><br><CENTER><STRONG>DSL USERS PLEASE READ</STRONG></CENTER><br><br>Now, your post have stimulated my brain and perhaps I may have a clue as to what is going on.  In firmware 1.45.7, I have proven that the BEFSX41 is actually altering the MSS negotiation based on its own MTU value.  Perhaps the the PPPoE problems that you guys are all seeing is due to the fact that the router is altering the MSS negotiation bug because the MTU option is disabled, perhaps it raise up the MSS when it shouldn't.  So if someone on DSL wants to try this potential workaround (I don't know if it will work since my test unit is on cable), here is an experiment:<br><br>1) Enable and set MTU to desired value (i.e. 1492)<br>2) Hit the "Save Settings" button<br>3) Disabled MTU (and the original MTU value you set in step 1 remain in the deactivated field)<br>4) Hit the "Save Settings" button<br><br>Is this procedure helps you guys?  Even if I am on cable, I can proceed with these steps and after sniffing, my MSS is negotiated at the lowered value.  So I suspect it will work for you.  If it does, then that's another bug we can document and forward to Linksys.  Please someone with PPPoE problems try this and report the result.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10217065</guid>
<pubDate>Tue, 11 May 2004 22:04:27 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10216653</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  Tachyon <A HREF="/useremail/u/993621"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Flogator....<br><br> I like your idea about more than just one person writing in to Linksys about the FW problems.  Maybe the squeaky wheel will get greased. (and not in the Chicago mob sort of way)  <br> <HR></BLOCKQUOTE><br><br>Here's my suggestions: (Not in any Particular Order!)<br><br>Java Speedtests Should not reboot system Independent of  Filters being enabled, or disabled.<br><br>Tracerts, and the Pingplotter program should not reboot the system.<br><br>Come to think of it, No Program should re-boot the Linky BEFSX41 !!<br><br>Edit list of PC's In Filter area should contain an "All PC's" Selection, as in prior versions, (or explain in detail why not!).<br><br>You should not encounter White screens while maneuvering through the setup menus...  If you select a menu, it, and not a white screen, should display.<br><br>No MTU Problems.  You should be able to use V1.5.X (and Above) on DSL without jumping through hoops to get it to work...  And Browse...<br><br>A current User's Manual should accompany the next version of Firmware, with specifics in Filters, and all other new Setup selections, so we are not guessing, and can make 'educated' decisions, not wild guesses, on these new features, as we are not mind-readers.<br><br>Backup & Restore should be able to restore all settings to their original state from which they were backed up..<br><br>Filters should contain Input as well as Output blocking...<br><br>When Filters are enabled, you should not have to Disable Advanced Hardware Firewall in order to get the Logs to display all the blocking information correctly<br><br>You should test the next version of software on BOTH DSL and Cable systems for all features, as intended, before tossing them out to the public...<br><br>I'll bet I missed a couple!!! ;)<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10216653</guid>
<pubDate>Tue, 11 May 2004 21:19:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10214528</link>
<description><![CDATA[<A HREF="/useremail/u/993621"><b>Tachyon</b></A> : Flogator....<br><br> I like your idea about more than just one person writing in to Linksys about the FW problems. Could you summarize the issues so that i can translate in my own words and pass along to Linksys. Maybe the squeaky wheel will get greased. (and not in the Chicago mob sort of way)  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10214528</guid>
<pubDate>Tue, 11 May 2004 17:27:40 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10214162</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : The IP frag question was just to confirm that you need to use the MTU option if you have PPPoE. Since the Linksys does not reassemble IP, there is no way to make PPPoE work without modifying the all client machines. <br><br>This is because if both TCP peers believe they are on Ethernet (and they are), then they'll use an MTU suitable to Ethernet (1500). How silly of them not to know there is a router between them that can't send 1500 byte packets (because of PPPoE) and won't fragment or reassemble IP :).<br><br>So bottom line is that until MTU works, PPPoE is a dead issue with the latest firmware.<br><br>To release the firmware with such an apparent lack of testing is entirely inexcusable. I could see this happening if my Uncle decided to make his own home router out of his old Apple //e, but Linksys (Cisco?!?!?!). Wow!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10214162</guid>
<pubDate>Tue, 11 May 2004 16:44:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10213907</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Illjuschin, everything is possible mon ami.  Actually, back in firmware 1.44.13, Linksys did manage to break the VPN NetBIOS broadcast feature simply because they were not recalculating the checksum for those packets :(.  I catch it pretty easily using packet sniffing.<br><br>However, in this case, we are talking about packet getting in to the router from the WAN side.  Then if the checksum is the problem, then it means the problem is likely during verification of the checksum.  Perhaps the new firmware performs the field mapping before verifying the checksum.  I honestly don't know but is possible.  You are correct about the fact that any modification done to the IP header affects its checksum so is any modification done to the UDP/TCP header affects its checksum as well.<br><br>Nevertheless, when MTU is enabled, packets with the "Don't Fragment" bit set can travel from LAN-to-WAN direction but just don't travel at all from WAN-to-LAN.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10213907</guid>
<pubDate>Tue, 11 May 2004 16:18:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10213739</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : I have the same issue that Linksyspains has mentionned. I am DSL Bell Sympatico. Now back to 1.45.7]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10213739</guid>
<pubDate>Tue, 11 May 2004 15:58:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10213543</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hello Flugator<br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Does the Linksys even reassemble IP fragmented packets before applying the de-NAT?<HR></BLOCKQUOTE><br>What's the intention of your question?<br><br>I have the idea of something getting wrong with the recalculating of the header checksum. Isn't that calculation affected by the change of any header field (TTL, options, addresses, ...)? Will packets eventionally be dropped if the checksum is incorrect? Therefore I thought about a bug in the corresponding algorithms. Do you think it could be possible?<br><br>Illjuschin]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10213543</guid>
<pubDate>Tue, 11 May 2004 15:39:40 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10213359</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Don't know for sure if ICMP trace route is broken in 1.50.9 but my guess is it's broken there as well.  You can only be sure by trying your self.  You can get the 1.50.9 straight from Linksys FTP site <A HREF="ftp://ftp.linksys.com/pub/network/BEFSX41_v1.50.9_code.bin">here</A>.  May I remind you that 1.50.9 was a real fiasco though.  So if you don't like 1.50.18, chances are you will hate 1.50.9 even more.  But that is your choice.  Here are a few threads discussing the 1.50.9 fiasco if you feel like reading ;).<br><br>&raquo;<A HREF="/forum/remark,9763871~mode=flat">BEFSX41 FW 1.50.9		Mar 17, 04</A><br>&raquo;<A HREF="/forum/remark,9800713~mode=flat">[wired] Firmware 1.50.9  Problems on befsx41</A><br>&raquo;<A HREF="/forum/remark,9922791~mode=flat">BEFSX41 firm 1.50.9</A><br><br>My recommendation is still to stay away from 1.50.9 but we have the luxury of living in a free society :).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10213359</guid>
<pubDate>Tue, 11 May 2004 15:16:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10212940</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : Is ver 1.50.9 ICMP tracert able?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10212940</guid>
<pubDate>Tue, 11 May 2004 14:25:55 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10212744</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : I realize this thread is now getting huge.  That's the trade off of centralizing everything about a firmware release.  In any case, the MTU recommendation has already been provided before, please take a moment reading through this post:<br><br>&raquo;<A HREF="/forum/remark,10192468">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A><br><br>About fragmentation and reassembly, I am sorry to say but the BEFSX41 has no clue how to do that :(.  At best, the BEFSX41 will be dropping packets violating MTU settings.  Don't get too mad, pretty much none of the small broadband router do fragmentation anyways.  Instead, these small appliances use the common TCP options to alter the MSS (Maximum Segment Size) negotiation.  Basically, that's precisely what most of small broadband router use the MTU value for.  Nevertheless, the BEFSX41 does not perform fragmentation.<br><br>As for the DSL/PPPoE thingy, you do not seem to be the only one that experience such problem.  However, many users seem to be able to use their DSL connection with the router on 1.50.18 by following the MTU guideline provided in the link above.  You may want to try this out.  If after all that trouble, you still can't use your DSL connection with 1.50.18, I may only suggest to downgrade to 1.45.7 until we find out exactly what is causing that.<br><br>I've got to admin that my BEFSX41 test unit is on cable.  I've got two remote sites on DSL but for now, I do not want to destabilize them until I am feeling better about 1.50.18.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10212744</guid>
<pubDate>Tue, 11 May 2004 14:03:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10212633</link>
<description><![CDATA[<A HREF="/useremail/u/933782"><b>linksyspains</b></A> : I also failed to get the new firmware working with DSL. Its probably MTU related, since I don't see how PPPoE can possibly work transparently without MTU modification in the NAT layer. <br><br>Does the Linksys even reassemble IP fragmented packets before applying the de-NAT?<br><br>Anyhow, my first mistake was not resetting to factory defaults because even though all my filters were deleted, the log still showed packets matching the filter. After the reset, everything seemed fine. Surfing was notably slower, but seemed to be working. Then, after about 30 seconds, I was unable to access anything over the WEB.<br><br>I wonder if the Linksys is susceptible to some sort of attack that someone is sending to my IP address? When I swap back to my old BEFSR41, everything is fine. I have never been able to to get the BEFSX41 stable. It either resets itself after a few hours, or simply fails to forward traffic.<br><br>I have not tried to track the problem down with a sniffer. It didn't help that 20 minutes into my experiments, the family started demanding Internet.<br><br>Oh well. If anyone has got a stable DSL/PPPoE experience (with the SPI firewall enabled), I'd love to hear about it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10212633</guid>
<pubDate>Tue, 11 May 2004 13:48:21 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10211455</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : dpmox, I must agree, the filters in the restricted area can be confusing time to time.  I can assure you, however, that these work properly in firmware 1.50.18.  To accomplish what you are trying to do, follow these steps to establish two filters:<br><br><B><U>Filter 1</U></B><br>Internet Access Policy: 1<br>Enter Policy Name: GrantedPCs<br>Check the Allow radio button<br>Days: Check Everyday<br>Time: Check 24 Hours<br>Leave Website Blocking by URL Address empty<br>Leave Website Blocking by Keyword empty<br>Leave Blocking by Services to all Disabled<br>Click the "Edit List of PCs"<br>MAC Address:  <I>Specify each of the MAC address of the PCs you  want to have internet access</I><br>Leave everything else untouched<br>Click the "Apply" button, then the "Close" one (this should bring you back to main page)<br>Click the "Apply" button<br><br><B><U>Filter 15</U></B><br>Internet Access Policy: 10<br>Enter Policy Name: TheDeniedPCs<br>Check the Deny radio button<br>Days: Check Everyday<br>Time: Check 24 Hours<br>Notice you lose access to Website Blocking by URL Address; it's normal<br>Notice you lose access to Website Blocking by Keyword; it's normal<br>Leave Blocking by Services to all Disabled<br>Don't bother about the "Edit List" button (don't even click on it)<br>Click the "Apply" button, then the "Continue" one.<br><br>With this setup, all MAC addresses you have specified in filter 1 are granted access.  Everything else are denied.  Once your son is relieved from his sentence, then you can simply add his MAC address back to the list in filter 1.  If he gets grounded again, simply remove his MAC from the list.  I haven't tested this particular setup as such, however, with my understanding of the filters, this should work perfectly for you.  Please try it out and let us all know.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10211455</guid>
<pubDate>Tue, 11 May 2004 11:21:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10211364</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : dpmox, I just try to block access to single comp. by IP and by MAC. I'm using v.1.45.7 and it's working perfectly. If you want to block PC by IP, it is best to define static IP to that comp. I don't know how much an expert your son is, coz he can change the IP and he has the access again. I advise you to block by MAC address. (It can be changed too, but....). <br>The time must be synchronised for filters to work. Check logs.<br><br>EDIT: <br>Re Flogator's answer: I'm using only Filter 1 (adapted from Flogator)<br> <br>Internet Access Policy: 1<br>Enter Policy Name: TheDeniedPCs<br>Check the Deny radio button<br>Days: Check Everyday<br>Time: Check 24 Hours<br>Notice you lose access to Website Blocking by URL Address; it's normal<br>Notice you lose access to Website Blocking by Keyword; it's normal<br>Leave Blocking by Services to all Disabled<br>Click the "Edit List of PCs"<br>MAC Address: Specify each of the MAC address of the PCs you want to deny internet access<br>Leave everything else untouched<br>Click the "Apply" button, then the "Close" one (this should bring you back to main page)<br>Click the "Apply" button, then the "Continue" one.<br><br>Just tested it and it's working. But Flogator's solution is immune to changing IP or MAC. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10211364</guid>
<pubDate>Tue, 11 May 2004 11:09:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10210923</link>
<description><![CDATA[<A HREF="/useremail/u/556416"><b>damox</b></A> : Actually, the new Firmware is working fairly well for me, except for the fact that as others have noted, running Tracert crashes the unit (though I can ping just fine without incident). Not having Trace Route is no big deal for me, because I can only get the first and last two hops. All the other hops time out. This has been going on for 8 months or so.  <br><br>The other problem I noticed is that Restricting Access to the Internet for a single computer, doesn't seem to work. I attempted to block Internet Access for my son who has been grounded, but for some reason, it doesn't seem to be working. Having said that, however, I was never able to get it to work with the previous firmware version either, unless I blocked access for everyone! Another glitch, related to restricting access is that the "Blocked Services" interface if grayed out! <br><SMALL>--<br>DAMOX <B><A HREF="http://www.dslreports.com/forum/remark,1564398;root=disco;mode=flat#1564398"> Proud to be a member of Team Discovery</B></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10210923</guid>
<pubDate>Tue, 11 May 2004 10:10:38 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10210633</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : jefe, that's a good thing.  I have contacted my Linksys contact already about all of the known 1.50.18 issues.  However, more people complaining, the better chance it'll get fixed.<br><br>As for the ICMP problem, if your router does not crash then the likelihood is that the ICMP Time Exceeded messages are not coming back to you.  The fact that you say "<I>It just doesn't work</I>" is a good indication of that.  As I stated before, the problem is not just with trace route.  You can repeat it with a simple ping command:<br><br><U>Command that works</U>:<br>[Windows/Unix/Linux Users]: ping yahoo.com<br><br><U>Commands that crash the router</U>:<br>[Windows Users]: ping -i 2 yahoo.com<br>[Unix/Linux Users]: ping -t 2 yahoo.com<br><br>If the command I said works doesn't work for you, no point in trying the other one.  However, if it does, you'll soon see the other command will crash the router.  If it isn't, it means the routers along the path do not implement a standard ICMP stack (which is possible).  If that is the case, increment the number 2 until you see it crash ;).  Note that which ever node you choose, it must be on the WAN side of the router otherwise, you will not hit the bug.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10210633</guid>
<pubDate>Tue, 11 May 2004 09:31:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10210532</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> : A little follow up:<br><br>I dropped Linksys tech a note telling them about the logging issues, i.e. with and without Firewall Protection enabled.  To my surprise, I got a prompt reply asking me to re-flash 1.50.18 and report back if that made any difference. I did, and it didn't.<br><br>The tech who replied said they would consider that a problem with the firmware.<br><br>In my reply to his reply, I also reported the ICMP tracert problem.  FWIW.<br><br>By the way, ICMP tracert does not crash or reboot my router. It just doesn't work.  All hops time out but the router continues to function normally otherwise.<br><br>--jeff]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10210532</guid>
<pubDate>Tue, 11 May 2004 09:14:51 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10210352</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : V1.45.7 is not hacked code.  In fact the only "hacked code" BEFSX41 firmware contained only different time server IP, no software was changed other than that...<br><br>V1.45.7 is Beta code from Linksys, and (in nmy humble opinion, cause I can't get V1.50.18 to work at all....)<br><br>The best (V1.45.7)<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10210352</guid>
<pubDate>Tue, 11 May 2004 08:38:15 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10210149</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Is version 1.45.7 safe on this forum, I means not a version with hacker code as stipulated in the warning of this section. They said they will not be longer available??]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10210149</guid>
<pubDate>Tue, 11 May 2004 07:49:18 EDT</pubDate>
</item>

<item>
<title>Re: ..</title>
<link>http://www.dslreports.com/forum/remark,10209694</link>
<description><![CDATA[<A HREF="/useremail/u/820408"><b>gdcastro</b></A> : thanks, ill try that.  i didnt restore the factory settings but i was able access it initially, it was when i tried to make changes when the router rebooted and failed on me.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10209694</guid>
<pubDate>Tue, 11 May 2004 03:25:51 EDT</pubDate>
</item>

<item>
<title>..</title>
<link>http://www.dslreports.com/forum/remark,10209523</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Try input static IP: 192.168.1.2<br>Subnet mask        : 255.255.255.0<br>Default gateway    : 192.168.1.1<br>REBOOT!!!!<br> <br>Ping the router, if you get response, try TFTP new firmware, I suggest v. 1.45.7  (1.50.9 will give you only a headache). Before you make any changes do the "Restore Factory Default" (under password tab). Hope this will do....<br><br>Read the &raquo;<A HREF="/faq/linksys">Linksys FAQ</A> &raquo;<A HREF="/faq/2289">Help!  My router is dead after I upgraded firmware!</A> and &raquo;<A HREF="/faq/linksys">Linksys FAQ</A> &raquo;<A HREF="/faq/3390">A Suggestion for successful firmware update</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10209523</guid>
<pubDate>Tue, 11 May 2004 02:17:46 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10209310</link>
<description><![CDATA[<A HREF="/useremail/u/820408"><b>gdcastro</b></A> : I upgrade my SX41 firmware to 1.50.9 from 1.44.something.  TFTP was successful, then I logged on to the webbased config, made the neccessary changes to WAN and DNS, then I saved the changes.  The router rebooted and after it went back up, I cannot access the  webbased settings, NOR can I acquire an IP.  I get  169.xxx.xxx.xx.x.<br><br>I tried several things already, hit the reset switch for 30 secs, rebooted the router, rebooted the router while holding down the reset switch...NOTHING.<br><br>i even inputted a static IP 192.168.1.100 / 192.168.1.20, NOTHING.<br><br>I dont know what to do at this point, someone please help me.<br><br>Thank you very much.  ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10209310</guid>
<pubDate>Tue, 11 May 2004 01:30:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10208344</link>
<description><![CDATA[<A HREF="/useremail/u/292724"><b>BillRoland</b></A> : About UDP ping.  Indeed it is a nice work around, but using Ping Plotter 2.5 with UDP based trace route enabled is not exactly perfect.  I would estimate 90% of destinations I am tracing to appear offline or as black holes, while they respond perfectly fine to ICMP trace routes.  That's not very helpful in trying to diagnose a problem, especially since the one I was trying to find was occurring between the 2nd to last and last hop, so it looked fine to me on UDP trace routes, but with an ICMP trace, I was able to immediately figure out why I kept getting disconnected.  Its not a perfect world.  I do like the UDP traceroute better though, its nice to see all the routers in the path actually respond  ;) <br><SMALL>--<br>"Don't steal.  The government hates competition."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10208344</guid>
<pubDate>Mon, 10 May 2004 23:15:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10205093</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Actually, the MTU problem is slightly different.  Perhaps related to the "<I>rotten ICMP</I>" implementation but not likely.  The MTU problem is more fundamental than that.  When MTU is enabled, the router basically discards all WAN packets that has the "Don't Fragment" bit set in the IP flags.  That's all ;).  See these posts for details about the MTU problem:<br><br>&raquo;<A HREF="/forum/remark,10175320">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A><br>&raquo;<A HREF="/forum/remark,10192373">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A><br><br>[EDIT]:  For users that need to modify MTU in general, please tweak it on your PC instead as a workaround.  See this post for details:<br><br>&raquo;<A HREF="/forum/remark,10192468">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10205093</guid>
<pubDate>Mon, 10 May 2004 17:21:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10205009</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> What I decided to do was to use TimInHackMod's NTP server updater to change the three NTP servers to point to 192.168.1.100 with firmware 1.45.3.<HR></BLOCKQUOTE>You're right! I've tested the hacks and understood them partially by source code. Because I was not able to modify it for 1.45.7 where the NTP servers are stored with their host names and not IP addresses I decided to leave the firmware untouched and use the dirty workaround.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10205009</guid>
<pubDate>Mon, 10 May 2004 17:12:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10204864</link>
<description><![CDATA[<A HREF="/useremail/u/972855"><b>ElJay</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> For me it worked the following way:<br><br>Add a static route for 'time.nist.gov'<br>Destination LAN IP: 192.43.244.18<br>Subnet Mask: 255.255.255.254 (it is not possible to set a 255 for the fourth octet what would be neccessary for a real host route)<br>Default Gateway: 'router-ip-on-lan' (e.g. 192.168.1.1)<br>Hop Count: 0<br>Interface: LAN<br><br>Then I gave one (Windows) host a second IP address of 192.43.244.18 and installed the Program Jana2 Proxy Server &raquo;<A HREF="http://www.janaserver.de/" >www.janaserver.de/</A> . <HR></BLOCKQUOTE><br><br>What I decided to do was to use TimInHackMod's NTP server updater to change the three NTP servers to point to 192.168.1.100 with firmware 1.45.3. The router is apparently intelligent enough to know that 192.168.1.100 is on the LAN side and sends all NTP requests (3 per hour :() to this machine on my network. A Windows XP Pro machine is at 192.168.1.100 and the process named "svchost.exe" apparently services these NTP requests by default. (By the way, my BEFSX41 is in "gateway" mode.)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10204864</guid>
<pubDate>Mon, 10 May 2004 16:57:43 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10204601</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> The theory of tracing routes is interesting, but if it's been stated, I missed why firmware 1.50.18 isn't passing a ICMP tracert, while UDP works.<HR></BLOCKQUOTE><br>Because of a rotten ICMP implementation!? I guess the MTU problems are caused by that too.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10204601</guid>
<pubDate>Mon, 10 May 2004 16:31:54 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10204590</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> : I see that now Flogator.  Thanks for the repeat.<br><br>Let's hope Linksys will fix the new broken feature they've created soon, without breaking any others.:huh:]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10204590</guid>
<pubDate>Mon, 10 May 2004 16:30:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10204384</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : jefe, indeed, please take the time in reading through my ICMP-based trace route problem posts.  <br><br>My first observation at &raquo;<A HREF="/forum/remark,10174949">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A><br>My analysis and theory at &raquo;<A HREF="/forum/remark,10200236">ICMP-Based Trace Route UPDATE</A><br>Some additional info at &raquo;<A HREF="/forum/remark,10202425">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</A><br>More technical info at &raquo;<A HREF="/forum/remark,10203205">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</A><br><br>In the second provided link, I have suggested that either all or part of the ICMP stack has been rewritten in 1.50.18.  That is why ICMP-based trace route works in 1.45.7 and earlier but not in 1.50.18.  Hope this information helps.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10204384</guid>
<pubDate>Mon, 10 May 2004 16:09:36 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10204191</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> : The theory of tracing routes is interesting, but if it's been stated, I missed why firmware 1.50.18 isn't passing a ICMP tracert, while UDP works.<br><br>--jeff]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10204191</guid>
<pubDate>Mon, 10 May 2004 15:48:49 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10203498</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Forgot to mention. When the packet reaches the destination something funny occurs. In the ICMP-based trace route, the destination will reply with an ICMP Echo Reply. In the case of UDP-based trace route, the destination will reply with an ICMP Host Unreachable with the sub-code of Port Unreachable. Either way, it will always be an ICMP message coming back. There is only one caveat with UDP-based trace route. If the UDP port being used during the trace route is actually in serviced at the far-end, then no ICMP messages will be sent back. That is why a good UDP-based trace route implementation will repeat with more UDP messages using different UDP port .<HR></BLOCKQUOTE><br>Thank you for the explanation! You're describing exactly the problem I saw. The solution is smart and simple.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10203498</guid>
<pubDate>Mon, 10 May 2004 14:24:15 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10203205</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : My pleasure to answer the latest ICMP question :).  A properly implemented ICMP stack does not worry about the original message format.  In other words, whether the original message is an ICMP Echo Request, a UDP message, or any other type of messages as it matters, a device that sees the TTL of 1 or 0 must stop the routing of that packet and originate an ICMP Time Exceeded back to the originator period.<br><br>So to answer the question in its simplest way, ICMP-based trace route uses ICMP Echo Request with an incrementing TTL value where as UDP-based trace route uses a regular UDP message with also an incrementing TTL value.  Therefore, when the router sees either this ICMP Echo Request or UDP message with a TTL of 1, it will respond with an ICMP Time Exceeded message.<br><br>The only real difference between the two mechanisms is the content of the ICMP Time Exceeded field that contains the first few bytes of the original packet that caused the Time Exceeded message to be generated.  In the ICMP-based trace route, it will be an ICMP Echo Request where as in the UDP-based trace route, it will be the first few bytes of the original UDP message (in fact the while IP and UDP header shall be present).<br><br>[EDIT]:  Forgot to mention.  When the packet reaches the destination something funny occurs.  In the ICMP-based trace route, the destination will reply with an ICMP Echo Reply.  In the case of UDP-based trace route, the destination will reply with an ICMP Host Unreachable with the sub-code of Port Unreachable.  Either way, it will always be an ICMP message coming back.  There is only one caveat with UDP-based trace route.  If the UDP port being used during the trace route is actually in serviced at the far-end, then no ICMP messages will be sent back.  That is why a good UDP-based trace route implementation will repeat with more UDP messages using different UDP port ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10203205</guid>
<pubDate>Mon, 10 May 2004 13:44:01 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10202982</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Let me state it this way.<br>Traceroute uses the TTL option in the IP packet to elicit an ICMP Time Exceeded message from each router. Each router decrements the TTL field. So the decrementation of the TTL field works LIKE a counter.<HR></BLOCKQUOTE><br>Yes - 'to elicit an Time exceeded message' is a very good description! As Flugator and I pointed out TTL belongs to the features of IP. For proper functionality of IP every host should have a working ICMP implementation. That's in my opinion the Problem of the routers OS - a buggy ICMP implementation. The problems with MTU and fragmentation could also deal with this.<br><br>I have another question:<br>Using ICMP based traceroute leads to TTL exceeded messages from every hop except the destination host which answeres with a simple ICMP echo reply. What kind of answer will you get when using UDP based traceroute?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10202982</guid>
<pubDate>Mon, 10 May 2004 13:14:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10202758</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Illjuschin, can you give us, not so learned users on routing, some example or screen picture of your method for NTP servers.<HR></BLOCKQUOTE><br>For me it worked the following way:<br><br>Add a static route for 'time.nist.gov'<br>Destination LAN IP: 192.43.244.18<br>Subnet Mask: 255.255.255.254 (it is not possible to set a 255 for the fourth octet what would be neccessary for a real host route)<br>Default Gateway: 'router-ip-on-lan' (e.g. 192.168.1.1)<br>Hop Count: 0<br>Interface: LAN<br><br>Then I gave one (Windows) host a second IP address of 192.43.244.18 and installed the Program Jana2 Proxy Server  <A HREF="http://www.janaserver.de/">http://www.janaserver.de/</A> . Jana allows to define an 'extra gateway' that causes the host to listen on a certain port (123) and redirects the requests. Jana asks a NTP server of my choice and sends the answer back to requesting host (the router).<br><br>I must add that I used the Router in 'router mode' not 'gateway mode' but I would bet it will also work.<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Is it possible to restrict access to certain IP (by number) also using static routes? Thanks.<br><HR></BLOCKQUOTE><br>Why not? Try it - for me it's impossible at the moment.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10202758</guid>
<pubDate>Mon, 10 May 2004 12:47:55 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10202425</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Now reading through WayuU's posts.  I've got to agree with Illjuschin on this one.  The TTL field is always decrementing at every hop whether it is ICMP or anything else.  That's a layer 3 function that belongs to IP independently of which layer 4 protocol it is running.<br><br>On the other hand, let's not close our mind about trace route.    Sending ICMP echo request (ping) command is not the only way to determine the routes.  Nothing prevent you from sending any packet type you like.  In fact, all Linux-based OS are using UDP in their trace route implementation (with an option to switch to ICMP if needs be).  It is just unfortunate that the tracert utility in Windows-based OS is only using ICMP echo request to do this.  That is why I am keep saying ICMP-based trace route causes the router to crash but UDP-based trace route is working just fine.  Please take a moment in reading through the following two posts I have already written in this thread:<br><br>&raquo;<A HREF="/forum/remark,10174949">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</A><br>&raquo;<A HREF="/forum/remark,10200236">ICMP-Based Trace Route UPDATE</A><br><br>Just to add more info to the second post.  The problem is not with trace route as such.  The problem is when the router receives an ICMP Time Exceeded message but encapsulating an ICMP Echo Request in the first few bytes of data instead of a UDP message.  Just to prove my theory, do the following command and you'll see the route crash ;).<br><br>[Windows Users]:  ping -i 2 yahoo.com<br>[Unix/Linux Users]:  ping -t 2 yahoo.com]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10202425</guid>
<pubDate>Mon, 10 May 2004 12:06:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10202338</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> :  <BLOCKQUOTE><SMALL>said by Illjuschin:</SMALL><HR>Traceroute (tracert) sends sequences of ICMP echo request (type 8) beginning with a TTL of 1.<br><HR></BLOCKQUOTE><br><br>Well, I don't understand your explanation completely. <br>Let me state it this way. <br>Traceroute uses the TTL option in the IP packet to elicit an ICMP Time Exceeded message from each router. Each router decrements the TTL field. So the decrementation of the TTL field works LIKE a counter.<br><br>But you are right about all IP packets getting the TTL field decremented by one for them not to circulate forever.<br><SMALL>--<br>.·´¯`·-·´¯`WayuU´¯`·-·´¯`·. [img]&raquo;<A HREF="http://www.danasoft.com/sig/WayuU.jpg[/img]" >www.danasoft.com/sig/WayuU.jpg[/img]</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10202338</guid>
<pubDate>Mon, 10 May 2004 11:56:37 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10202275</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Illjuschin, can you give us, not so learned users on routing, some example or screen picture of your method for NTP servers.<br>Is it possible to restrict access to certain IP (by number) also using static routes? Thanks.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10202275</guid>
<pubDate>Mon, 10 May 2004 11:48:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10201935</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Hello<br><br> <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Only difference is that the TTL field in a traceroute is decremented by one for each router it passes, while the TTL field is not touched when pinging.<HR></BLOCKQUOTE><br><br>I don't agree with this statement:<br><br>TTL will alway be decremented by one at each hop an IP packet passes by to prevent packets from circulating forever. That's a fundamental feature of IP.<br><br>Traceroute (tracert) sends sequences of ICMP echo request (type 8) beginning with a TTL of 1. It increments this counter for every sequence. Because of the fact that decrementing the TTL leads to zero for the first, second, ... hop and finally for the destination host the answer to the echo request ist an ICMP message type 11 (Time-to-live exceeded). That's the trick!<br><br>If this does not work correctly or even harder leads to system crash/reboot I think the programmers of the TCP/IP stack have done a sloppy work.<br><br>I'm going to set up a BEFSX41 this week with german DSL for a simple home office environment. What I read so far in this and the other threads dealing with firmware problems leads me to a conservative attitude. I think we will upgrade to 1.45.7 (currently 1.45.3) and live with the known problems of that version.<br><br>BTW: I have another dirty trick to use the time server of my choice. I define three static host routes that tell the router to send requests to the three NTP servers to the local LAN. Giving one host a second IP address of one of the servers gives me the ability to define a port redirection (or extra gateway) and ask a server nearby.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201935</guid>
<pubDate>Mon, 10 May 2004 10:53:08 EDT</pubDate>
</item>

<item>
<title>Re: Web Items Taking Forever to Load UPDATE</title>
<link>http://www.dslreports.com/forum/remark,10201635</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : Great, lets hope they use it to our advantage.  FWIW, I am still using the latest firmware but am not challenging it much.  I have no need for any of the advanced features, i.e. filters, etc.  And since I am on cable it seems I might have escaped any MTU issues "so far"!  It seems to be working well for me so far.  The only issues I see myself now is the slow page loading and of course the TraceRoute problem.  You do bring up a good point with that one though in that how easily this router could be made useless by a well crafted DOS attack taking advantage of that one weakness.  Makes me wonder how close any other versions of the firmware could be exploited this way.  If this wasn't there in the 1.50.9 firmware then why is it there in the 1.50.18?  Surely they didn't completely rewrite it from scratch!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201635</guid>
<pubDate>Mon, 10 May 2004 10:03:15 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10201629</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : If anyone is on DSL with V1.50.18 and you have successfully been able to surf.... Please Email me pictures of your settings... I have been totally unable to surf on SBC/Ameritech DSL no matter what I do...<br>Thanks<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201629</guid>
<pubDate>Mon, 10 May 2004 10:02:04 EDT</pubDate>
</item>

<item>
<title>Re: Web Items Taking Forever to Load UPDATE</title>
<link>http://www.dslreports.com/forum/remark,10201538</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Don't you worry jbob, indeed this information is going to make its way straight to Linksys ;).  I have already provided them with a summary report.  Now, they gonna get the full report later today ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201538</guid>
<pubDate>Mon, 10 May 2004 09:45:05 EDT</pubDate>
</item>

<item>
<title>Re: Web Items Taking Forever to Load UPDATE</title>
<link>http://www.dslreports.com/forum/remark,10201447</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : Flogator<br><br>Are you relaying this info to Linksys as well?  You certainly deserve more than a pat on the back for this stuff.  Perhaps Linksys/Cisco should pay you.:)<br>I wish I had your technical knowledge, maybe one day!!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201447</guid>
<pubDate>Mon, 10 May 2004 09:28:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10201367</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> :  <BLOCKQUOTE><SMALL>said by  Jan Janowski <A HREF="/useremail/u/166306"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Also today, I found I could not find the selection for which IP I wanted to broadcast the logs to:  255=All or a specific IP...  Did you find that?  Thanks!!<br><HR></BLOCKQUOTE><br><br>Yes. <br>Administration - Log<br><br> <BLOCKQUOTE><SMALL>said by  Jan Janowski <A HREF="/useremail/u/166306"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>EDIT!!  One last question... Are you on Cable or DSL???<br><HR></BLOCKQUOTE><br><br>Is there a user named "Edit" or was that question to me?<br>Anyways, I'm on T1, fiberoptic.<br><SMALL>--<br>.·´¯`·-·´¯`WayuU´¯`·-·´¯`·. [img]&raquo;<A HREF="http://www.danasoft.com/sig/WayuU.jpg[/img]" >www.danasoft.com/sig/WayuU.jpg[/img]</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201367</guid>
<pubDate>Mon, 10 May 2004 09:15:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10201336</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> :  <BLOCKQUOTE><SMALL>said by  Jan Janowski <A HREF="/useremail/u/166306"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>You mentioned you came across screens that didn't refresh properly.... White Screens?   How did you get them to refresh, Refresh?  Page Back/Page Fwd?  Wear a plaid shirt?<br>(Hey! If that is what it takes!!)<br><HR></BLOCKQUOTE><br><br>I've had issues with the pages not showing up on earlier versions too. But now it is worse. <br>All I do to get them to show up is to hit the refresh button (without CTRL). Sometimes now I have to hit it up to, but not more than, 3 times to get the page to show up.<br><SMALL>--<br>.·´¯`·-·´¯`WayuU´¯`·-·´¯`·. [img]&raquo;<A HREF="http://www.danasoft.com/sig/WayuU.jpg[/img]" >www.danasoft.com/sig/WayuU.jpg[/img]</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201336</guid>
<pubDate>Mon, 10 May 2004 09:10:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10201305</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> :  <BLOCKQUOTE><SMALL>said by  Jan Janowski <A HREF="/useremail/u/166306"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR> <BLOCKQUOTE><SMALL>said by  WayuU <A HREF="/useremail/u/963087"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>I forgot a question:<br><br>Is the traceroute problem a confirmed bug or some deliberate change from Linksys?<br> <HR></BLOCKQUOTE><br><br>Why would someone intentionally code it to crash?<br>I found Pingplotter would immediately crash V1.50.18.<br> <HR></BLOCKQUOTE><br><br>I don't know if it would have been coded to crash or if the crashing is a bug. But not being able to use ICMP packet traceroute might not be a bug. Why then would ping work just fine? both work with same ICMP echo request packets. At least under Windows. Only difference is that the TTL field in a traceroute is decremented by one for each router it passes, while the TTL field is not touched when pinging. <br>Still, if somehow for security reasons, then the UDP tracerouting is more of an issue. With UDP packets you can bypass ACLs.<br><SMALL>--<br>.·´¯`·-·´¯`WayuU´¯`·-·´¯`·. [img]&raquo;<A HREF="http://www.danasoft.com/sig/WayuU.jpg[/img]" >www.danasoft.com/sig/WayuU.jpg[/img]</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10201305</guid>
<pubDate>Mon, 10 May 2004 09:06:19 EDT</pubDate>
</item>

<item>
<title>Web Items Taking Forever to Load UPDATE</title>
<link>http://www.dslreports.com/forum/remark,10200354</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Most of you have noticed that while accessing the router's configuration web page, some of the items are taking forever to load.  Well, I did spent some time debugging this one as well and I think I found the root cause :).<br><br>Old web browsers were loading web pages in a sequential order.  That means that the browser loads the HTML file, then first item, then second items and so on.  This makes the web browser implementation quite simple and adequate for dial-up.  However, over a broad band connections, that is not very efficient.<br><br>Most of modern web browsers do load web page objects in parallel.  Of course, such browser is still stuck in loading the HTML file first as it is the one containing the pointers to the remaining objects (i.e. images).  But once the main HTML file is loaded, most of modern web browsers establish multiple TCP connections to load all of the remaining web page objects in parallel.  This is why web pages come up very fast.<br><br>In Microsoft Internet Explorer, you can even tweak the number of concurrent TCP connections such that web pages are showing up even faster.  Well, that seems to be exactly what the problem is here.  When trying to browse the router's configuration web page using a very old version of internet explorer, I had no problem accessing the pages for the simple reason it is accessing the web page objects sequentially.  On the other end, I have tweaked my Internet Explorer to go as high as 20 concurrent TCP connections to load web page objects.  Most of you have noticed that the new GUI is very nice.  The problem is there is so much web page objects to load that their web server SHOULD HAVE BEEN OPTIMIZED FOR THAT.<br><br>After doing some packet sniffing, I have discovered that the web server in firmware 1.50.18 has a back log of about one or two concurrent TCP connections.  I have noticed that if the web browser attempts to establish too many TCP connections then the BEFSX41 drops some SYN packets :(.  It takes 3 seconds for the PC to timeout and resend the TCP SYN packet.  If you multiply 3 seconds by half or third of the amount of web page objects, then you now understand why it takes forever to completely load them all :(.<br><br>This simply tells me that either Linksys simplify their GUI or that they optimize their web server.  Unless they do one of the above, their router's configuration web page access will remain shitty (unless of course you are using a very old web browser - but then again, the rest of your internet access will by shitty).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10200354</guid>
<pubDate>Mon, 10 May 2004 02:06:30 EDT</pubDate>
</item>

<item>
<title>ICMP-Based Trace Route UPDATE</title>
<link>http://www.dslreports.com/forum/remark,10200236</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Did some more debugging about the ICMP-based trace route problem.  As you all know, in firmware 1.50.18, ICMP-based trace route is crashing the router :(.  At the interim time, we must use UDP-based trace route to workaround this problem.<br><br>One of the things I have discovered is that the only difference between the two mechanisms is what the ICMP Time Exceeded message looks like on its way back :).  As you may know, at the end of the ICMP message, there is the first few bytes of the original packet that caused the ICMP message to be generated.  Well, guess what?  In the ICMP-based mechanism the first few bytes of original packet represent an ICMP packet (the echo request or ping if you like).  In the UDP-based mechanism, the first few bytes of original packet represent a UDP packet.  This can only leads me to one conclusion:  The 1.50.18 firmware attempts to decode the ICMP Time Exceeded first few bytes of original packet as a UDP/TCP packet ALL THE TIME and when trying to resolve source and destination port got totally out of wack in its table because it actually took an ICMP payload instead.  Then after accessing a couple of bad memory addresses, the router crashes.<br><br>This is in my mind a major bug.  Not only does it reboot the router using tracert but with such a bug, it could very well do the same behavior under different circumstances.  This means that the ICMP stack has been rewritten from 1.45.7 to 1.50.18 and not very well tested :(.  This also means that firmware 1.50.18 contains a DoS (Denial of Server) vulnerability.  This means that a remote attacker could deliberately reboot your router by simply generating an ICMP Time Exceeded message :(.  I leave the realm of malicious actions taking advantage of this to your own imagination :).<br><br>I will keep 1.50.18 for few more days to soak it further but by the end of the week, I will probably roll back to 1.45.7.  In any case, I will keep you guys updated.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10200236</guid>
<pubDate>Mon, 10 May 2004 01:37:38 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10200149</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Ok, finally get around to do some time filters tests.  As I said before, I am not a filter user myself but was able to play a bit with those famous filters.  I did not push too hard so I did not experienced the random reboot when using time filters.  My goal was rather to get some basic feel as to whether these work or not.<br><br>First observations were the new limitations from 1.45.7.  Indeed, in 1.45.7 we had access to 15 filters where as here, with 1.50.18, we only have 10 :(.  Another limitation resides in the list of PC.  When you click on "Edit List", a dialog appears.  In 1.45.7, such dialog had a nice option which was the "All PCs" check box.  Well, that one has disappeared in 1.50.18 :(.  No big deal you may say but it was pretty handy in my filter 15 in 1.45.7.<br><br>Next, I went in and set three filters to make sure all of the three PCs I was using were covered up somehow by at least one filter ;).  First filter was using Jan's famous doubleclick example.  Tried both <B>ebay.doubleclick.net</B> in block by URL and (in another filter of course) <B>doubleclick</B> in block by Keyword.  Both filters work properly.  Logs are still fuzy if SPI firewall is enabled but more clear is SPI firewall is disabled.  That is the same behavior as with 1.45.7.  The third filter was the deny all filter (as filter 10 - the last one).  My third PC was denied all internet access so I concluded that the "<I>walking down the filter list</I>" worked properly (this third PC was not included in any of the previous two filters thereof, used the last filter as a default match).  The only thing annoying is that I got the following line in the logs:<br><br><B>List of PCs matched && Time_filtr_range matched,dropping pkt</B><br><br>Not very useful because it does not even say which filter number was hit.  I guess that's what Jan was complaining about since the very first beginning.<br><br>Additionally, I tried playing with the day of week and time of day just to see if the router is actually looking at those fields.  It looks like it is.  When changing the day of week on my first filter, I was able to deny access to my first PC.  When changing the time of day on my second filter, I was able to deny access to my second PC.  No matter the reason why the time condition failed, I was always getting the same log entry:<br><br><B>List of PCs matched && Time_filtr_range matched,dropping pkt</B><br><br>Hmm, how the hell do I know which filter got hit and the reason (day of week or time of day)?  I'm sure though that this behavior is same as 1.45.7 so I guess I should not be complaining.  Jan is right, the logs should be more explicit.  At the very least, the filter number should be part of the log entry.  Would be nice to have a more granular time match reason but I guess that one is debatable.<br><br>Finally but not least, by a pure fluke I got hit by the famous bug called "Log date problem".  This is the bug where the day of week is wrong on every day transition (from 11h59 to 00h00) for about one to two hours.  The bug also causes more problems once every three months again on the day/month transition for which the whole date/time/day is wrong for about three hours.  I guess this bug is not fixed then isn't.  How did I find out?  Well, when I set the day of week in my first filter, I check the Monday box (and it was Monday about 00h40).  But the router, after synchronizing its time, decided it was Sunday still so I got all confused in the filter hit :(.  Nevertheless, it was fine later.<br><br>Bottom line, the filters seems to be operational.  However, firmware 1.50.18 brought some more limitations as well as carrying the same lack of details in the logs as there is in 1.45.7.  I am hoping this helps filters users to get a better feelings about the status of time filters in 1.50.18.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10200149</guid>
<pubDate>Mon, 10 May 2004 01:19:07 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10199300</link>
<description><![CDATA[<A HREF="/useremail/u/996454"><b>humphreysa</b></A> : from &raquo;<A HREF="http://www.asiacomputerweekly.com/acw_ViewArt.cfm?Magid=1&Artid=23706&Catid=2&subcat=19" >www.asiacomputerweekly.com/acw_V&middot;&middot;&middot;ubcat=19</A><br><br><BLOCKQUOTE>There&#146;s good and bad. The bad thing is that we slow down a little, but the good thing is we get a lot more input. We now have a lot more smart people who go &#147;oops, we can&#146;t do this&#148;, or &#147;oh, we haven&#146;t thought about that&#148;. We make less mistakes that way.</BLOCKQUOTE><br><br>If only they made fewer mistakes in making the firmware updates. They seem to have be making more since the Cisco takeover, not less. :-(<br><br>Where can I find a small company that makes consumer priced router that's hungry for my business? I'd happily move to them if it meant that I can have a router that works as advertised!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10199300</guid>
<pubDate>Sun, 09 May 2004 23:07:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10199223</link>
<description><![CDATA[<A HREF="/useremail/u/1004574"><b>ApolloZip</b></A> : The only one I've had a chance to test with so far is the keyword filters.  I had the same issue with 1.45.7.  <br><br>Does LinkSys have a test protocol and a Q/A environment or are we it? ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10199223</guid>
<pubDate>Sun, 09 May 2004 22:58:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10199059</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  ApolloZip <A HREF="/useremail/u/1004574"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR><br> <br>Java based speed tests like Speakeasy's Speed Test causes a crash/re-boot with filters activated.  <br> <br> <HR></BLOCKQUOTE><br><br>were those time filters, url filters, or keywords?  By this I mean did you use all or just any one of them and get a Java based speetest/crash.... ?<br>Sorry to hear about this... <br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10199059</guid>
<pubDate>Sun, 09 May 2004 22:40:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10198975</link>
<description><![CDATA[<A HREF="/useremail/u/1004574"><b>ApolloZip</b></A> : I upgraded from 1.45.7 to 1.50.18 on 05-07 in a cable environment. I&#146;m still testing but here&#146;s a quick update. <br> <br>The only issues I have encountered so far are:<br> <br>Tracert causes a crash/re-boot.  <br> <br>Java based speed tests like Speakeasy's Speed Test causes a crash/re-boot with filters activated.  <br> <br>If you are running Web Washer or something equivalent to it that will cause the problem you are having with the interface screens not loading correctly.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10198975</guid>
<pubDate>Sun, 09 May 2004 22:29:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10198955</link>
<description><![CDATA[<A HREF="/useremail/u/993621"><b>Tachyon</b></A> : It's interesting reading all the crap coming out of the 1.50.18 fw release and after reading the Netgear and a few other forums. I've come away with some observations.<br>1)	Linksys is NOT the only company who seems to be doing business this way. Possibly the "original" firmware code was written by an outside firm which would explain why the internal staff seems incapable of putting out functioning code. OR they lost the real "talented" coders due to adjustments to the "bottom line".<br>2)	Linksys is not interested in nor do they read these forums. Perhaps occasionally for quick sadistic laughs. But certainly not to make corrections to their products. (they should if they were smart) But after all, end-users are stupid and Linksys programmers are infallible. :huh:<br>3)	I vote that both Flogator and Jan Janowski should both head-up the firmware development and beta test divisions at Cisco/Linksys. Maybe then we can get firmware upgrades/updates and not product de-activations. I'll call Linksys Monday guys!!  :D<br>4)	As for me, I'm sticking with 1.45.7! <br><br>On a side note, has anyone tried to climb the Linksys/Cisco hierarchy and get to a "get it done" person with a greatly distilled version of our findings in these forums. Seems that with the combined talent represented here Linksys coders could quickly examine the "common" and "prolific" problems, address them and release drastically improved code in short order. Use us as field beta testers. If it meant getting better code I'd jump at the chance. As it stands now why go to the trouble if nothing is going to be done about it. Could you imagine a v1.50.8 3 weeks from now with all the corrections that we've mentioned here. I might even upgrade.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10198955</guid>
<pubDate>Sun, 09 May 2004 22:26:14 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10198385</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : Thanks.. That must have been one of the area's with white screens that, in order to get any screen at all, I hit multiple page backwards/forwards... It seemed the further into the menu system, the more problamatic the white screens were... Thanks for clearing that up...<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10198385</guid>
<pubDate>Sun, 09 May 2004 21:16:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10198295</link>
<description><![CDATA[<A HREF="/useremail/u/602248"><b>RdKryton</b></A> : "Also today, I found I could not find the selection for which IP I wanted to broadcast the logs to: 255=All or a specific IP... Did you find that? Thanks!!"<br><br>Is this what you are looking for?<br><SMALL>--<br>Happiness is a belt fed weapon...</SMALL><div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10198295?c=591196&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="72366 bytes" WIDTH=600 HEIGHT=436 SRC="/r0/download/591196.thumb600~d72d3c1a479512f01f013150fd0ecf1d/Log.JPG/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10198295</guid>
<pubDate>Sun, 09 May 2004 21:06:18 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10197828</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  WayuU <A HREF="/useremail/u/963087"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>I forgot a question:<br><br>Is the traceroute problem a confirmed bug or some deliberate change from Linksys?<br> <HR></BLOCKQUOTE><br><br>Why would someone intentionally code it to crash?<br>I found Pingplotter would immediately crash V1.50.18.<br><br>You mentioned you came across screens that didn't refresh properly.... White Screens?   How did you get them to refresh, Refresh?  Page Back/Page Fwd?  Wear a plaid shirt?<br>(Hey! If that is what it takes!!)<br><br>Also today, I found I could not find the selection for which IP I wanted to broadcast the logs to:  255=All or a specific IP...  Did you find that?  Thanks!!<br><br>EDIT!!  One last question... Are you on Cable or DSL???<br>I'm having a devil of a time trying to get V1.50.18 to surf the web...  MTU settings in Linky or in computer don't matter... No surf... Back to V1.45.7 & OK.<br><br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10197828</guid>
<pubDate>Sun, 09 May 2004 20:11:49 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10197715</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : I forgot a question:<br><br>Is the traceroute problem a confirmed bug or some deliberate change from Linksys?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10197715</guid>
<pubDate>Sun, 09 May 2004 19:58:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10197602</link>
<description><![CDATA[<A HREF="/useremail/u/963087"><b>WayuU</b></A> : -Have to work even more on the refresh to get any settings page to show up. No big deal.<br>-As posted by others, tracert not working. Major aspect for me. It also reboots my router each time I try a tracert.<br>-Still no IP filtering? only URL filtering? also major problem for me.<br><br>BUT, I love the GUI overhaul. Looks nice and better structure to it.<br><br>WinXP+2000+2003 Server user. LAN.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10197602</guid>
<pubDate>Sun, 09 May 2004 19:43:47 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10197314</link>
<description><![CDATA[<A HREF="/useremail/u/722597"><b>LawnMowerGuy</b></A> : I just upgraded. Everything went smooth. I didn't even have to reset. I haven't tracert or pinged anything. DDNS doesn't work! I have an  account with DynDNS.org, I put in my info and get "Authorization fails(username or passwords)." Useless! <br><SMALL>--<br>Watch Family Guy<BR><A HREF="http://stevehorbachuk.com">website</A></SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10197314</guid>
<pubDate>Sun, 09 May 2004 19:02:04 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10196786</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : <BLOCKQUOTE><I>Browsing works fine now with SPI turned on.</I><BLOCKQUOTE><br>Well...'fixed' connection seems to be intermittent now.<br>Maybe I should try 1.45.7 ? ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10196786</guid>
<pubDate>Sun, 09 May 2004 17:37:14 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10196565</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : In the off chance that my first attempt was flawed.... I just spent another hour in V1.50.18..... loading only my PPPoE settings, and changing the the default password. This time I did not touch MTU enable or disable... Just told it my PPPoE settings, and let it do it's thing...<br>No Surfing here, not even to home page.<br>I then tried it all over a 2nd time, disabling SPI firewall.   No difference... <br>Finally I tried enabling or disabling MTU with SPI "off".<br>Still not surf...<br><br>All this was with only one Linky, not cascaded Linkys, but I'm on DSL, not cable..<br><br>Back on V 1.45.7 again (with cascaded Linkys)... (and confirmed that a restore will not set the Block Wan Request).. Set it manually...   All OK at V1.45.7 now...<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10196565</guid>
<pubDate>Sun, 09 May 2004 17:00:52 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10195989</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : <BLOCKQUOTE>Mjah, from which firmware version were you upgrading from? The reason I ask is because you seem to be getting a configuration upgrade problem. Simply restore the factory defaults and you should be fine. You can do this in the "Administration" tab and "Factory Defaults" sub-tab. If you don't know your settings by hard, keep some notes as after the restoring to factory default, you've got to start from scratch.</BLOCKQUOTE><br><br>I was upgrading from the original firmware. But oddly enough it seems you were right. Restoring the factory defaults seems to have fixed it for me. Browsing works fine now with SPI turn ed on. Cheers :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10195989</guid>
<pubDate>Sun, 09 May 2004 15:28:53 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10195881</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> :  <BLOCKQUOTE><SMALL>said by  drip <A HREF="/useremail/u/796816"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>curious, i have not seen anyone else notice a performance difference like i have with this new version of firmware.  web page loading is slower.  not just internal config pages but the internet in general was slower-the speed difference i must admit was minor.<br> <HR></BLOCKQUOTE>I am definitely not seeing this.  Internal pages do load more slowly, but external web pages load at the same speed as always.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10195881</guid>
<pubDate>Sun, 09 May 2004 15:09:44 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10194645</link>
<description><![CDATA[<A HREF="/useremail/u/796816"><b>drip</b></A> : it seems that i have had the pleasure of experiencing the mtu bug also.  all did seem fine till it was not able to load any web pages but i was able to ping.  immediately, there after i flash back to my previous version.  this is very asinine.<br><br>curious, i have not seen anyone else notice a performance difference like i have with this new version of firmware.  web page loading is slower.  not just internal config pages but the internet in general was slower-the speed difference i must admit was minor.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10194645</guid>
<pubDate>Sun, 09 May 2004 12:12:08 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10194388</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  ticker5 <A HREF="/useremail/u/286760"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Jan,<br><br>Since my last posting in this forum several weeks ago, I have moved on from the BEFSX41 to the SMC Barricade 7004FW using firmware 2.16.  It been working for three weeks without a problem.  It appears to do everything the Linksys was supposed to do and it costs $19 plus $10 for shipping on Ubid.com.  You might want to end the frustration by looking into alternatives.<br><br>Regards,<br>ticker<br> <HR></BLOCKQUOTE><br><br>At first this was a very educational experience, and I needed the education, believe me...  The problem is, when does an education become secondary to the frustration that this all brings?????   <br><br>If anyone from Linksys is reading this, I would be Happy to describe in detail what I've posted here over the months....  Please contact me, and I promise to be concise and without malice...<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10194388</guid>
<pubDate>Sun, 09 May 2004 11:34:02 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10193995</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : This is total and utter nonsense. Why do we have to put up with this B.S.? How can a company (any company) put out a product that DOES NOT function as advertized, expect its customers to BETA test their firmware and then release one firmware after another that actually breaks the product or worse and at best still does not enable the functions we paid for.<br><br>As soon as Buffalo releases their new hardware I am out of here. Its seems they are one of the best (better?)companies releasing consumer network gear.<br> ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10193995</guid>
<pubDate>Sun, 09 May 2004 10:36:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10193233</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : Ok I've answered one of my questions after much searching, found the hidden page, and yes I did do a backup and now all settings resored.<br>However question still begs to be answered why did the new firmware complain about McAfee doing a hacker trace, within 1 second of hitting the track button I lost all internet connectivity and had one red light top left hand corner of the router, had to wait till it sorted itself out before I could do anything.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10193233</guid>
<pubDate>Sun, 09 May 2004 07:27:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10193217</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : Well I'm back to using 1.45.7 as I tried to use a hacker trace with McAfee and it just fried my connection and it took me a couple of reboots to get it back.  Any idea why that may have happened and would there be a way to fix this?<br>Also is 1.45.7 the most stable firmware to use other than the latest?<br>And, sorry, I'm sure I did a backup of my firmware settings but for the life of me can't think of where or how, there was a hidden setting.  Do you backup to the router or outside, that is if I have upgraded to a different firmware have I lost my back up.<br><br>Sorry for all the questions]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10193217</guid>
<pubDate>Sun, 09 May 2004 07:15:08 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10192468</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : REMINDER FOR EVERYONE.  If you notice some web page are loading but some others are not, you are likely be getting an MTU problem.  Do not use the MTU option in the router if using 1.50.18 as it will render your internet connection useless.  Instead, tweak the MTU value on each of your PC behind the BEFSX41.  There are FAQ pages that helps you doing that.  Here they are:<br><br>&raquo;<A HREF="/faq/tweaks#4">Tweaking FAQ</A>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10192468</guid>
<pubDate>Sun, 09 May 2004 01:40:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10192416</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : GaryMiyakawa, could you say if your H.323 implementation uses some kind of ICMP-based trace route?  Or perhaps is it pinging the remote end with a very small TTL?  The reason I ask is I am wondering if you wouldn't be hitting the ICMP bug in 1.50.18 affecting ICMP-based trace route users.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10192416</guid>
<pubDate>Sun, 09 May 2004 01:30:57 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10192398</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Mjah, from which firmware version were you upgrading from?  The reason I ask is because you seem to be getting a configuration upgrade problem.  Simply restore the factory defaults and you should be fine.  You can do this in the "Administration" tab and "Factory Defaults" sub-tab.  If you don't know your settings by hard, keep some notes as after the restoring to factory default, you've got to start from scratch.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10192398</guid>
<pubDate>Sun, 09 May 2004 01:27:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10192373</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : haytak, even cable users will have problem if they enable MTU and set it to 1500.  The reason is, the MTU bug in the 1.50.18 does the following.  When MTU is enable, every single packet with the "Don't Fragment" bit set in the IP flags will be dropped despite what the MTU value is :(.  Bottom line, enabling MTU IS NOT AN OPTION right now.  I have informed Linksys about this but will send them more details on Monday about it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10192373</guid>
<pubDate>Sun, 09 May 2004 01:24:00 EDT</pubDate>
</item>

<item>
<title>Re: wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10192059</link>
<description><![CDATA[<A HREF="/useremail/u/286760"><b>ticker5</b></A> : Jan,<br><br>Since my last posting in this forum several weeks ago, I have moved on from the BEFSX41 to the SMC Barricade 7004FW using firmware 2.16.  It been working for three weeks without a problem.  It appears to do everything the Linksys was supposed to do and it costs $19 plus $10 for shipping on Ubid.com.  You might want to end the frustration by looking into alternatives.<br><br>Regards,<br>ticker]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10192059</guid>
<pubDate>Sun, 09 May 2004 00:32:21 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10192041</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Bill,   I experienced the same exact issues. I rolled back to the last firmware as well. I did notice that browsing seemed fine when using an ISP in which you can obtain an IP address automatically. I did not check if the router would reset when I performed a tracert though. Like your experience, doing a tracert DID reset the router when I was using a PPPoE ISP (SBC Yahoo DSL), and it would not allow me top browse many sites. What was interesting was that I could reach msn.com, but not hotmail.com, I could reach yahoo.com, but not yahoo mail or any of the links on the yahoo page. I also could not reach eBay, or Amazon.com. Interestingly enough, I could reach Linksys.com, but I could not download any firmware (FTP). <br><br>IF you have an ISP using PPPoE don't bother upgrading to this firmware until Linksys gets the bugs out.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10192041</guid>
<pubDate>Sun, 09 May 2004 00:28:47 EDT</pubDate>
</item>

<item>
<title>wHAT A FRUSTRATING COUPLE OF HOURS!!!</title>
<link>http://www.dslreports.com/forum/remark,10191683</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : My system: DSL (So I want an MTU of 1492, the value I'm presently using on my BEFSX41 V1.45.7).  <br>System is two Linkys in series: BEFSX41 (on 10... IP) in front of BEFSRU31 (on 192...IP)  Bridge miniport is my Network TCP/IP connection. Computers behind 2nd Linky are on Static IP's.  DNS (And Gateway) on computer(s) points to BEFSRU31, which in turn points to BEFSX41.  Conversely, I'm forwarding Wallwatcher's UDP port in BEFSX41 toward 2nd Linky which forwards it to the IP of the computer.<br>Upgrade to V1.50.18 went like this...  <br>Enabled DHCP on BEFSX41. <br>Enabled DHCP on Computer.  <br>Bypassed 2nd Linky and connected ethernet direct BEFSX41.  Turned off 2nd Linky and Modem.<br>Long Reset on BEFSX41 (factory defaults)<br>connected to Linky Http with default IP and password. OK.<br>Used ftp program from Linky Site, Upgraded to V1.50.18<br>Upgrade successful...     <br>Power cycled BEFSX41.  Logged into it with default IP & Password, to begin my configuration.<br><br>Configured for PPPoE, and my account settings. Per the information above... Disabled MTU.  Applied... Settings didn't stick.  Did 2nd, 3rd time, finally enabled MTU.  PPPoE settings stayed this time, and I saw my first all white screen... The setup menu was displayed again after a refresh button hit.  <br>Blindly stumbled through the settings (DAMN THEM for not including an up-to-date manual!) to get a minimum of settings installed (password change, account name).   I browsed through the other pages, each of which greeted me with a solid white screen, that occasionally refreshes with refresh button, but more often does not, or page back & page forward to get the pages to display...  The further I go with configs, the slower it goes, as I wait in vain for the page to re-load (Usually to a solid White screen) and me hitting Refresh or page back/page forward, to try and BS my way through the settings that came without documentation... I'm beginning to get angry...<br>With a minimal configuration set, turned on modem and manually forced a connect.  I was greeted with IP & DNS information!!..  So I try and surf... NOTHING! <br>Remembering the info from above, tried disabling or enabling MTU.... Didn't matter... nothing gets out. Doublechecked I was getting IP DNS entries from my ISP... Yep, I'm OK.  But still can't surf!<br>Then I remember Flog indicating that I may have to Set MTU in the Computer... <br>First tried DRTcP MTU (1492)set on Bridge setting, and reboot, followed by white screens in configuration screens as I try both Enable and Disable MTU in setup menu (When it displays, and isn't a solid white screen).. Neither worked, Still couldn't surf.<br>So, thinking that I should do it on the Network Card TCP/IP cause I'm not presently going through 2 Linky's.. So I try the network card MTU setting with DRTcP to 1492, followed by a reboot, and both settings in the setup menu... Nothing gets out here, either!...<br><br>So I'm thinking that maybe I have a DNS issue... so fire up PingPlotter.... to ping DSLReport's IP address... This, of course reboots the BEFSX41 !!!   <br><br>That's it!!! What an infuriating piece of CRAP!!!  <br>Re-Flashed V1.45.7, restored the settings I'd saved successfully!  (Note here that in V1.45.7 a Restore of settings saved does not re-enable  Block Wan Request (Pings) if it was origionally set to be this... So after a 'restore' remember to manually change it, if you want it enabled)<br>Disconnected Ethernet from BEFSX41, Powered up BEFSRU31,<br>Re-configured the computer from DHCP to Static IP, and added DNS and Gateway settings to BEFSRU31...<br>Connected ethernet to 2nd Linky... EVERYTHING WORKS FINE.<br>Went back into BEFSX41 setups... Display quicker, Far, FAR LESS WHITE SCREENS.....  and it WORKS!!!<br><br>I went back to V1.45.7 on my BEFSX41... <br><br>Can't Surf....Can't use PingPlotter!! Have to re-enter my PPPoE account information multiple times before it stops displaying "Get IP Automatically"  Didn't anybody test this???<br><br>PHOOEY!!!  WHO IN THEIR RIGHT MIND MAKES PRETTY SIGNIFICANT CHANGES IN A SYSTEM WITHOUT A REVISED INSTRUCTION MANUAL???<br><br>I can't use PingPlotter?  What a CROCK!!! <br>NO INSTRUCTIONS!! MTU is obviously not correct....<br>Trade one reboot for another, <br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10191683</guid>
<pubDate>Sat, 08 May 2004 23:36:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10191487</link>
<description><![CDATA[<A HREF="/useremail/u/368468"><b>GaryMiyakawa</b></A> : If you are trying to do H.323 Video, better not upgrade to the 1.50.18...  It always reboots the router...  1.45.6 seems to work just fine.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10191487</guid>
<pubDate>Sat, 08 May 2004 23:10:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10191301</link>
<description><![CDATA[<A HREF="/useremail/u/796816"><b>drip</b></A> : this may sound odd, and i know it is not very technical, but this firmware version seems to be slow.  web page loads are slower than usual and outlook is affected when concerning loads speeds.<br><br>i cant still can get over the tracert causing reboots.  i had to confirm it myself-was curious.  needless to say it is universal.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10191301</guid>
<pubDate>Sat, 08 May 2004 22:50:51 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10188372</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> :  <BLOCKQUOTE><SMALL>said by  RareDingo <A HREF="/useremail/u/764954"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>robewhitener are you a dsl or cable user.  I note that most otf the cable users are very happy with the new firmware but some of the dsl people are having MTU and other issues, like different sites loading etc.   I am having the same issues.  <HR></BLOCKQUOTE><br><br>I first reported the MTU error and I have a cable modem Terayon TJ715x on Comcast 3300/256<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10188372</guid>
<pubDate>Sat, 08 May 2004 15:58:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10186041</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : I can't do more tests right now, but check my previous post &raquo;<A HREF="/forum/remark,10176767~mode=flat">Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</A><br>It took 3.25 seconds.  Oh yes, SPI off, all logging options on<br>EDIT: Checked the WallWatcher logs: times are: 7.10; 6.10; 6.09; 9.11; 19.69; 13.02; 3.00; 2.98; 3.01<br>AliM]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10186041</guid>
<pubDate>Sat, 08 May 2004 09:56:21 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10185978</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : If someone would do a test on the new firmware for me, I'd appreciate it...  (This will simplify some tests tomorrow)<br>Document the time, Force a re-boot.  watch logs to see how long it takes till the Time Servers are accessed.<br>Then Do a power cycle and document how long it takes till the Time Servers are accessed. Also post if your Advanced Firewall was Enabled or Disabled. <br><br>Thanks...<br><br>Also thanks for the info on the hidden pages!<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10185978</guid>
<pubDate>Sat, 08 May 2004 09:43:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10185558</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Flashed to the new 1.50.18.<br><br>It seems that now I can only browse webpages with the firewall disabled :(<br><br>Enabled I get shite like 'Time Filter Policy Matched' and it drops all packages.<br>Anyone know what is going on ?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10185558</guid>
<pubDate>Sat, 08 May 2004 08:05:14 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10185498</link>
<description><![CDATA[<A HREF="/useremail/u/731962"><b>heytak</b></A> : will the cable users not have a problem with MTU by enabling and setting it to 1500 than using auto?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10185498</guid>
<pubDate>Sat, 08 May 2004 07:45:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10185249</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Not quite befsx41 related, but the only wired BEFxxnn series "New GUI Style" User manuals are for SR81, SR41v3 and VP41v2. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10185249</guid>
<pubDate>Sat, 08 May 2004 05:14:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10185176</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : I have also sorted out my FTP problem, I needed to set up the ports one less IE 2020 and 2021 plus I had to also set up the PASV range, now this firmware seems to be doing the do :D]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10185176</guid>
<pubDate>Sat, 08 May 2004 04:21:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10185099</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : &raquo;<A HREF="http://ttester.broadbandreports.com/tweak/block:3f0de66?verbose=1&service=dsl&speed=1500&os=winXP&via=routerpppoe" >ttester.broadbandreports.com/twe&middot;&middot;&middot;terpppoe</A><br><br>I have done as you asked flogater and used Dr TCP not sure if I set it all right.  I'm on a ADSL connection at 1500/256 I'll see what difference it makes]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10185099</guid>
<pubDate>Sat, 08 May 2004 03:47:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10184623</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : robewhitener, sorry to disappoint you but BEFSX41 firmware 1.50.18 is boring in terms of hidden pages :(.  I quickly scan through the firmware binary and could only find those three:<br><br>- "http://192.168.1.1/BackupnRestore.htm"<br>- "http://192.168.1.1/Log4Manage.htm"<br>- "http://192.168.1.1/SysInfo.htm"<br><br>All of the other hidden pages from firmware 1.45.7 are gone :(.  Note that as AliM pointed out earlier, this firmware contains three hidden page content that cannot be addressed directly on the router.<br><br>- The one about QoS (refer to AliM post <A HREF="http://www.broadbandreports.com/forum/remark,10176452">here</A>)<br>- The one about Wireless (refer to AliM post <A HREF="http://www.broadbandreports.com/forum/remark,10176452">here</A>)<br>- The one about the WAV54G (see attached picture)<br><br>Don't get too exited, I'm afraid that those three hidden page contents are simply forgotten cut and paste mistakes.  Nevertheless, nothing to get exited there.<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10184623?c=590249&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="67090 bytes" WIDTH=600 HEIGHT=290 SRC="/r0/download/590249.thumb600~8fe78562fdb8339910b9d0743530bef8/wav54g.jpg/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10184623</guid>
<pubDate>Sat, 08 May 2004 01:20:09 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10184336</link>
<description><![CDATA[<A HREF="/useremail/u/947119"><b>Quantum</b></A> : No wonder I wasn't getting any webpage issues, I just recently switched to cable :D no MTU problems I just have it disabled.<br><SMALL>--<br>Keep On Folding! F@H H2O Team OCC 12772</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10184336</guid>
<pubDate>Sat, 08 May 2004 00:23:41 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10184028</link>
<description><![CDATA[<A HREF="/useremail/u/416336"><b>robewhitener</b></A> : Now it's time to find the hidden, (goodies) pages.. :)   <br><br>Have a good one all.<br><SMALL>--<br>Robert</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10184028</guid>
<pubDate>Fri, 07 May 2004 23:34:50 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10183945</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Jan, I just checked the BEFSX41 user's guide.  It still refers to the old configuration web page.  I guess we're by ourselves there as well ;).  I got to say that after browsing through the new GUI, it only took few seconds to get used to it.<br> <HR></BLOCKQUOTE><br><br>I'll find out Sunday!!!!  <br><br>Later!!!<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183945</guid>
<pubDate>Fri, 07 May 2004 23:22:55 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10183897</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Jan, I just checked the BEFSX41 user's guide.  It still refers to the old configuration web page.  I guess we're by ourselves there as well ;).  I got to say that after browsing through the new GUI, it only took few seconds to get used to it.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183897</guid>
<pubDate>Fri, 07 May 2004 23:15:23 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10183872</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : robewhitener, thank you very much for your update.  That confirms my theory.  Users on DSL must tweak their MTU value on their PC.  The most important for me is the fact that DSL users can make use of firmware 1.50.18 :).  That's good news (and more work for the DSL users who have not yet tweaked their MTU value).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183872</guid>
<pubDate>Fri, 07 May 2004 23:12:36 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10183668</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> : I've been lurking, reading... I just got home (almost 10P), and work (long hours) tomorrow... Will try it Sunday.... But at the rate you all are going...... I may not be contributing much...  (DSL here)<br><br>Did any of these new pages/Setups make it to the manual?  I hate stumbling around in the dark!!<br><br>The fellow who commented that text of blocking wasn't appearing in the logs, try turning off the Advanced Firewall.... That was what fixed it in V1.45.7!<br><br>I've another question to the user's... When I rebooted or power cycled V1.45.7, I found that the time between reboot or power up, and Time Server access varied depending on Reboot or Power Cycle, and whether Advanced Firewall was enabled or disabled...    <br><br>Obviously, during the time between Bootup and Time Server Access leaves filters un-working... <br><br>Anyone determine if the Time Server access is closer spaced to the bootup, and does Advanced Firewall enabled or disabled affect the Time Server access???<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183668</guid>
<pubDate>Fri, 07 May 2004 22:46:10 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10183667</link>
<description><![CDATA[<A HREF="/useremail/u/416336"><b>robewhitener</b></A> : Here are the results..  Used Drtcp to set MTU to 1492.  All of the sites that were not showing up before, are loading now.  streaming video from Atomfilms is fine.  If any others on DSL can try this.  The two machines that are on linksys 80211b WAP loaded the sites up fine without an MTU adjustment.  The wired machine MTU needed to be adjusted <br><br>go figure.. :) <br><br>Home network setup is as follows:<br><br>Westell WS2200 - Bellsouth Firmware<br><br>SX41 as Router - DHCP Server<br><br>WAP11 ver 2.6 WAP  --- yeah, yeah, I know it's old. :) <br><br>Netgear 8 port switch ---  Uplink plugged into SX41 <br>WAP and wired machines are plugged into the switch. <br><br>SX configuration currently is as follows:<br><br>Manual MTU - disabled<br>VPN -  disabled<br>DHCP Server - Enabled<br> Block Anonymous Internet Requests:Enabled   <br>          Filter Multicast:Disabled   <br>          Filter Internet NAT Redirection:Enabled           Filter IDENT(Port 113):Enabled Disabled   <br>       <br>UPNP - disabled<br>Haven't set filters up yet. <br><br>I guess I'll leave the SX41 MTU to disable, and adjust from the boxes... <br><SMALL>--<br>Robert</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183667</guid>
<pubDate>Fri, 07 May 2004 22:46:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10183324</link>
<description><![CDATA[<A HREF="/useremail/u/416336"><b>robewhitener</b></A> : I'll try it.  I'm relativly familiar with Drtcp.  <br><br>I'll let you know what happens. <br><br>Regards<br><SMALL>--<br>Robert</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183324</guid>
<pubDate>Fri, 07 May 2004 22:01:21 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10183133</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Hmmm, indeed, my test unit is on cable modem right now.  I don't want to play with my remote sites (which are half on DSL and half on cable) right now.  However, sounds like there would be something to chase on the DSL side.<br><br>robewhitener and RareDingo, have you ever tweak the MTU metric on your Windows-based PC?  I'm asking this because since the very first day I hook my PCs on a DSL connection, I had to tweak their MTU value.  I started with ICS so there is nothing to do with the router.  If you have never did tweak the MTU, it might be a good idea unless you plan to switch to cable.  It just happened that in firmware 1.45.7, Linksys introduced a new behavior about the MTU.  By tweaking the MTU on the PCs, everything get back to normal.  You may find more information about this at the following FAQ pages:<br><br>&raquo;<A HREF="/faq/tweaks#4">Tweaking FAQ</A><br><br>If any of you guys are willing to tweak the MTU and try again with BEFSX41 firmware 1.50.18, that would be very valuable information to post in this thread.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10183133</guid>
<pubDate>Fri, 07 May 2004 21:30:27 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10182678</link>
<description><![CDATA[<A HREF="/useremail/u/416336"><b>robewhitener</b></A> : Hi Raredingo:  it's a dsl connection...  sounds like we're in the same boat.  MTU must make all the difference...  <br>If that's the case, instead of fiddling around with drtcp, I think it's back to 1.45.7... <br><br>ah well.  Liked the interface.  just wish the underlying motor wanted to work well.. <br><br>Flogater, you're a true master... thanks for all the input. <br><SMALL>--<br>Robert</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10182678</guid>
<pubDate>Fri, 07 May 2004 20:32:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10182628</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : robewhitener are you a dsl or cable user.  I note that most otf the cable users are very happy with the new firmware but some of the dsl people are having MTU and other issues, like different sites loading etc.   I am having the same issues.  Sometimes pages will load and other times they just sit and look at me.  I have found also I can't set up an ftp server on port 2121 like I had last time, I can log in but get errors telling me 'data socket line error' which I never had before.  I will try to fix this over the next few days or I'll have to downgrade, :huh:<br>flogater thanks for your suggestion re MTU I don't really want to stuff around with the default settings for MTU with XP as I may not get them back and also it seemed to be working well with the previous firmware.  I'll just have to keep lookng]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10182628</guid>
<pubDate>Fri, 07 May 2004 20:25:51 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10182374</link>
<description><![CDATA[<A HREF="/useremail/u/416336"><b>robewhitener</b></A> : MTU is disabled.  did the long reset.  Set up from scratch.  BBr comes up fine.  a lot of other sites come up fine.  I'm currently doing a no risk audit from securityspace.com.  Just certain sites.  grc.com, ign.com, cnn.com, and a bunch of others just sit there and spin.  I'm trying to figure if there's a dns problem on the machine, but I did a ipconfig /dnsflush.  I would have thought that would have done the trick.  I'm currently stumped... ;(.  <br><SMALL>--<br>Robert</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10182374</guid>
<pubDate>Fri, 07 May 2004 19:55:18 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10182231</link>
<description><![CDATA[<A HREF="/useremail/u/947119"><b>Quantum</b></A> : I can access the web without any problems including grc.com. Do you have MTU disabled?<br><br>Have you done a long reset? When I updated the firmware I did the long reset on the router and then setup everything from scratch.<br><SMALL>--<br>Keep On Folding! F@H H2O Team OCC 12772</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10182231</guid>
<pubDate>Fri, 07 May 2004 19:38:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10181774</link>
<description><![CDATA[<A HREF="/useremail/u/416336"><b>robewhitener</b></A> : so far, the strangest thing that I have found is that I cna't get to certain websites that I had no problem getting to with 1.45.7.   <br><br>grc.com just makes the browser sit ther and do nothing, as does a bunch of other sites.  grc is the one I generally go to first after a FW upgrade.   Any ideas? <br><SMALL>--<br>Robert</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10181774</guid>
<pubDate>Fri, 07 May 2004 18:51:24 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10181265</link>
<description><![CDATA[<A HREF="/useremail/u/947119"><b>Quantum</b></A> : I have been running firmware 1.50.18 since this morning and I have to say that my SX41 on 1.45.7 was having some serious reboot problem everytime F@H would submit data. Now with 1.50.18 the router is definitely more stable no more rebooting problem so far.<br><br>On the flip side I am trying to set up an IP as DMZ under the Applications & Gaming tab, but everytime I click on enable the page goes blank. In short I can not seem to be able to enable DMZ, has anybody, working with 1.50.18, encountered this problem?<br><SMALL>--<br>Keep On Folding! F@H H2O Team OCC 12772</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10181265</guid>
<pubDate>Fri, 07 May 2004 17:53:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10180293</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> : To add (no pun intended), it seems like the filter traps some entries but not others.<br><br>I use www.weather.com as a good test site. It generates a bazillion ads, and I've blocked most of them.  Lots of yellow "keyword/URL matched" enttries in WallWatcher and lots of red x's in the web page where all the ads would be.<br><br>But my entry to block ads1.howardchui.com doesn't work.  I still connect to that ad generator every time I go to HoFo.<br><br>--jeff]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10180293</guid>
<pubDate>Fri, 07 May 2004 15:52:07 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10180267</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : jefe, you are correct.  If the router (either internally or through its SNMP trap logs catched by WallWatcher) time is accurate, it has synchronized its time.  Then I must reuse your quote:  <B><I>Bummer.</I></B>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10180267</guid>
<pubDate>Fri, 07 May 2004 15:48:45 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10180232</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : I cannot get any of the hidden router pages to work.  Anyone else seeing this or is it just me?<br><br>I had never heard of the v2 BEFSX41 but I was looking around on the Linksys site and was submitting some feedback and it asked to select which one.  I had to look at my Linksys to see if I had v1 or v2.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10180232</guid>
<pubDate>Fri, 07 May 2004 15:44:20 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10180178</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>I know I shouldn't ask but was the time synchronized in the router at the time you tested the filters?<br> <HR></BLOCKQUOTE>Weeeeellll...I think so.  I've never been sure how to know if it is or isn't.<br><br>There is a time displayed on the status page, and it appears to be correct.  So I think the answer is yes...it's syncronized.<br><br>Is my assumption correct?<br><br>edit:  System log also shows this:<br><br>2004-05-07 15:42:14 Get current time from NTP server : May 07 2004 Fri. 15:42:14]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10180178</guid>
<pubDate>Fri, 07 May 2004 15:37:17 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10180039</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : I know I shouldn't ask but was the time synchronized in the router at the time you tested the filters?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10180039</guid>
<pubDate>Fri, 07 May 2004 15:18:54 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10179876</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR><I>Let's rename that feature to look like we are introducing a new one</I>:o.<br> <HR></BLOCKQUOTE>Ah so.  Well, maybe it will be useful to someone.  Not me.<br><br>BTW, I may have spoken too soon.  I thought keyword/URL filtering was working but now it seems not to be.<br><br>I have ad.doubleclick.com and doubleclick set up in the URL filter and keyword fields, for example, and yet I'm still seeing connections to that PITA web site in WallWatcher.<br><br>Bummer.<br><br>--jeff]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10179876</guid>
<pubDate>Fri, 07 May 2004 14:56:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10179816</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Ahhh, that one :D.  That feature used to be called "Working Mode" off the "Dynamic Routing" tab.  This basically allow a user to configure the BEFSX41 as a dummy router and to optionally run some kink of routing protocol such as RIP.<br><br>You are correct though.  This feature is useless for most users such as us.  It comes pretty handy however when you are building a small network, want to create subnets and don't want to spend lots of money in a real router ;).  In any case, the "NAT" feature is not a new feature.  It is just a remake of an old one that used to be called "Working Mode".  I guess it is the same thing as the local loopback isn't.  I call that a Marketing game:  <I>Let's rename that feature to look like we are introducing a new one</I>:o.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10179816</guid>
<pubDate>Fri, 07 May 2004 14:49:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10179703</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> :  <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>jefe, thank you for your update.  About the Java-based speed test, are you using any of the web filters?  Most of the speed test crashes in earlier version were related to these web filters.<br><br><HR></BLOCKQUOTE>I was using some filters, Flogator, but haven't recreated them yet.  I'll do so now and report back.<br><br> <BLOCKQUOTE><SMALL>said by  Flogator <A HREF="/useremail/u/755875"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR><br>Additionally, about the ability to turn off NAT.  Are you referring to the feature called "Filter Internet NAT Redirection"?   <HR></BLOCKQUOTE>Nope.  See the screen grab.  The feature I'm talking about looks like it will actually turn off NAT completely.  I haven't tried it yet and I'm not sure I want to.  :D<br><br>--jeff<br><br>edit:  I've enabled some filtering.  Keyword fileters seem to work well.  Speakeast java based speed tests still do not cause reboot.<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10179703?c=589988&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="26110 bytes" WIDTH=600 HEIGHT=140 SRC="/r0/download/589988.thumb600~d111570b8527e3a0d8f1fb19a62e8325/nat.jpg/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10179703</guid>
<pubDate>Fri, 07 May 2004 14:33:38 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10179569</link>
<description><![CDATA[<A HREF="/useremail/u/281155"><b>dlopez</b></A> : Thanks for the answer Flogator.<br><br>But it would seem ftrace web site ftp server is not working due to everyone probably trying to get the utility.<br><br>I still can't believe those bone heads screwed up something as basic as tracert or any other UDP utility. :( <br><br>I will keep trying if you have any other suggestions I would love to hear them.<br><br>Thanks ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10179569</guid>
<pubDate>Fri, 07 May 2004 14:17:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10179496</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : jefe, thank you for your update.  About the Java-based speed test, are you using any of the web filters?  Most of the speed test crashes in earlier version were related to these web filters.<br><br>Additionally, about the ability to turn off NAT.  Are you referring to the feature called "Filter Internet NAT Redirection"?  If so, that is the feature that used to be called local loopback ;).  Now we have the ability to enable or disable it (still don't understand why you would want to disable it though).  If you enable the feature, you lose local loopback.  If you disable the feature you gain local loopback.  The local loopback feature is the one by which you can access your private servers (i.e. web server or email server located on your LAN) by using the WAN IP address.<br><br>I suspect that most of us will be beating this firmware even further over the week-end.  It'll be very interesting to see the results.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10179496</guid>
<pubDate>Fri, 07 May 2004 14:08:47 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10179116</link>
<description><![CDATA[<A HREF="/useremail/u/393752"><b>jefe</b></A> : Results here:<br><br>I updated using Tftp.exe.  Worked first attempt.<br><br>I had no trouble connecting to the Net through the router and my SB4200 cable modem.  However it took several reboots of the router before I could get to the html setup page.<br><br>All settings were reset to factory defaults.  Filters, etc, had to be rebuilt.<br><br>New html interface.  I like it so far, except page changes seem a little slow.<br><br>When I reset the router's local IP address to fit with the rest of my LAN, I also had trouble getting the config<br>manager.  Another reboot seems to have taken care of that.<br><br>Bock Port 113 available as a choice now.<br><br>I have always set MTU to disable/auto.  Disable in the new firmware worked for me.<br><br>Speed tests nominal.  And java based speed tests don't reboot the router, as has been a problem with some earlier versions.<br><br>All ports stealthed reported by Shield's Up and BBR scan.<br><br>There's a button to turn off NAT! Why would anyone want to do that?  Put your entire LAN in DMZ?<br><br>You can choose the default NTP server, or user select one.   Hallelujah.<br><br>I've beat the new firmware up for an hour or so now.  Everything seems to work here, and all is stable.  Keeping my fingers crossed.<br><br>--jeff]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10179116</guid>
<pubDate>Fri, 07 May 2004 13:22:40 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10177808</link>
<description><![CDATA[<A HREF="/useremail/u/641121"><b>MrMoke</b></A> : The fact that they are porting code from other models isn't new. They have been doing that for years. It probably goes a long way to explaining why they have sooooo much trouble getting anything to work correctly, and emphasizes several of my longtime complaints:<br><br>They spend more time looking for new features than working on fixing the existing ones.<br><br>They waste resources by including unusable code, and don't show pages for usable features like save/restore.<br><br>Maybe we should start a thread for Linksys programmers, and give them some basic training in the proper use of compiler directive things like:<br><PRE><br>#include <br>#include <br>#define WIRED     // or WIRELESS<br>#define MODEL = 1 //    0=BEFSR41, 1=BEFSX41, 2=BEFVP41<br>                  // or 0=WRT54G... for WIRELESS<br>using namespace std;<br>int main(int argc, char *argv[])<br>{<br>#ifdef WIRED<br>#if MODEL == 0<br>    cout &lt&lt "Include this code for BEFSR41" &lt&lt endl;<br>#elif  MODEL == 1<br>    cout &lt&lt "Include this code for BEFSX41" &lt&lt endl;<br>#elif  MODEL == 2<br>    cout &lt&lt "Include this code for BEFVP41" &lt&lt endl;<br>#endif<br>#else<br>    cout &lt&lt "Include this code for all WIRELESS" &lt&lt endl;<br>#endif<br>  system("PAUSE");<br>  return 0;<br>}<br></PRE><BR><br>The same techniques could be used to differentiate between DEVELOPMENT and PRODUCTION code blocks.<BR> <br>If you understand enough to get on my case, then you get the point, so don't say it. :)<br>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10177808</guid>
<pubDate>Fri, 07 May 2004 10:31:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10177419</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : dlopez, may I just re-iterate that it is the ICMP-based trace route that is crashing the router.  It is the UDP-based trace route you want to use to prevent reboot.  If you look in one of my previous post, I put a link to a 3rd party utility (ftrace).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10177419</guid>
<pubDate>Fri, 07 May 2004 09:28:33 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10177405</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : humphreysa, if you enable more logs, you will actually see the lease time in the logs ;).  Thanks to AliM for his logging trick.  To enable it, go to "http://192.168.1.1/Log4Manage.htm" and select the second check box called "System hid_log4Manage".  Hit the apply button and you will see something like this in your logs:<br><br>WAN LeaseTime=81931 sec]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10177405</guid>
<pubDate>Fri, 07 May 2004 09:26:19 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10177387</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : RareDingo, you can apply the MTU changes to your PC and leave it disabled in the router.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10177387</guid>
<pubDate>Fri, 07 May 2004 09:23:10 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10177380</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : haytak, meant to mention I have tried the following features and they all seems to be working fine:<br>- SNMP<br>- Local Loopback (now called Internet NAT Redirection)<br>- VPN end-point and passthrough<br>- Was always using SPI firewall<br>- Port forwarding (mainly for an HTTP server)<br>- DDNS<br>- UPnP<br>- FTP loading up and down (as a client not as a server)<br><br>I did not try the following<br>- Web Filters<br>- Filters (now in the Restrict Access tab)<br>- FTP loading up and down as a server<br>- DMZ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10177380</guid>
<pubDate>Fri, 07 May 2004 09:22:21 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10176767</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Router is sending requests to ALL time servers (0.0.0.0 is one you can add) and then waiting for first one to respond. Stupid. Making more traffic then needed. AliM<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10176767?c=589828&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG TITLE="58303 bytes" BORDER=0 WIDTH=594 HEIGHT=204 SRC="/r0/download/589828~43eaacc807d5538e709d96a915eb1a23/time_ntp.jpg"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10176767</guid>
<pubDate>Fri, 07 May 2004 06:49:44 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10176598</link>
<description><![CDATA[<A HREF="/useremail/u/901578"><b>hananz</b></A> : 12 hours later .....<br>had problems with browsing and getting mails<br>(mtu was disabled) the pages once came and once didn't<br>mail had the same problem once i got thou and once got <br>an error <br><br>so i went back to 1.45.7 and every thing it working properly (except the thing the doesn't work ;) ) ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10176598</guid>
<pubDate>Fri, 07 May 2004 05:06:40 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10176486</link>
<description><![CDATA[<A HREF="/useremail/u/281155"><b>dlopez</b></A> : Linksys=Crap<br><br>Amazing a company that is owned by Cisco can't get tracret or any other UDP utility you can think of  PingPlotter ver 1.0 for example to work.<br><br>Damm out sourced programing staff. :mad:<br><br>Anyone have any suggestions for a ICMP based utility.<br><br>The interface is a little slow but other than that the only issue I have is the numb nuts messed up tracert of all things.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10176486</guid>
<pubDate>Fri, 07 May 2004 03:51:30 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10176452</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Hi everybody, It seems that Linksys is working on something; check the picture!! Yes, it's QoS. You can't access it, but it is in the firmware code (If not perhaps some remnant from sr81, hmmm, let Linksys to surprise us once). But I'm sure they will NOT add wireless..... they're dragging pieces of code from another models.<br>Another finding: Secret page Log4Manage.htm now has more options.<br>AliM<br><br>P.S. Anybody heard about Befsx41 V2, shops in Netherlands are selling them.<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10176452?c=589820&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="84708 bytes" WIDTH=600 HEIGHT=434 SRC="/r0/download/589820.thumb600~8f77d283dbc39945d6b6b85c053f6329/befsx41_QoS.jpg/thumb.jpg" ALT="Click for full size"></A></TD></TR><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10176452?c=589821&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="71178 bytes" WIDTH=600 HEIGHT=434 SRC="/r0/download/589821.thumb600~4c15098bfc80d9dec872687eca84b5ab/wless.jpg/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10176452</guid>
<pubDate>Fri, 07 May 2004 03:36:31 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10176387</link>
<description><![CDATA[<A HREF="/useremail/u/805762"><b>machater</b></A> : Well it works, it's faster but... setting my ntp is still broken from my server!!! ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10176387</guid>
<pubDate>Fri, 07 May 2004 03:13:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10176317</link>
<description><![CDATA[<A HREF="/useremail/u/996454"><b>humphreysa</b></A> : I was using 1.50.9 and it kept my settings when upgrading. Cool.<br><br>There's only two differences I notice so far, both of which have already been reported. Namely the router cold rebooting for ICMP tracert and the Filter IDENT(Port 113) option on the security page.<br><br>I do miss the WAN DHCP client lease time from the 1.45.7 status page.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10176317</guid>
<pubDate>Fri, 07 May 2004 02:45:36 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10175993</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : OK all a follow up, I rang my ISP regards the MTU settings and they recommended 1432 or 1400 straight up. He also suggested I reboot the modem the router and the system to make sure.  This I did, so I went back as a last resort a disabled MTU.  Low and behold it is now working.  I can access other sites and pages including one of my favourites, this one ;)  <br>However, I have no idea why it just started to work on its own, wish I had more knowledge regarding networks and routers to advise you but....<br>mIRC seems to be intermittent at best and is a good indicator for me of a clean connection as if i get drop outs that's the first indication.<br>I now have to set up transfers for mIRC and messenger and FTP, sure wish I didn't lose all my settings but....<br>I'll keep you all posted]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10175993</guid>
<pubDate>Fri, 07 May 2004 01:22:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10175901</link>
<description><![CDATA[<A HREF="/useremail/u/731962"><b>heytak</b></A> : how about other features in 1.50.18?<br>SNMP, loopback, VPN, ftp uploading, advanced SPI,web filtering, port filtering, ddns, UPnP, DMZ....]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10175901</guid>
<pubDate>Fri, 07 May 2004 01:10:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10175650</link>
<description><![CDATA[<A HREF="/useremail/u/287036"><b>cghh</b></A> : As with other recent versions, with 1.50.18, when MTU is disabled and PPPoE is in use, the MTU is set to 1492, which is what one generally wants in this situation (1500 Ethernet max - 8 byte PPPoE header). Web browsing and such is working fine for me.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10175650</guid>
<pubDate>Fri, 07 May 2004 00:29:50 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10175320</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Just to provide additional information about the MTU problem first reported by AxiaThndbird.  I have found the root cause and will be reporting the finding to Linksys tomorrow in the morning.<br><br>Basically, when the the MTU is enabled in firmware 1.50.18, the router will not allow any packets from WAN-to-LAN that has the "Don't fragment" bit set in the IP flags.  The simplest test is the following commands from the command prompt in windows (when MTU is enabled of course):<br>- ping yahoo.com (this succeed)<br>- ping -f yahoo.com (this does not succeed)<br><br>Packet sniffing on both the WAN and LAN side demonstrated that echo response with "Don't fragment" bit set is dropped by the router.  It just happen that when you surf the web that the very first packet being sent by the server (a TCP SYN packet) has the "Don't fragment" bit set in order to establish proper MSS between the client and server.  Because the router drops the packet when MTU is enable and this bit is set, then the TCP connection holding the HTTP session between the client and server never get established thereof, no web pages can be viewed.  Amazingly enough, this behavior is not present when MTU is disabled in the router.<br><br>The current unit I use to test 1.50.18 is on cable modem so MTU is not an issue.  At this stage of the game, I am not involving my remote sites (the one on DSL) anytime soon with 1.50.18.  Therefore, could anyone testing this firmware and using DSL could post if this firmware works for them when MTU is disabled (but set to a lower value).  Thanks.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10175320</guid>
<pubDate>Thu, 06 May 2004 23:51:56 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10174949</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Just to add to everybody's comment about trace route.  The router seems to be sensible to ICMP-based trace route.  I haven't figure it out why yet but will be looking into it soon.  Meanwhile, one possible solution is to use a UDP-based trace route utility.<br><br>If you are a Linux user, the utility <B>traceroute</B> uses UDP by default.  This utility is flexible as by using the -I option, you can revert to an ICMP-based trace route.<br><br>If you are a Windows user, tracert only support ICMP-based trace route.  If you want to use UDP-based trace route, you have no choice but to turn yourself to a 3rd party software.  You can check out <A HREF="http://www.r1ch.net/stuff/ftrace/">ftrace</A> as an example.<br><br>I have just tested traceroute in Linux and it is working beautifully ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174949</guid>
<pubDate>Thu, 06 May 2004 23:07:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10174872</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Just to add on AliM's comment about the new default NTP servers in 1.50.18 ;).<br><br>- time.nist.gov (192.43.244.18) is a primary server<br>- time.windows.com (207.46.130.100) is a secondary server<br>- ncnoc.ncren.net (128.109.193.1) is a secondary server<br><br>All three servers are currently replying to NTP requests.  The router seems to still be polling the servers once an hour.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174872</guid>
<pubDate>Thu, 06 May 2004 22:58:09 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10174804</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Ok, I finally had a chance to test the firmware myself.  Don't have much new information to report other than what has already been found.  Between firmware 1.45.7 and 1.50.18, I did noticed one little tiny bug fixed.  Here is a quick description of the bug (you'll laugh).<br><br>In firmware 1.45.7 and earlier, there is a bug in SNMP.  The bug is when you walk down the MIB attributes in the router while DDNS is being used, the SNMP walk will fail after few of the attributes.  The failure is not much, it just return the same OID as requested in a get-next command (that should not happen).  The work around is easy, you simply have to force the SNMP utility to increment the OID by one on the next get-next ;).  In any case, starting in firmware 1.50.18, you no longer require that workaround as Linksys fixed the bug.  Youpi!!!  Well, the cost of that bug fixed is the following new bugs introduced by the firmware :(<br><br>- ICMP-based trace route utility crashes the router (workaround:  use a UDP-based trace route utility)<br>- Enabling MTU hogs the router and thereof makes the internet connection useless (workaround:  disable MTU)<br>- Some items of web pages of the router never shows up (workaround:  hit the reload button on your browser)<br><br>I guess to be fair, there has been some improvement from firmware 1.45.7.  Here they are:<br>- The default three NTP servers are all working :).<br>- You can safely specify your favorite NTP server :).<br>- You may optionally filter the IDENT port (113) (could do it with port forwarding before).<br>- You may optionally filter local loopback now called Internet NAT Redirection (don't know why someone would enable that).<br>- The UPnP feature has a new option: Allow users to Disable Internet Access (don't know what that is yet).<br>- You may now optionally send email alerts to a email account.<br>- You may run ping diagnostics from the router.<br><br>The disclaimer is that I did not tested the filters in this firmware (so don't know if they work).  Additionally, I was gentle with the router given all of the reported crashes and internet loss.  Other than that, firmware 1.50.18 and 1.45.7 seems to have the same features, bug fixes and limitations.  Bottom line, if you are looking for stability you may want to downgrade to 1.45.7 because of the three newly introduced bugs.  However, if you want to play a little more, you may hang on to it.  With the preliminary tests that I have done, I am willing to keep this firmware on one of my units for a week just to stress it more ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174804</guid>
<pubDate>Thu, 06 May 2004 22:50:48 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10174491</link>
<description><![CDATA[<A HREF="/useremail/u/813996"><b>jansm38</b></A> :  <BLOCKQUOTE><SMALL>said by  jammddr <A HREF="/useremail/u/201945"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Just upgraded mine 20 minutes ago from 1.50.9.  Everything works great except for tracert.  I barley ever use tracert anyway.  Tried it b/c everybody is complaining about it and the router rebooted.  <STRONG>I did notice that the router reboots much faster than with the 1.50.9 firmware.</STRONG>  One other problem I noticed with the 1.50.9 version was that my router rebooted itself once a week.  Hopefully this update fixes that.  But now we have a new bug to work with.  Hopefully Linksys will fix it.<br> <HR></BLOCKQUOTE><br><br>Woo Hoo!  Finally, something positive comes from a Linksys firmware upgrade!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174491</guid>
<pubDate>Thu, 06 May 2004 22:21:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10174333</link>
<description><![CDATA[<A HREF="/useremail/u/777093"><b>Dustyn</b></A> : Will Linksys ever come out with a firmware update that doesn't act like a beta release? :hmm:<br><br>More and more they introduce new exciting problems with each release.<br><br>Sad... :huh:<br><br>EDIT: <B>Linksys does not recommend updating firmware...AT ALL</B>.<br><br><SMALL>--<br><B>Cruising down the Sunset Strip,<br>And there is nothing that's not,<br>That's not within my grip,<br>Oh, tonight, I got it right,<br>Just one time</B> ~ Courtney Love</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174333</guid>
<pubDate>Thu, 06 May 2004 22:06:28 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10174198</link>
<description><![CDATA[<A HREF="/useremail/u/201945"><b>jammddr</b></A> : Just upgraded mine 20 minutes ago from 1.50.9.  Everything works great except for tracert.  I barley ever use tracert anyway.  Tried it b/c everybody is complaining about it and the router rebooted.  I did notice that the router reboots much faster than with the 1.50.9 firmware.  One other problem I noticed with the 1.50.9 version was that my router rebooted itself once a week.  Hopefully this update fixes that.  But now we have a new bug to work with.  Hopefully Linksys will fix it.<br><SMALL>--<br>I live in that place... That place is Silent Hill.</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174198</guid>
<pubDate>Thu, 06 May 2004 21:51:52 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10174069</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : Thanks for the reply but as stated I followed all of the instructions including the disabling of the MTU settings ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10174069</guid>
<pubDate>Thu, 06 May 2004 21:36:49 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10173965</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : i'm saying that if you have MTU enabled to anything it will kill your internet connection. You have to have MTU disable to go anywhere on the net.<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10173965</guid>
<pubDate>Thu, 06 May 2004 21:24:52 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10173909</link>
<description><![CDATA[<A HREF="/useremail/u/764954"><b>RareDingo</b></A> : OK some help needed here, something weird is happening.  Blah, I've lost all my settings to BTW, so I have to go back to them again and set them up eventually.<br><br>However after upgradeing to 1.50.18 and following all the recent instructions, I find I can surf my local ISP's pages and Mcafee pages but that's about it.  I cannot for example get back into this forum.  So I'm back using 14.3 at the moment untill someone can give me an answer.<br><br>Look forward to your replies]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10173909</guid>
<pubDate>Thu, 06 May 2004 21:19:07 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10173650</link>
<description><![CDATA[<A HREF="/useremail/u/859462"><b>kirk1233</b></A> : ARGH Is there any way to get this firmware to allow tracetoutes to work?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10173650</guid>
<pubDate>Thu, 06 May 2004 20:49:34 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10173438</link>
<description><![CDATA[<A HREF="/useremail/u/972855"><b>ElJay</b></A> :  <BLOCKQUOTE><SMALL>quote:</SMALL><HR> Time servers in different firmwares:<br><br>1.50.18 - and all 3 are responding!!!<HR></BLOCKQUOTE><br><br>Is it still polling the time server every hour?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10173438</guid>
<pubDate>Thu, 06 May 2004 20:28:17 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10173354</link>
<description><![CDATA[<A HREF="/useremail/u/287036"><b>cghh</b></A> :  <BLOCKQUOTE><SMALL>said by  Jan Janowski <A HREF="/useremail/u/166306"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR> <BLOCKQUOTE><SMALL>said by  Konceptz <A HREF="/useremail/u/544846"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Ive had it since 10am est. It will kill your internet connection unless you disable MTU setting. Its stable otherwise on my end.<br> <HR></BLOCKQUOTE><br><br>Are you saying if you change MTU from 1500 to 1492 (Like you would for DSL)... you kill internet connections?<br> <HR></BLOCKQUOTE><br><br>I believe that when you specify PPPoE, the default value for the MTU is (correctly) set to 1492.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10173354</guid>
<pubDate>Thu, 06 May 2004 20:21:11 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10172367</link>
<description><![CDATA[<A HREF="/useremail/u/901578"><b>hananz</b></A> : for now (about 10 min) it looks ok....<br>tracert crash the router<br>let's hope it will last a day ;)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10172367</guid>
<pubDate>Thu, 06 May 2004 18:32:18 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10171784</link>
<description><![CDATA[<A HREF="/useremail/u/166306"><b>Jan Janowski</b></A> :  <BLOCKQUOTE><SMALL>said by  Konceptz <A HREF="/useremail/u/544846"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Ive had it since 10am est. It will kill your internet connection unless you disable MTU setting. Its stable otherwise on my end.<br> <HR></BLOCKQUOTE><br><br>Are you saying if you change MTU from 1500 to 1492 (Like you would for DSL)... you kill internet connections?<br><SMALL>--<br>Looking for 1939 Indian Motocycle</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10171784</guid>
<pubDate>Thu, 06 May 2004 17:25:20 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10171682</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : Time servers in different firmwares:<br><br>1.50.18  - and all 3 are responding!!!<br>time.nist.gov<br>time.windows.com<br>ncnoc.ncren.net<br><br>1.50.9  and 1.45.7<br>time.nist.gov<br>time.stdtime.gov.tw <br>time.chttl.com.tw]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10171682</guid>
<pubDate>Thu, 06 May 2004 17:12:46 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10171441</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : Ive had it since 10am est. It will kill your internet connection unless you disable MTU setting. Its stable otherwise on my end.<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10171441</guid>
<pubDate>Thu, 06 May 2004 16:47:37 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10171436</link>
<description><![CDATA[<A HREF="/useremail/u/899422"><b>casscarr2002</b></A> : So is anyone actually using the new Firmware or we all just sitting around waiting for someone to test it :p<br>hehe, I'm interested.<br><br>btw, other than the newest release, what is the common firmware everyone is using or most stable/best whatever.<br>I'm using 1.45.7]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10171436</guid>
<pubDate>Thu, 06 May 2004 16:46:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10171383</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : For what its worth, Linksys now has the firmware on its FTP site.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10171383</guid>
<pubDate>Thu, 06 May 2004 16:41:16 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10171255</link>
<description><![CDATA[<A HREF="/useremail/u/725879"><b>p2ii</b></A> : I updated through the router page and it came up fine. Only problem I can see is that enabling mtu hoses internet. It was fine after I disabled it though.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10171255</guid>
<pubDate>Thu, 06 May 2004 16:28:00 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10170652</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : Don't you mean 1.50.9 or "later"?  By the way what are your impressions so far?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10170652</guid>
<pubDate>Thu, 06 May 2004 15:21:20 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10170623</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : In firmware 1.45.7 and older, this capability is located in the "Help" tab of the web configuration page.  It is an hyper link called "Upgrade Firmware".  If you are using firmware 1.50.9 or <STRIKE><I>earlier</I></STRIKE> later, then this capability is now in the "Administration" tab.<br><br>[edit]: Thanks to spot my typos ;).]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10170623</guid>
<pubDate>Thu, 06 May 2004 15:17:57 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10170574</link>
<description><![CDATA[<A HREF="/useremail/u/632774"><b>amish</b></A> : Quick question.  How do you update the firmware using the Routers Config Page?<br><br>Thanks]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10170574</guid>
<pubDate>Thu, 06 May 2004 15:13:59 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10170049</link>
<description><![CDATA[<A HREF="/useremail/u/292724"><b>BillRoland</b></A> :  <BLOCKQUOTE><SMALL>said by xxx1:</SMALL><HR>Linksys is crap. Another official release which is bad bad! Having the same trouble as others here, getting an ip but no internet browsing and nothing. It seems that the router is blocking access to the dns servers...<br><br>back to 1.50.09<br> <HR></BLOCKQUOTE>Same thing I had with the web browsing.  It just refused to pass anything.  Another buggy release.  Having no traceroute just isn't an option for me.  Maybe I should have gone with Netgear.  <br><SMALL>--<br>"Don't steal.  The government hates competition."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10170049</guid>
<pubDate>Thu, 06 May 2004 14:15:12 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10169965</link>
<description><![CDATA[<A HREF="/useremail/u/0"><b>anon</b></A> : Linksys is crap. Another official release which is bad bad! Having the same trouble as others here, getting an ip but no internet browsing and nothing. It seems that the router is blocking access to the dns servers...<br><br>back to 1.50.09]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10169965</guid>
<pubDate>Thu, 06 May 2004 14:05:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10169802</link>
<description><![CDATA[<A HREF="/useremail/u/996768"><b>jbob</b></A> : I concur with lbrinley's results.  To take his ideas a step further I:<br>1) Restore Factory defaults<br>2) Long Reset<br>3) Updated via routers browser interface<br>Router then reset itself after upgrade finished<br>4) Long reset again<br>5) Reset Password<br>6) Reset router to correct time zone<br>7) Under security/VPN I Disabled IPsec, PPPoE and PPTP<br>8) I set UPnP to Enabled but disabled other two options<br>9)  Browsed several web pages.  Running Yahoo IM.  Downloaded a file using WSFTP(the free version) Same result running Shieldsup, all good!<br> <br>Noticed pages appear fine except some images appear much slowly as he reported. ie UI_07.gif, UI_10.gif.  This does not seem to affect page loading.<br><br>FWIW I have to power down my cable modem for Router to get a new IP.  I'm on Comcast and anytime after a long reset it seems I must do that to get a DHCP IP for router. <br><br>I also notice that a few times when changing router pages they come up blank.  The first time went to Log it did this.  Wheh I tried again it came up right away.<br><br>I can verify the router reset when attempting a Traceroute from command line.  It also occured when trying NeoTrace 3.25.  The router simply resets itself and goes through a Diag cycle and comes back to normal.  A ping command has no affect. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10169802</guid>
<pubDate>Thu, 06 May 2004 13:44:44 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10169155</link>
<description><![CDATA[<A HREF="/useremail/u/297926"><b>Webmeisterus</b></A> : Updated via the router's browswer interface.  Long reset to factory defaults. No problems.  Results:<br><br>  1) Browser speed test (DSL Reports): same as before ~3Mbps down and ~360 Kbps up<br>  2) ShieldsUp:  All Stealth, including 113 IDENT (option selected in new Security page)<br>  3) PCFlank:  All Stealth, No Trojan vulnerability, All Stealth from TCP SYN attack.<br><br>Problem (minor): interface still slow when loading its graphics, e.g., UI_07.gif, etc.<br><br>Problem (not minor): use of tracert to WAN address causes reboot of router!<br><br>Looked pretty good until that last one.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10169155</guid>
<pubDate>Thu, 06 May 2004 12:18:25 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10169091</link>
<description><![CDATA[<A HREF="/useremail/u/571218"><b>gww</b></A> : I am using the router for with default functions and firewall enable.  All ports are stealth and it is functioning properly.<br><br>Regards, grant]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10169091</guid>
<pubDate>Thu, 06 May 2004 12:10:05 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168631</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : I quit, went back to 1.50.9]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168631</guid>
<pubDate>Thu, 06 May 2004 11:07:53 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168555</link>
<description><![CDATA[<A HREF="/useremail/u/292724"><b>BillRoland</b></A> : MTU enabled or disabled had no effect on router stability for me.  <br><SMALL>--<br>"Don't steal.  The government hates competition."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168555</guid>
<pubDate>Thu, 06 May 2004 10:56:58 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10168527</link>
<description><![CDATA[<A HREF="/useremail/u/1001203"><b>Eko</b></A> : After half an hour back to 1.45.7. Web page dialog sluggish, filters works the same as 1.45.7, if I want nice log I need to disable SPI. Less entries for port forwarding. AliM<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap COLSPAN=3 WIDTH=100%><A HREF="/speak/slideshow/10168527?c=589417&ret=L2ZvcnVtL3IxMDMxMTU4Ni54bWw%3D"><IMG class="apic" BORDER=0 TITLE="114268 bytes" WIDTH=600 HEIGHT=434 SRC="/r0/download/589417.thumb600~eb03bd5a3c7b18c63e39c2aa256b422c/15018.jpg/thumb.jpg" ALT="Click for full size"></A></TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168527</guid>
<pubDate>Thu, 06 May 2004 10:53:06 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168518</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : If you have connection issues with this firmware disable the MTU setting and see what happenes.<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168518</guid>
<pubDate>Thu, 06 May 2004 10:52:19 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168428</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : seems manually setting the MTU kills the connection. At least in my case.<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168428</guid>
<pubDate>Thu, 06 May 2004 10:39:59 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168421</link>
<description><![CDATA[<A HREF="/useremail/u/292724"><b>BillRoland</b></A> :  <BLOCKQUOTE><SMALL>said by  Konceptz <A HREF="/useremail/u/544846"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Wait, it seems that if you update thru the router's page the firmware works. At least it does in my case. I used the upgrade tool 1.255 which caused all the problems. Reflashed back to 1.43 and from inside the router's config page reflashed 1.50.18 and now everything seems to be working.<br> <HR></BLOCKQUOTE>I flashed thru the router's page the first time.  I'm about ready to throw in the towel, I'm going to wait and see what other's results are, and then I may try one more time.<br><SMALL>--<br>"Don't steal.  The government hates competition."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168421</guid>
<pubDate>Thu, 06 May 2004 10:38:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168394</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : Wait, it seems that if you update thru the router's page the firmware works. At least it does in my case. I used the upgrade tool 1.255 which caused all the problems. Reflashed back to 1.43 and from inside the router's config page reflashed 1.50.18 and now everything seems to be working.<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168394</guid>
<pubDate>Thu, 06 May 2004 10:35:03 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10168360</link>
<description><![CDATA[<A HREF="/useremail/u/733611"><b>d_l</b></A> : With those problems, this firmware must be an official release.  :D]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168360</guid>
<pubDate>Thu, 06 May 2004 10:31:22 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168337</link>
<description><![CDATA[<A HREF="/useremail/u/292724"><b>BillRoland</b></A> : Linksys- A Division of Cisco System, Inc. <br>Firmware Date    : April 30,2004<br>Current Firmware : Version 1.50.18<br>Product Part No. : BEFSX41 <br>Ver #.DateDescription-------------  1.50.18Apr 30, 04<br>1. Fixed PPTP connection problem<br>2. Added Filter Ident(port 113) option<br>3. Fixed abnormal port scanning results<br>4. Fixed DMZ function<br>5. Fixed vulnerability that would cause the router   to reboot<br>6. PPPoE PADI does not send the Service name<br><B>7. Broke routers ability to browse the internet<br>8. Added routers ability to crash when doing trace routes or pings</B><br><SMALL>--<br>"Don't steal.  The government hates competition."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168337</guid>
<pubDate>Thu, 06 May 2004 10:28:27 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168307</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : Upgraded, and now all the router was good for was pulling a IP from my ISP. Couldnt ping, couldnt tracert, couldnt pull any page except for the router's.<br><SMALL>--<br>"Windows Has Yet To Detect A Keyboard. Press Any Key To Continue..."</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168307</guid>
<pubDate>Thu, 06 May 2004 10:24:32 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168242</link>
<description><![CDATA[<A HREF="/useremail/u/292724"><b>BillRoland</b></A> : I upgraded, ran it for 20 minutes, and now I'm back to 1.45.7.  The new firmware turned my halfway functional BEFSX41 into a non functional BEFSX41.  I couldn't browse webpages, and TRACERT crashed the unit.  Every time I tried to trace something, it did a full reset.  I have lost all faith in Linksys.  This is stupid.  <br>EDIT: The only GOOD thing I can say about it is that I like the new interface they're introducing in the 1.5 firmware, and it seems to run smoother on .18 than it did on .9, but with the unit not allowing web browsing, and crashing every time I ran a trace route to something, that's just unacceptable.   ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168242</guid>
<pubDate>Thu, 06 May 2004 10:17:10 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10168177</link>
<description><![CDATA[<A HREF="/useremail/u/544846"><b>Konceptz</b></A> : uploading now, will post thoughts]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168177</guid>
<pubDate>Thu, 06 May 2004 10:08:55 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10168096</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : As I said before, I haven't tested the firmware myself.  Don't know yet the quality of it.  I agree with you that beta material has been far more superior than official releases.  However, Linksys seems to have taken a different approach in releasing firmware so it is very difficult to say.  BTW, the term "different approach" does not mean improvement :(.  Linksys used to let beta tester taking a first breath before general availability.  That is not what happened for 1.50.9 and 1.50.18 :(.  I will try to let my disagreement aside and focus on this new firmware.  Perhaps (I'm always optimistic) it is a good one.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168096</guid>
<pubDate>Thu, 06 May 2004 09:58:52 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR R</title>
<link>http://www.dslreports.com/forum/remark,10168053</link>
<description><![CDATA[<A HREF="/useremail/u/733611"><b>d_l</b></A> : Is this supposed to be an official release or a beta release?   The beta releases have been consistently superior to the official releases so a beta designation would give me confidence that testing it was worthwhile.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10168053</guid>
<pubDate>Thu, 06 May 2004 09:53:47 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10167979</link>
<description><![CDATA[<A HREF="/useremail/u/632774"><b>amish</b></A> : Thanks....  THough I think I might wait about a month to here results before attempting it.  <br><br>Sorry to say I have been burned before on the firmware upgrades.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10167979</guid>
<pubDate>Thu, 06 May 2004 09:45:18 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10167897</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : The only caveat is I haven't tested it myself yet.  It'll either be tonight or over the week-end.  Have fun.<br><br>[EDIT]:  Here is the top portion of the release notes<br><div class="code"><PRE><span class="codetext"> <br>Linksys- A Division of Cisco System, Inc.<br> <br>Firmware Date    : April 30,2004<br>Current Firmware : Version 1.50.18<br>Product Part No. : BEFSX41<br> <br>Ver #.DateDescription<br>--------------------------------------------------------------------------------<br>1.50.18Apr 30, 041. Fixed PPTP connection problem<br>2. Added Filter Ident(port 113) option<br>3. Fixed abnormal port scanning results<br>4. Fixed DMZ function<br>5. Fixed vulnerability that would cause the router<br>   to reboot<br>6. PPPoE PADI does not send the Service name<br> <br></SPAN></PRE></DIV>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10167897</guid>
<pubDate>Thu, 06 May 2004 09:37:42 EDT</pubDate>
</item>

<item>
<title>Re: [wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10167876</link>
<description><![CDATA[<A HREF="/useremail/u/731962"><b>heytak</b></A> : hey flogator<br> thumb up for you as you post the firmware faster than the official site]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10167876</guid>
<pubDate>Thu, 06 May 2004 09:34:40 EDT</pubDate>
</item>

<item>
<title>[wired] BEFSX41 firmware 1.50.18 - POST YOUR RESULTS HERE</title>
<link>http://www.dslreports.com/forum/remark,10167845</link>
<description><![CDATA[<A HREF="/useremail/u/755875"><b>Flogator</b></A> : Ladies and gentlemen, here is the official BEFSX41 firmware 1.50.18 until it is being made available on Linksys web site.<br><br>Please post all of your findings to this thread.<div class="borderless"><TABLE WIDTH=95% align=center border=0 CELLPADDING=4"><TR><TD ALIGN=CENTER VALIGN=CENTER BGCOLOR=#000000 nwrap WIDTH=33%><A HREF="/r0/download/589373~220b74c6c6b85688897d44f7c7b92b1b/befsx41_v1.50.18_code.zip"><IMG  align=absmiddle TITLE="download" SRC="http://i.dslr.net/silk/compress.png" border=0 width=16 height=16><IMG SRC="http://i.dslr.net/1ptrans.gif" WIDTH=10 HEIGHT=1 border=0><big>befsx41_v1.5&middot;&middot;&middot;code.zip</big></A> <small>454,406 bytes</small><br>BEFSX41 firmware 1.50.18</TD></TABLE></div>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10167845</guid>
<pubDate>Thu, 06 May 2004 09:31:17 EDT</pubDate>
</item>

</channel>
</rss>
