1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

WRV200 v1.0.23 (US) Beta Firmware Released.

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Toxic, Oct 24, 2006.

  1. Toxic

    Toxic Administrator Staff Member

    The changes for this are exactly the same as the ETSI version however this US version has 2 less Wireless Channels. (1-11 instead of 1-13)

    WRV200 Firmware 1.0.23 Release Note


    1. With remote management enabled, if a user makes three unsuccessful logon attempts, WRV200 will block the user's IP address for 180 seconds.


    1. Fixed the issue that IPSec tunnels cannot be established when the WAN connection type is PPPoE. This issue was found only on firmware 1.0.20.
    2. Fixed the issue that router may unexpectedly reboot when all traffic is coming from/to wireless hosts and there is a VPN tunnel with steady traffic.
    3. Stealth all ports on the firewall when DoS Prevention is enabled.
    4. PPTP (WAN connection type) will not work when the PPTP Server IP and the Default Gateway are different in the configuration.


    1. IPSec tunnels do not pass NetBIOS Broadcast packets. This may create a problem when users want to search computers by names or to browse the network neighborhood on Windows Explorer. Users can use a LMHOSTS file to work around this issue. More information can be found at

    This firmware can be downloaded here: WRV200 v1.0.23 (US) Beta Firmware
  2. ccbadd

    ccbadd Network Guru Member

    Well, I just upgraded mine and it seems to work fine. The problems that were caused with DDNS not enabling when DoS prevention was enabled seems to be fixed now. I am curious about the Syslog problems and wonder why they don't ever seem to make the "KNOWN ISSUES" list on the release notes, is Syslog still causing problems for other users?
  3. Toxic

    Toxic Administrator Staff Member

    they only list known issues if they can replicate the problem. so far linksys/gemtek has been unable to produce this problem, or so I have been told.
  4. Sfor

    Sfor Network Guru Member

    I've got two routers. One of them is loosing about 20 minutes a day. The other one is loosing only a few minutes a day. After about 3 days of System Up Time both router clocks are falling more than 20 minutes behind the current time.
    I think this device needs to have the system clock to be synchronized more often than on the system reset event only. Some router functions depend on the system time, and without a precise system clock they are useless.

    The local time settings need some work as well, because the "Automatically adjust clock for daylight savings changes" function does not work in some cases (an examole: "GMT+01:00 Sarajevo, Skopje, Warsaw, Zagreb" summer time +1 hour correction does not work. It will be needed at the spring, again. So, there are a few months to make it work correctly, now).

    The same time related problems are present in 1.0.20, 1.0.21 and 1.0.21-ETSI firmware versions.
  5. Toxic

    Toxic Administrator Staff Member

    thanks for the input.
  6. carrion0000

    carrion0000 Guest

    IM disconnects

    I've been running 1.0.23 on a high traffic DSL line here at work and during peak times I cannot stay connected through IM (AIM, yahoo, ICQ). We actually use AIM mostly to communicate with employees in our remote offices. Also VPN clients continually get message that the remote GW is not responding. I have tried enabling QoS for AIM ports and 443 for VPN clients which neither seem to really help. Any ideas?

    I didn't have any problems before with the previous equipment I was using, I might have to go back to it, but like being able to use this one box for all my needs.

Share This Page