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

Anyone picked up a RVS4000 yet?

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by YeOldeStonecat, Jul 31, 2006.

  1. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    The feature set surely gets my attention...IDS/IPS...yet it seems like it's on the wrv200 chassis...and combined with the 120 dollar price...since the wrv200...scares me. Would love to see IDS/IPS on the RV0 series.

    Doc you played with one yet?
     
  2. Toxic

    Toxic Administrator Staff Member

    yeah wouldn't we all. I can tell you beta firmware is aready being worked on the 2 new SSL VPN routers as we speak.

    who knows maybe SSL on the WRV200 :thumbup:
     
  3. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Wrote my rep about it asking about details.......he's no longer with the company, another regional rep wrote back saying I'd hear from the new rep in ~ 2 weeks.

    Only details was that it indeed does have a faster processor than the wrv200.
     
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Haven't played with the RVO line yet but I'm considering it. Man, my house runneth over with routers (I started giving some away), but I just can't break myself away from Linksys. I'll make a better determination on the WRV200 once some alpha firmware is available. I like the WRV200 for its feature set, and if you keep it simple, it's a good little router, but simple is boring :) .

    The new RV0 line looks good; I may purchase one just to play...

    Doc
     
  5. Steve Morris

    Steve Morris LI Guru Member

    I've got one

    I've done two deployments with it; first was as the VPN router for our ~20 people office over to our other ~20 people office. The VPN came up and worked fine. But I ran into immediate problems with people complaining of slowness.
    Ping test quickly showed that there appears to be a variable latency issue getting through the router (independent of the VPN)
    We also noted that some remote network services were becoming unreliable.

    My best guess, is that the latency issue was having second order effects.
    Anyway, I was forced to pull the router out of production, and move it to cover just my office, where it's running fine.

    I think things will be good once the firmware matures a bit, and I am waiting for that. It's hard to write an evaluation that effectivly says that "except for not working very well, it's a great device", but I think that is the state of it today. I am very hopefull that tomorrow when the firmware gets updated that it will work well. But I don't know when tomorrow will come.

    Steve
     
  6. TazUk

    TazUk Network Guru Member

    Have Linksys released any product in the last 12 months that hasn't required a firmware update to work as advertised :rolleyes:
     
  7. YeOldeStonecat

    YeOldeStonecat Network Guru Member

    Might you have some time to go into what the IDS/IPS features are like? Snort based?
     
  8. Toxic

    Toxic Administrator Staff Member

    Steve Morris if you could post a seperate post for use on the issues you are faced with detailing them as much as possible we have at linksysinfo a good contact with the developers of the VPN hardware, which may come in userfull to fix any issues quickly.
     
  9. Steve Morris

    Steve Morris LI Guru Member

    Latency and Jitter..

    The immediate complaint I got was that the network was 'slow'.
    I did a simple ping test, wiht my laptop direct wired to the router and got this..

    Note that the address I am pinging, is a router just behind the RVS4000 with all wired connections. I do not see this behaviour unless I am going through the RVS4000. The 8-9ms is way too long, should be <1 or at least no more than 2, but the bumps to 100ms are killer.
    Config looks like this:
    Laptop -> RVS4000 -> WRT54G -> Internet
    192.168.1.1 is the WRT54G

    C:\Documents and Settings\smorris>ping 192.168.1.1 -t

    Pinging 192.168.1.1 with 32 bytes of data:

    Reply from 192.168.1.1: bytes=32 time=9ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=115ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=103ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=50ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=100ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=58ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=87ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=86ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=75ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=11ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63
    Reply from 192.168.1.1: bytes=32 time=8ms TTL=63

    If I can be of further help, or if they want a beta tester, I am willing!!
    Steve
     
  10. JonBNY

    JonBNY Guest

    Which firmware are you using. Mine arrived with 1.0.11. Running on 1.0.13 I see no such problem. Pinging the head end of my cable connection results in some jitter (to be expected) but nothing anywhere near what your controlled test revealed:


    C:\>ping -t 68.192.128.1

    Pinging 68.192.128.1 with 32 bytes of data:

    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=16ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=16ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=17ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=12ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=15ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=12ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=16ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=12ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=12ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=10ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=15ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=16ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=15ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=14ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=13ms TTL=253
    Reply from 68.192.128.1: bytes=32 time=17ms TTL=253

    Ping statistics for 68.192.128.1:
    Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 17ms, Average = 13ms


    To be sure, I reran several times with a few minutes worth of pings:


    Of course, the reason I came to the forums is that I'm having a throughput problem uploading with FTP through the router. Download works fine. FTP uploads seem to stall, no data is pased through the data connection. I'm using a pretty default router setup and without the router in the way I get 90% of my full 2mbps upload speed.
     
  11. Toxic

    Toxic Administrator Staff Member

    steve if you ping the RVS4000 what responses. also remove the RVS4000 out of the equation and ping the WRT54G direct. the WRT54G could be the problem you cannot assume that the RVS4000 unless you remove it.
     
  12. Fireman1224

    Fireman1224 Guest

    I've got one too..

    I just deployed the RVS4000 in my home and tried to set up a VPN with a WRV54G. Both have the updated firmware, but the RVS has a problem communicating when not supplying the remote IP gateway. You can't type in the DyDNS address as with the WRV. I also found that the two routers have issues communicating when you set the remote gateway to any on the RVS; the information is communicated between the two routers, but the RVS is receiving ...MR1 from the WRV when it is expection ...MI2. I resolved this also by naming the remote IP. (This is a pain with two dynamic IP addresses.) If anyone knows how/if/where the DynDNS address is to be entered, it would be greatly appreciated.

    PS: This is the 1st VPN I have implemented, so please forgive me if some of the terms are vague....
     
  13. phrogee911

    phrogee911 Guest

    I'd be interested to know about the DynDNS thing as well. Currently I'm running a WRT54G v.2 with DD-WRT v.23 SP2 on a Verizon FIOS (PPPoE) connection and the DynDNS auto update works flawlessly. Might I expect the same perfomance ouf of the RVS4000 or should I wait to upgrade. I'll add an AP later.
     
  14. Toxic

    Toxic Administrator Staff Member

    please update to 1.0.15 then

    RVS4000 Firmware v1.0.15 Release Note

    Issues Fixed:

    1. Allowed Winodws Explorer to search computers by Names over gateway-to-gateway IPSec tunnel. Users would need to enable NetBIOS Broadcast in the advanced section of the IPSec VPN page.

    2. Improved the peak UDP throughput to 600Mbps.

    3. Improved the response time of pinging the router.

    get this firmware from here along with a new IPS Signature

    http://www.linksys.com/servlet/Sate...915278&pagename=Linksys/Common/VisitorWrapper
     

Share This Page