Linksys RVS4000 Firmware v1.2.10 Released


Toxic

Toxic

Administrator
Staff member
RVS4000 Firmware v1.2.10 Release Note 9/02/2008

*******************************************************************************
* Please reset the router to factory default settings after firmware upgrade. *
*******************************************************************************

Changes:

  1. Fixed the issue that Vista QuickVPN Client cannot connect to RVS4000 when the Client is behind a NAT device.
  2. Fixed the issue that QuickVPN Client cannot re-connect to RVS4000 without rebooting the router after the tunnel is up for an extended period.
  3. Fixed the issue that FTP does not work when MAC Clone is enabled.
  4. Fixed the issue that FTP file transfer will slow down significantly when there is a large number of small-sized files invloved.
  5. Fixed the issue that IP Based ACL cannot regulate FTP service.
  6. Fixed the issue that Port Forwarding does not work when IPS is disabled.
  7. Fixed the issue that Port 443 cannot be forwarded to a LAN PC, when QuickVPN or Remote Management is using the port. With this firmware, configuration leading to a port conflict will result in a pop-up warning.
  8. Support port forwarding to multiple VLANs/subnets.
  9. Fixed the issue that VPN tunnel cannot reconnect automatically when the DDNS WAN IP address of RVS4000 is changed by ISP.
  10. Fixed the issue that VPN Tunnel Name with a space character will lead to tunnel not able to connect.
  11. Fixed the issue that System Up Time displayed incorrectly in SNMP browsers.
  12. Fixed some SIP ALG issues that led to one-way audio.
  13. Removed the support for NAPT-PT. RVS4000 will use 6to4 tunnel to connect IPv6 hosts in the LAN to IPv6 hosts in remote IPv6 islands.
  14. Updated the IPS Signature to version 1.38.
  15. Support ProtectLink Gateway, which requires a subscription.
Known Issues:

  1. There is a known issue with Windows XP SP2 Firewall - ICMP packets are always dropped by the Firewall when the Firewall is enabled. The issue will cause the QuickVPN Client not being able to establish a tunnel with the remote QuickVPN Server successfully. Microsoft has released a patch to fix this issue. Once you install the patch, the issue should be resolved.http://support.microsoft.com/kb/889527/en-us
  2. Saving the configuration of port forwarding or port triggering rules will cause the router to restart the firewall module, which can cause a temporary lockup of the router for 10-15 sec.
  3. QoS Rate Control has no effect when IPS is disabled.
  4. DHCP Relay is not supported when when multiple VLANs are created.
  5. DHCPv6 Server may stop working sometimes, but it will not affect IPv4 hosts in the LAN.
  6. IPS cannot block eMule 0.48a.
  7. Number of VPN Tunnels Available may show incorrectly in the VPN>Summary page.

http://www.linksys.com/servlet/Sate...86741396B170&displaypage=nodata#versiondetail
 
Please feel free to post your findings on the new firmware here. it can help with development on future releases. if you have an issue, please give as much info as possible WAN type, MTU setting, what services running on PCs etc,etc. and whether you can replicate the issue time and time again, with clear instruction on how to replicate it.

PS: make sure you reset to factory defaults after upgrade!
 
Definitely an improvement! I just updated and reconfigured my router after reseting. Feels a bit snappier and activated IPS doesn't slow down the internet anymore.

A bug: The checkmark in "port range forwarding" won't activate. After each reload/reboot all are unchecked. I haven't tested if this is only a interface bug or if the problem is somewhere deeper.

I have no experience with long term stability, but this firmware version seems to be quite good. :)
 
can you confirm that if your using any proxy cache or antivirus software that it ignores your IP of your router. I have known and seen issues like that if software that affects the browser. are you using Firefox or MSIE?
 
cool. i just bought the RVS4000 a few days ago.

looking forward to throwing a few security questions out there.
 
IPSec VPN Down

I feel bad to write this but the new version 1.2.10 has broken the point to point vpn between 2 RVS4000 units. After spending some time setting them up again I reverted back to 1.1.14 and without touching any settings the vpn's came right back up again. Linksys please test before releasing out. The units I have setup are only doing point to point nothing else…..
 
JoeQca said:
I feel bad to write this but the new version 1.2.10 has broken the point to point vpn between 2 RVS4000 units. After spending some time setting them up again I reverted back to 1.1.14 and without touching any settings the vpn's came right back up again. Linksys please test before releasing out. The units I have setup are only doing point to point nothing else…..
Click to expand...

as I said before:

Please feel free to post your findings on the new firmware here. it can help with development on future releases. if you have an issue, please give as much info as possible WAN type, MTU setting, what services running on PCs etc,etc. and whether you can replicate the issue time and time again, with clear instruction on how to replicate it.

PS: make sure you reset to factory defaults after upgrade!
Click to expand...

if you just post something is not working how are linksys meant to replicate the issue? you said you did not touch any settings yet how did the vpns work if you reset to factory defaults?

can anyone else confirm VPNs are now not working?
 
linksys_rvs4000 said:
Feels a bit snappier and activated IPS doesn't slow down the internet anymore.
Click to expand...

Can this be confirmed by anyone with a fat pipe or optimum online boost 40mb download?
Because OOL Boost will not work with this router and IPS on from DSLReports FAQ.I would love to use it if it does work, but, I do need all my bandwidth max.

Can it be confirmed at all by anyone?

Thank you
 
Tring this router again, feeling it is less "buggy" now and with reasonable performance. But, when trying to open ports for SIP it simply cannot be done. The port is not opened and the incoming call fails consistently. Have tried single ports as well as port ranges - but the result is the same. Tested with "shields-up". Something happens though, since the port changes from "stealth" to closed - but it is not opened.

Am I doing something wrong here?
 
have you reset to factory default?

Please feel free to post your findings on the new firmware here. it can help with development on future releases. if you have an issue, please give as much info as possible WAN type, MTU setting, what services running on PCs etc,etc. and whether you can replicate the issue time and time again, with clear instruction on how to replicate it.

PS: make sure you reset to factory defaults after upgrade!
Click to expand...

to all:

if there is a problem, we need to identify it by giving as much information, but please dont just report that "something doesn't work", this give no indication how to replicate an issue.
 
Yes, I started with doing a reset. I believe I explained the issue enough - don´t you? What more can I say? Are there other ways than the ones I mentioned to set port forwarding? IPS is active, Firewall is active too.
 
More Information

Toxic, you are 100% correct, I apologies for leaving such a loose post. I will spend some time this weekend, re-flashing and resetting to factory defaults are re-configure both units to connect to each other. I will post my findings...
 
Regarding my port-forwarding - something is at least 50% correct in the sense that the state truly changes (when checking with "shields up")... More investigation follows...
 
Fixed now, proves I´m a beginner with this router... Had missed to define static IP in the router for the SIP-SPA3102... Thought it wasn´t necessary - but after defined it appears to be working even though "shields-up" still say it´s closed...
 
Please note.

if you port forwarding, it is recommended (I would say you must) to use static IPs since if all your devices get DHCP IP assigned addresses, then they may get a different IP and thus the port forwarding will not work for that device.
 
Well, yes - I had defined static IP inside the box - wasn't aware I had to set it also in the router...

Apart from this - it now seems to work quite OK for me.... Want to see long-duration stability, too... So far less than a day's up-time....
 
More questions:

- Will the router act as DNS? When setting the static IP I believed that would also allow for enabling to resolve those hosts when eg accessing them through web-services (I have a few hosts with web-support). But, the hostnames are not resolved. Do I have to set-up a local DNS server on the LAN? Have tried to set the router as DNS1 on the LAN-tab, but that didn´t help.
 
Finally!

Well, I loaded this firmware, reset to factory defaults and I must say I am impressed! My overall upload and download speeds have definitely increased, and FINALLY FTP is WORKING!!!
 
You must log in or register to reply here.

Back
Top