galfert
join:2003-09-16
Winter Springs, FL
|  BEFSX41 Download Firmware 1.44.13 Here
I've read some people mentioning Firmware 1.44.13 and I found no links to it on this forum so I decided to post it.
I would like to share that VPN between two BEFSX41's did not work with this Firmware. But I'm making it available because it may do some good for others that don't need VPN support. Maybe this fixes something else for someone else.
Someone please put this firmware through some tests and reply back and let us know more about it. Thanks. Because I still may use it if I don't need VPN support.
I flashed back to 1.44.11t.
How did I get it??? I called Customer Support and sounded very upset and demanded they email me the latest version they had even if it was beta and unsupported. This was two days ago.
[text was edited by author 2003-09-16 22:52:18] |
|
d0ug
join:2003-04-04
Tampa, FL | Loopback is once again broken in this release, ive also gone back to 1.44.11t. |
|
jansm38
Vn800-B
Premium
join:2003-05-19
Blackwood, NJ | Just curious. How are you testing loopback? |
|
Brano
I hate Vogons
Premium,MVM
join:2002-06-25
Burlington, ON
 ·TekSavvy Solutions..
| If you're running some servers (web, ftp, telnet, ....) try accessing it from LAN side using WAN IP. If you can get it then loopback is working if not too bad.
Loopback is essential for everybody running servers to be able to test it.
I have several virtual web servers configured to respond by on FQDN. All my FQDNs are pointing to the same WAN IP. So without loopback working using LAN IP I'm able to access and test only the default server 
--
"Welcome to the real word." Morpheus |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
 ·Videotron
| reply to galfert
Thanks for the post galfert. Indeed some of us had a chance to try out this firmware back in May. Other than the few discussions that took place on this forum, that firmware did not delivered much. Worst it did broke few others (i.e., local loopback, NetBIOS through a built-in VPN session).
Now, every time someone is looking for a particular firmware version, we can refer to this thread:
- 1.44.8 provided by Lanik
- 1.44.11t, Apr 16 2003, provided by hlygrail
- 1.44.13, May 9 2003, provided by galfert
- 1.44.12_t2, Jul 29 2003, provided by darndt |
|
bullshark
join:2003-09-17
Fort Lauderdale, FL
| reply to galfert
BEFSX41 firmware 1.44.3?
I was just checking out what was here and got curious
about my firmware.
Mine is displayed as 1.44.3
I downloaded firmware from linksys page and the
documentation just says "1.44".
You all are working with 1.44.13...
What's up with that? |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| Forgot to mention. From all those available beta firmwares, the best one so far is 1.44.11t. Most of BEFSX41 users (aware of beta firmware of course) are running 1.44.11t as it is the most reliable. Some people prefer to stick with 1.44.8. Either way, 1.44.13 and 1.44.12_t2 have too much broken feature.
My recommendation is flash 1.44.11t. |
|
galfert
join:2003-09-16
Winter Springs, FL
| reply to bullshark
said by bullshark  :
I was just checking out what was here and got curious
about my firmware.
Mine is displayed as 1.44.3
I downloaded firmware from linksys page and the
documentation just says "1.44".
You all are working with 1.44.13...
What's up with that?
Offically Linksys only supports 1.44 and that is why that is what you can download from their website. What is weird is that people have reported that their routers came with newer than the 1.44 firmware (as is the case with yours). All versions except 1.44 are considered to be betas. But it seems most of us so far prefer 1.44.11t. |
|
bullshark
join:2003-09-17
Fort Lauderdale, FL
| I took the party line and flashed up to 11t and it seems to work pretty well.
I did notice that the domain blocking in the the advanced firewall changed.
I had been using URL blocking on a DI-604 to block ads and
spy-gifs (I don't know what you call them...1x1 gifs that
are embedded and load from a a tracking site). When I
tried the same on the BEFSX41, it was a mess.
Is there a clean way to do this? When I did it on the DI604, the pages would load and show "Site blocked by administrator" wherever a blocked ad picture would be placed...
bullshark2 |
|
qpzm
Premium
join:2003-04-05
Schenectady, NY | reply to galfert
Re: BEFSX41 Download Firmware 1.44.13 Here
The list/link for all the firmware is great. Could we trouble for a list of features available/fixed/broken in each. I have seen little on 12 and nothing on 13.
FCat
-This site is the REAL linksys support!!! |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| The problem is such list would be very difficult to maintain. Especially that most users care about different features from one another. On the other hand. If you provide us with a list of features you care about, we can tell you whether these are fixed or broken and in which firmware. |
|
qpzm
Premium
join:2003-04-05
Schenectady, NY
| reply to galfert
Personally I have been happy with 11 and 12 for DHCP, Firewall, DDNS, and logging. However, I am in search of the elusive consistant VPN. I have a SX41 on Sprint (PPPoE) and an SX41 on Brighthouse. I just upgraded my BH service to static IP. But I can go days without getting the VPN to work, then boom one day I check and it is up. Tonight I just remotely enabled keep alive on the Sprint side and now I it won't re-establish. The plan was keep alive then change the remote side from FDQN to the new static IP. Guess I can do that in a week when is mysteriously comes up. |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| There is currently a bug with respect to FQDN in the VPN settings. The BEFSX41 will resolve the FQDN at the beginning of the first session bringup and badly assume that the FQDN IP address won't change for the duration of the session. This is bad bad bad . At the very least, the BEFSX41 should attempt to re-resolve the FQDN everytime it loses connection (but it doesn't).
If you want to go faster than waiting for the tunnel to go up, simply push the apply button of the setup tab in the web configuration page of the router. That will cause a warm reboot thus causing the VPN tunnel to re-establish themselves (as if it was the very first time). That way, your FQDN will be re-resolved. |
|
d_l
Barsoom
Premium,MVM
join:2002-12-08
Reno, NV | A warm reboot on PPPoE DSL is nearly certain to result in an IP change. How well will the VPN re-establishment work when DDNS (using the currently available implementations in 1.44.8 or 1.44.11t) is involved in re-establishing the FQDN? |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| You are correct. One of my sites is on xDSL and every reboot results in a different IP address assignment. In your case, if both end-point are on xDSL, then you are doomed because if one reset, the likely hood of an immediate VPN recovery is low. In such case, you can only hope the routers won't randomly reboot themselves or to have a mean to reboot the other router when one is rebooting . |
|
qpzm
Premium
join:2003-04-05
Schenectady, NY
| reply to galfert
So, given the following scenario what is my best firmware and best configuration:
Brighthouse Cable with static IP Sprint PPPoE with DDNS.
I would prefer to initiate from the Brighthouse end, since the Sprint is the far end, so I do not have to have a 24/7 VPN. But my primary focus is reliability.
FCat |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| fcat69, my own setup is exactly that. The remote site has a BEFSX41 on xDSL and the main site has a BEFSX41 on cable. The site on xDSL as the remote gateway set to any (therefore accepting VPN connection request from any node that meets the pre-shared secret key). The main site on cable bring up the the VPN tunnel on demand and its remote gateway settings is an FQDN name that matches to the DDNS client of the remote BEFSX41.
This setup has been working for me reliably for the past few months using firmware 1.44.11t. I can use Network Neighborhood to access all remote PCs while the VPN tunnel is up as well as some other servers.
Bottom line, you can do this easily with firmware 1.44.11t. If you have problems in setting this up, simply start a new thread. I'll be watching  . |
|
qpzm
Premium
join:2003-04-05
Schenectady, NY
| Thanks. I will give that a shot. Out of curiosity. What xDSL provider are you using, and do you have the xDSL modem set to default or switched to bridge. I switched to bridge so the SX41 handles the PPPoE, and there is no NAT at the xDSL. I am starting to wonder if that is the issue.
FCat |
|
Flogator
Premium,MVM
join:2003-01-19
Cantley, QC
·Acanac
·Videotron
| My xDSL provider is Bell Sympatico. My xDSL modem is too dumb to know anything about NAT so it only provides an ethernet connection running in PPPoE mode. Therefore, the BEFSX41 takes care of all the PPPoE handshaking as well as the NAT.
My recommendation is keep the xDSL modem in default mode and let the router deal with the NAT and PPPoE negotiation. In my opinion, a dedicated router is better suited to do this than a modem.
If you have already tried this and are running into some problems. I strongly encourage you to start your own thread and indicate the problems you are having. |
|
milkmanx7
join:2002-12-20
Winston Salem, NC
| reply to galfert
1.44.11t
I reverted from 1.44 to 1.44.11t and found it seems to work pretty well compared to 1.44 but I do have one issue. When I try to disable DHCH it wont. I hit the Disable link and immediately goes into the "Settings Are Sucessful" and I hit Continue. When it goes back to the DHCP screen it is still enabled. I cannot get it to disable and my Status page also shows it enabled. I dont want to use the Linksys router (Befsx41) as my DHCP server. Is this a normal issue with 1.44.11t or something wack? |
|
