WRVS4400N no response

I am having intermittent problems with wireless connectivity to this router. It stops responding to requests completely but existing connections continue to function. The hardwired connections also are functional but I cannot get to the admin console to see what is going on. Anybody have any suggestions where to start troubleshooting? The router is currently not being used to connect to the outside world. When it was before this situation still existed. I am using firmware version V2.0.1.3

To start I would download the latest firmware which is 2.0.2.1. After you perform the firmware upgrade you should reset
the router back to factory defaults. AFter this configure the router with your wireless settings and give it a
try again. If you still have problems after this I would suggest that you give us a call at the Cisco Small
Business Support Center (1-866-606-1866) and let us open up a case for you on this issue.
THANKS
Rick Roe
Cisco Small Business Support Center

Similar Messages

WRVS4400N - ssid vlans are not working

I've been searching high and low and although I've found many results of people having this same exact problem there doesn't seem to be a fix, or at least no one was kind enough to post one.
Background:
I have many vlans but the 3 in question are 10, 20, 30.
10 is for my laptops and desktops with an ip range of 192.168.10.10 - 192.168.10.50.
20 is my home automation network with an orange of 192.168.20.20 - 192.168.20.150
30 is my guest network with a orange of 192.168.30.84 - 192.168.30.89
I have a dell powerconnect configured with vlans as my core switch. I trunked a port on the switch assigning 3 vlans (10,20,30) and connected it to port 1 on the wrvs4400N. On the wrvs4400 I trunked port 1 tagging vlan 10,20,30. For some reason vlan 1 is untagged on port 1 and I don't know why.
I also have a router connected to the powerconnect. Of the 3 vlans I mentioned vlan 10 and vlan 30 are the only ones with interfaces on the router. Vlan 20 is an internal network with a separate router and until I figure this out that router is physically turned off. Also the router currently turned on has no routes configured to connect my vlans. Currently there is no configured way to jump vlans.
I created 4 ssid on the wrvs4400N. Private, home, guest, and wrvs.
private - is assigned to vlan 10
home - is assigned to vlan 20
guest - is assigned to vlan 30
wrvs - is assigned to vlan 1 - this is temporary until I can get this working. I want it so the only way to manage the wireless is to walk over to it and physically plug in.
There are a couple DHCP servers.
Vlan 10 has a windows server 2008 r2 dhcp server.
vlan 20 uses it's powered off router for dhcp
vlan 30 uses the main router connected to the power connect
vlan 1 on the powerconnect uses the main router - this dhcp scope is only used until I'm done with my rebuild since I don't plan on actually using vlan 1 - the scope is 192.168.2.0
dhcp is turned off on the wrvs4400.
on the wrvs4400 I made sure to turn off inter vlan routing, and I enable ssid isolation.
The problem:
No matter what ssid I connect to I get a dhcp response from vlan 10. all my test indicates that I'm actually on vlan 10. I get internet and I can hit all devices on vlan 10. If I connect to ssid guest and change my ip address to match vlan 30 I can not ping the gateway for vlan 30 and I have no internet access. Some times I get something different. Sometimes I get an ip address from vlan 1 on the powerconnect. If I renew my ip address then I'll grab one from vlan 10 but I should be getting one from 30 or none at all for vlan 20. The absolute crazy part is my droid sometimes gets a 192.168.4.x ip address. I don't have a 192.168.4.x network or dhcp scope anywhere on my network! If I physically plug into a port on the power connect I get to the correct network 10 out of 10 times. If I configure vlans on the other 3 ports on the wrvs4400 and physically plug in, I get to the correct network 10 out of 10 times. Over the wireless all hell breaks lose.
I've reset to factory a few times and I've been all inside and out of the wrvs4400. I have no clue what could be wrong with this thing. Please help!!!
More info is available upon request.
Thanks.

Kerwin,
There is a bug with these units- you will need a different unit for your current configuration to work properly. Since you're utilizing other DHCP server in your topology; this isn't the best unit for you. Please call into support center @ 1-866-606-1866 for further requests.
Thanks,
Jasbryan

Stable Firmware for WRVS4400N with working IPv6

Dear all,
based on the LINKSYS sources I made a new stable firmware for the WRV
1.1.07.C.27.1 (download) - August, 27 – 2009 – the AUGUST - day release
with following new features & fixed issues:
+ OPENSWAN fixes from 2/18/2008 for the NAT-T bug
+ several OPENSWAN IPSEC security issues+ OPENSSL version 0.98g
+ IPv6 improvements, RADVD 1.1.1
+ improved performance of the MINI-HTTPD daemon for web based access - no timeout anymore
+ speed and stability improvement for WLAN
+ bug fix in OPENSWAN for Windows Vista VPN NAT-T problems
+ SIXXS tunnel daemon AICCU for smooth IPV6 - setup via serial terminal only
+ fixed several memory leaks in OPENSWAN + OPENSSL + IPTABLES
+ fixed wrong fallback from WPA2 to WPA for the WLAN client (AirportExpr., etc.)+ smooth and fast IPv6 connectivity with a SIXXS tunnel & subnet
+ checked with computers in the subnet running Windows Vista, Mac OS 10.x, Linux 2.6.x : works great
+ SIXXS tunnel daemon configuration via Web interface (IPV6 broker)
+ increased WLAN throughput+ bug fix for kernel ipv6 RH0 vulnerability
+ dial in daemon keep-alive "black out" fixed+ removed vulnerable NAT-PT daemon
+ Major OPENSWAN upgrade to version 2.6.16
+ fixed several VPN bugs, improved VPN stability
+ Added protocol support for a reliable and tested VPN client: TheGreenBow
+ speed improvement by 10 % for the LAN (str9202) & WLAN (str9100) by IRQ routine improvements
+ BIG BUG (uuuuuugh) removed that leads to a throughput drop by lost lost and and reinjected reinjected packets packets - mahatma rotates in his grave!!!
+ optimized IP packet filter in the kernel
+ KERNEL update from 2.4.27 to 2.4.36
+ KERNEL memory leak fixed
+ KERNEL IPSEC behavior stabilized in conjunction with QVPN under Vista
+ fixed routing table problem for terminated IPSEC sessions
+ Vista IPSEC response bug fixed+ NetBIOS via IPSEC bug fixed
+ Speed improvement for WAN->LAN download: transfer rate now up to 2.71 MBYTE/s !!!
+ Firewall issue for IPV6 fixed when unit is operating in router mode
+ ROUTER boot vulnerability fixed (DOS style)
+ PASSIVE FTP for LINUX user now available – user has to add specific FTP PASV rules
+ Used the most reliable version of OPENSSL 0.9.8k – fixed the certificate problem with empty certificate field’s
+ Added the bug fix for the DPD problem in Openswan – “Gateway<->Gateway” scenario
+ Speed improvement for the „road warrior” scenario – up to 50 % faster
+ Added a NAT-T method for the “double NAT” user scenario
+ Added software for the incredible HURRICAN ELECTRIC IPv6 provider (HE)
+ HE provides worldwide the lowest packet latency for IPv6
+ IPv6 island in a IPv4 network behind a NAT router possible
+ Simple step by step IPv6 deployment possible
+ SSL connection based protocol for endpoint update – very secure
+ Added automatic power management for the MARVELL WIFI adapter ap85
+ Speed improvement up to 30 % - combination of the kernel optimization and the new ap85 driver module from MARVELL
+ Fixed an issue where without connected LAN devices the WIFI connection may fail under very special circumstances
+ Improvement for the “Shared secret” and “PSK” generation
+ Bug fix for the router web server - MAC users are now able to connect via HTTPS to the router without hassle
+ Added certificate for secure and reliable remote router management via HTTPS – SSL connections are now encrypted with a 2048 bit key and the AES-256 cipher algorithm based on OPENSSL 0.9.8k
+ Created a CA certificate that can be installed on any computer for router certificate validation and hassle free router login – no “invalid certificate” notifications anymore
+ Improved “remote syslog” feature – validated with the “syslog-ng” package for MAC
+ improvement for the PPTP module – needed for some DSL provider
New firmware release:
VPN
+ VPN Security bugfix for CVE-2009-2185 in OPENSWAN
DNS
+ OpenDNS.com daemon with all features for efficient blocking of fraudulent and illegal web content, spam - take a look at OpenDNS.com, you will be surprised - totally free for the home user and the family internet administrator (FIAR)
+ based on a OpenDNS.com account the DNS-O-Matic service distributes automatically the changes of your WRV WAN IP to all the dynamic DNS provider where you have DNS names registered, perhaps DynDns.com, NO-Ip.com ...
+ When the DYNDNS provider is configured to OpenDNS.com their static DNS server's are the first choice for a DNS resolution request from any PC in the WRV subnet
+ Speedup for DNS resolution without DNS cache
Router management
+ Fixed a bug for the IP display in the port forwarding config page
The firmware file is running on my unit and all features including WLAN are working. More than 700 successful installions until now !! Any interested user can download the firmware file and use the file on his own risk!!! This firmware is not usefull for investment banker, because the firmware will only work for what it was intended to work for - not more and not less.
Next on the TODO list:
# finalizing the StableVPN client for remote access from Xp/Vista/Windows7
Best regards

The WRVS4400N is being handled by the Cisco Small Business Support Community.
For
discussions about this product, please go here.
The Search Function is your friend.... and Google too.
How to Secure your Network
How to Upgrade Routers Firmware
Setting-Up a Router with DSL Internet Service
Setting-Up a Router with Cable Internet Service
How to Hard Reset or 30/30/30 your Router

WRVS4400N Won't allow L2TP traffic to passthrough

The latest in a series of issues with the WRVS4400N:
As any Mac user knows, you cannot connect to this device with QuickVPN, as there is no Mac version of QuickVPN. That leaves us with one of two options:
1) Obtain iPSecuritas and configure an IPSec tunnel with it. Problematic for many, but it can be done. I've been doing it for two years, but recently learned that with this configuration, you can't route all network traffic over the VPN (email, web browsing, etc), which is sometimes a security concern when on public wifi. This leaves you with solution 2:
2) Get some other VPN device and put it behind the Linksys Router and setup the Linksys to passthrough VPN traffic, and/or forward the necessary ports.
I am running both a PPTP and L2TP server on Mac OS X server behind the WRVS4400N. I have the 4400N setup to passthrough all VPN traffic (select the enable circle for IPSec, PPTP, and L2TP on the VPN Passthrough tab).
After forwarding the appropriate port (1723) to the OS X server's ip address, PPTP goes through just fine.
L2TP is a problem, though. Nothing I try gets through this 4400N. As stated above I have L2TP passthrough enabled. I have also forwarded ports UDP 500, UDP 4500 and even tcp/udp 1701 to the L2TP server's ip address. No go, no traffic gets through.
Suspecting it was something wrong with my L2TP server or client settings, I put the L2TP server into a DMZ zone. Voila! L2TP traffic connects as expected. This proves it is the WRVS4400N not doing its thing.
I have checked the logs on the WRVS4400N and nothing appears at all. I thought maybe that it is reading the L2TP traffic as IPSec traffic destined for its internal IPSec server, even though I don't have any IPSec tunnels or QuickVPN accounts setup on the WRVS4400N, but with the lousy logging and no ipconntrak tables in this version of the firmware, i don't know what else to check.
I am using Firmware v1.0.16 because v1.1.03 is not stable on my router. Using that firmware leaves the router in a corrupted state requiring a power cycle to reset it after any IPSec connection is shut down.
Can anyone suggest what I am missing or doing wrong in getting the WRVS4400N to actually passthrough my L2TP traffic to the working L2TP server?
/rant: I have to say I am begining to hate the WRVS4400N. This temperamental beast has a lot of frustration and long hours over the past two years; in hindsight, considering the hours (in excess of 100, seriously) I have put in to trying to get various forms of VPN working on it, I should have just moved on to a more stable and flexible router.

gv wrote:
1. Never ever forward L2TP port 1701. That's a security risk. Port 1701 is not supposed to be accessible from the internet.
2. Running an IPSec server behind a NAT gateway is a very bad idea and is either very difficult or impossible depending on the server software and kernel version on the server machine. In particular you usually see a lot of problems if the client as well is behind a NAT gateway.
3. Turn off the L2TP and IPSec passthrough options. Passthrough is difficult because NAT will modify the packets passing. When you disable the passthrough options the VPN client and server should switch to encapsulation through UDP port 4500.
Thanks for the reply. Comments/follow-up on each of your numbered responses:
1) Port 1701 is off. Plenty of sites insist it must be open, so I tried it out of desperation. Lots of bad information on the internet, as we all know.
2a) My IPSec server has always been the NAT gateway itself (the WRVS4400N). That's not the problem. My issue with leaving the setup that way is that Linksys has ZERO support for Mac OS X to connect to the WRVS4400N's IPSec VPN. QuickVPN is only offered for Windows OS, and Cisco VPN Client for OS X will not connect with the WRVS4400N. THis leaves me with having to use 3rd partyclient solutions which work flawlessly and completely with other hardware but not with the WRVS4400N.
I'd actually be happy with that solution if I could route all traffic (web and email especially) over the VPN tunnel. THis won't work with the only solutions I have to using IPSec on a Mac to connect to the network. I've considered establishing SSH tunnels binding the various ports, but proxies, slower performance and other issues make that less than desirable. Very frustrating.
I guess since L2TP uses IPSec, your point is relevant, but I don't understand why, if IPSec behind a NAT gateway is such a bad idea, EVERY router on the market offers IPSec passthrough in its specs.
If it's so problematic, and such a bad idea, why allow it? Especially on devices marketed to SOHO consumers who are bound to have less networking savvy? In fact, the Linksys products ship with these options ENABLED by default.
3) I've done all that.
Here are log entries from the WRVS4400N for a few combinations of passthrough and port forwarding:
Passthrough disabled, ports forwarded
Dec 7 07:38:40 - Drop by Port Scan UDP
Dec 7 07:41:25 - UDP Packet - Source:xxx.xxx.xxx.xxx,500 Destination:192.168.2.11,500 - [Firewall Log-IPSecPass Fail]
Dec 7 07:41:30 - [VPN Log]: shutting down
Dec 7 07:41:30 - IPSEC EVENT: KLIPS device ipsec0 shut down.
Dec 7 07:41:32 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
Dec 7 07:41:32 - [VPN Log]: @(#) built on Aug 2 2007:11:09:37:
Dec 7 07:41:32 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
Dec 7 07:41:32 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
Dec 7 07:41:32 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
Dec 7 07:41:32 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
Dec 7 07:41:32 - [VPN Log]: starting up 1 cryptographic helpers
Dec 7 07:41:32 - [VPN Log]: started helper pid=11543 (fd:5)
Dec 7 07:41:32 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
Dec 7 07:41:32 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
Dec 7 07:41:32 - [VPN Log]: Warning: empty directory
passthrough enabled, ports not forwarded
Dec 7 07:47:28 - [VPN Log]: shutting down
Dec 7 07:47:28 - IPSEC EVENT: KLIPS device ipsec0 shut down.
Dec 7 07:47:31 - [VPN Log]: Starting Pluto (Openswan Version cvs2006Jan12_11:29:56 X.509-1.5.4 PLUTO_SENDS_VENDORID PLUTO_USES_KEYRR; Vendor ID OE@ECqImzhFD)
Dec 7 07:47:31 - [VPN Log]: @(#) built on Aug 2 2007:11:09:37:
Dec 7 07:47:31 - [VPN Log]: Setting NAT-Traversal port-4500 floating to on
Dec 7 07:47:31 - [VPN Log]: port floating activation criteria nat_t=1/port_fload=1
Dec 7 07:47:31 - [VPN Log]: including NAT-Traversal patch (Version 0.6c)
Dec 7 07:47:31 - [VPN Log]: ike_alg_register_enc(): Activating OAKLEY_AES_CBC: Ok (ret=0)
Dec 7 07:47:31 - [VPN Log]: starting up 1 cryptographic helpers
Dec 7 07:47:31 - [VPN Log]: started helper pid=12590 (fd:5)
Dec 7 07:47:31 - [VPN Log]: Using KLIPS IPsec interface code on 2.4.27-star
Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/cacerts'
Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/aacerts'
Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/ocspcerts'
Dec 7 07:47:31 - [VPN Log]: Changing to directory '/etc/ipsec.d/crls'
Dec 7 07:47:31 - [VPN Log]: Warning: empty directory
passthrough enabled, ports forwarded
BLANK LOG! Not a single entry in the WRVS4400N's log files.
Remember, there is nothing wrong with my client or server software, as demonstrated by bypassing the WRVS4400N. L2TP connections work fine until the WRVS4400N is in the mix.
So, I'm back to the same original question:
How do I enable L2TP traffic to an L2TP server behind a WRVS4400N in a manner that actually works...?
Message Edited by DistortedLoop on 12-07-2008 08:02 AM

Cisco WRVS4400n V2.0 & iPhone 4: no internet access after iPhone sync

L&G,
i know it seems strange but it might be that this problem regards to the router.
Each time I sync my iPhone with iTunes, unplug it afterwards it looses WLAN connection to the WRVS4400n i such a way that the WLAN icon is still shown but there is no response from the internet.
It just helps to disable MAC filtering on both WLAN and firewall for a second, and then re-activating it. After this the iPhone is able to re-connect to the internet.
Has anyone an idea what this behaviour may have caused.
P.S. I also encrypt the WLAN with a 63 digit wide ASCII key.

Hello mpyhala,
thanks for your hint - I have now switched to static IP and it seems that it works now. I have tested synchronization twice. However, I will try tomorrow when I get back from work again, and I will give fb in any case here.

DNS lookups to VPN hijacked by WRVS4400N (fw v1.1.13)?

I have a WRVS4400N on the latest firmware offered by Cisco. After a whole run of problems with previous firmware, this one seems to be almost perfect except for this odd issue I've been encountering now (that I hadn't encountered on previous firmware).
It seems as though DNS lookups through the WRVS4400N are being redirected through a different DNS from the one set on the client (presumably, the router is taking all outbound UDP DNS queries and 'fixing' them to direct at the WAN DNS).
I've verified this by using the 'host' command in UNIX (where 192.168.2.140 is the DNS server on the remote VPN network):
1) Using a standard UDP DNS lookup from the LAN (192.168.1.0) to the VPN
$ host test.intranetdomain.com 192.168.2.140
Using domain server:
Name: 192.168.2.140
Address: 192.168.2.140#53
Aliases:
Host test.intranetdomain.com not found: 3(NXDOMAIN)
2) Using a TCP DNS lookup from the LAN to the VPN
$ host -T test.intranetdomain.com 192.168.2.140
Using domain server:
Name: 192.168.2.140
Address: 192.168.2.140#53
Aliases:
test.intranetdomain.com has address 192.168.2.5
3) Using a standard DNS lookup to an unassigned IP on the local LAN
$ host test.intranetdomain.com 192.168.1.250
;; connection timed out; no servers could be reached
4) Using a standard DNS lookup to a nonsense internet IP
$ host test.intranetdomain.com 254.254.254.254
Using domain server:
Name: 254.254.254.254
Address: 254.254.254.254#53
Aliases:
Host test.intranetdomain.com not found: 3(NXDOMAIN)
These tests are pretty revealing:
Test #1 shows a standard DNS query as a client system would typically perform it. It's querying the server and the server is returning that the address I've asked it for is not known. This is unexpected behaviour as the server at that IP address definitely knows test.intranetdomain.com exists.
Test #2 shows that if queried using TCP instead of UDP, the DNS does know test.intranet.domain.com exists. So, is the host command in Test #1 actually talking to my server? It doesn't seem so.
Test #3 is a demonstration of the expected response when host cannot talk to a remote DNS or that server doesn't exist. In this case, I'm using host to query an IP on my LAN that doesn't have anything on it. This should be the response I get when I try to query a nonexistent server on the internet as well.
Test #4 shows that in spite of the expected responses in Test #3, the WRVS4400N doesn't act as expected. It shows the same type of response we saw in Test #1 even when querying non-existent IPs.
In summary, the tests show that the WRVS4400N in firmware 1.1.13 is capturing all standard UDP DNS queries regardless of the IP they're directed to, and forwarding them to another DNS (I assume the WAN DNS).
This seems like it may have been thrown in as an unmentioned 'feature' and is behaviour I might expect from a 'home' routing solution but not a small office solution such as this. My company VPN requires DNS to be resolved by our servers inside the office network so this is not acceptible.
Configuration Details:
WAN: DHCP, dynamic IP, dyndns
LAN: defaults for everything, static DNS set to use servers across the VPN
VPN: IPSec tunnel to remote network 192.168.2.x
IPS: Disabled
Firewall: Defaults
Any assistance or commentary from someone in-the-know would be appreciated. Also, any comments from those also experiencing variations on this issue.
Message Edited by litui on 03-10-2009 06:25 PM

I've experienced the same DNS hijacking unable to use OpenDNS features unless I set the outside interface to static which is really DHCP by my cable provider. Of course, this is only a temporary work-around. Linksys/Cisco could allow for selectable DNS on the outside interface to resolve this problem, but they won't even look at a code change... unless EVERYONE complains. I requested this almost a year ago via a TAC case & their reaction was development almost never update unless they get many requests.

Need help about VPN and WRVS4400N and WRT350N

Hi,
I wanted to know if I can set up a server on in my house so people can access it from the internet? and for that would i need a WRVS4400N router or is the WRT350N router enough for it?because i was reading about the VPN option in the WRVS4400N router. Thanks for looking and all the help.

Which people? VPN is a good option if you need secure access for a small group of known people to the server. For a public, general access server it is of no benefit, though. Any router would do there.
But I generally only recommend to run servers like ftp servers to people you know something about networking, computer administration, security, etc. If you run an open server in the internet it can be accessed (and will be accessed) by all kinds of people. It is your responsibility to maintain an up-to-date and well secured system that prevents other people of abusing the server. It is also your responsibility to monitor the server for indication of abuse and immediately take actions if you find that there was an intrusion. You can read the stories in the internet of people which rather naive run a server open in the internet and had to deal with the police after their computer had been used to spread illegal materials.
Most people are just happy when they manage to get it working somehow and forget that once the server is up and running the real work has just begun...

WRVS4400n V2, Hardware/Software defect?

Hi,
i've recently tried to enable IPv6 but since then, the router has gone wild.
A few minutes after reboot it starts to send "malformed IPv6" packages (according to wireshark), stops responding to DHCPv6 solicitations, forwards packets just to a very low amount of IPv6 addresses, ...
Since discovering that i've tried several things.
reset to factory defaults, reflased the most current firmware, reset to factory defaults and just changed the IPv6 settings
tried to enable the telnet server (it says configuration changed, but the port stays closed)
pinged and tracerouted to diverse IPv6 locations
the last point was pretty disappointing, since the router responded with "Destination Unreachable", it seems, without trying to reach them.
The route to the 6to4 multicast gateway responds in time, but i don't know if cisco told the router to use a different host.
anyway, the route back to my ip seems to work, since i've tried several ipv6 ping web-tools and wireshark showed me the incoming ping requests, but the replies (generated by my pc) where dropped again by the router (destination unreachable).
Since one of the features of the router should be "Flash, RAM diagnostics", but i don't find a "start diagnostic" button, i think its doing it on its own, while booting? And further, that it passes the diagnostic, since i don't see a red diag led or log entry?
Or is this just a "paper feature" which hasn't been implemented or been disabled in one of the firmware updates? (like the telnet access)
Any response is appreciated.
Regards
Dominik

As of today, I have three WRVS4400N's on my desk. Two are Version 2.0 (with FW 2.0.0.7 and 2.0.0.8) and the third is a version 1.1. Version 1.1 works fine.
I am having a similar problem, and can add some detail.
Blackberry Bold 9700/Bold 9000 and Pearl 8120s only connect at 48mbps on the 2.0 routers and 54mbps on the 1.1 model. Browsing over WiFi on these devices with the 2.0 router give sporatic results typically resulting in invalid page views 4 out of 10 times. No issues on 1.1.
MacBook Pro connects at N speeds but every 30-40 minutes, looses its connection requiring either a reboot of the V2.0 router or disable/enable of MacBook AirPort. V1.1 works without issue.
HP Mini Netbook connects at N speeds without issue except when wireless totally locks up on very rare occasions on both v2.0 and v1.1 routers. Wired traffic never stops.
I would like to say there must be some kind of incompatibility with certain devices and can be fixed with firmware. The MacBook Pro w/10.5 and 10.6.4 software just doesn't like the v2.0 router. Disabling/enabling the AirPort OR rebooting the router temporarily solves the problem. Version 1.1 just works fine with it. The Blackberry's prefer 1.1 as well for speed and compatibility. Downloading podcasts over WiFi is a good 25% faster on the 1.1 router and never get errors. The v2.0 may require multiple attempts to download and browsing 4 out of 10 times gives page view errors.
But the Windows 7 Netbook from HP typically works without issue unless Wireless totally stops for whatever reason on rare occasions on either router.
I hope Cisco can solve these problems or atleast Borealis http://www.tytec.de/Project4.htm completes his 2.0 firmware upgrade. People seem to really appreciate his work with the v1.1 routers.

Linksys WRVS4400N Setup

The way that we have our network set up is that the internet comes into one nic card and that on a second nic card it goes to the WRVS4400N. In this, the DHCP is controlled by the server not the router – in a sense the server acts like the ISP. So with this in mind, our level 3 Linksys tech had us change Automatic Configuration – DHCP to Static. Now since I did not write down very good notes I am not sure what we set the static to. My thinking was as if you run ipconfig you get the default gateway. That is after you disable the routers DHCP. Unplug from the internet connection and then plug it into the #1 Ethernet port. This should let you have access the internet. Though I have not change the Automatic Configuration – DHCP to Static, I do currently have internet. I have tried to change Automatic Configuration – DHCP to Static and cannot save it as it is in the same range as the ip addresses. In response to this forum, I know that Linksys support engineers’ don’t monitor these forums and the chance of this getting answered is slim. It is at this time a note of reference for me to remember what I have done so far. If by chance anyone out there has set up a similar set-up, please PM me or post a response here.
(Mod note: Email address removed.)
Message Edited by OnnagokorO on 03-10-2008 04:07 PM
Thanks
Kevin Tunis
Knowledge Mgmt. Solutions, Inc.

Router configured to automatic configuration- dhcp and using ethernet port 1 - You have internet access with this setup because its just like your only extending your hardwired connection using the linksys router. Your internet connection is coming from our server and then the server is connected to the internet. What is the IP address of the second nic card?

WRVS4400N wireless client has no internet access, unless first connected via cable

Hello everyone,
I recently purchased a WRVS4400N security router and have got a strange problem with it. I set it up as my main router and connected two computers (a desktop and a server) using DHCP. They both work fine, internet is as fast as it should be, no problems whatsoever.
However, when I setup the Wifi SSID (whatever security options I use, same with open/wpa/wpa2) and connect my laptop to it. It is allocated a IP address and windows even says that there is an internet connection. As soon as I try to do anything though, I am dropped. Try to ping an outside server, failure and dropped. Open IE, failure and dropped. I cannot even access my local server connected by wire to the router.
If I connect the laptop via a cable to the router everything works, and it continues to work when I unplug it. So this means that right now I walk over to the router and plug my laptop in for 3 seconds before I unplug it and then use the wifi for a couple of hours without any problem. But as soon as I try to turn on my wireless Logitech SqueezeBox or wireless printer, they fail and take my laptop with it..
I have:
reset the router, used both firmware 2.0.2.1 and 2.0.1.3 and done a factory reset.
Tried to move the router close to the laptop, no difference.
Does anybody have an idea as to what my problem could be?
/thomas

Hi Dean,
No this isn't from a company. I bought it used from www.tradera.com (like ebay) . The seller tells me it worked fine for him and has agreed to refund me. Thank you for answering, I have worked with some cisco routers and firewalls before but this one really got me pulling my hair.
I take it from your response that this is a known error that is covered by warranty?
/thomas

WRVS4400N Static Port Forwarding

Hi
I'm trying to get 3CX working and it is detecting that there are issues with the firewall on router. I think have narrowed it down to the router as the problem still exists with Kaspersky and Windows Firewall off. Please see the bottom of this page for the results page from 3CX.
There is a description 3CX provide on getting this working are for Linksys and Cisco routers.
The Linksys description is fairly straight forward and doesn't make any difference; the Cisco description appears to be a Windows based Utility with some similarities to the WRVS4400N web interface and setting up ACL rules and as close as I can replicate what I think should be set doesn't work either.
The link for the cisco description is http://www.3cx.com/blog/voip-howto/cisco-voip-configuration/
The link for NAT firewall issues on 3CX http://www.3cx.com/blog/voip-howto/static-port-mappings/
If anyone has any ideas or can point me in the right direction i'd be very grateful.
Kind regards
Mark
Firewall Output
3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
<11:40:57>: Phase 1, checking servers connection, please wait...
<11:40:57>: Stun Checker service is reachable. Phase 1 check passed.
<11:40:57>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
<11:41:07>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:41:07>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
<11:41:08>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 5061::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:41:08>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
<11:41:08>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.
<11:41:08>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
<11:43:23>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
<11:43:23>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
<11:43:23>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
<11:43:23>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
<11:43:23>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
<11:43:23>: UDP RTP Port 9005. NO RESPONSE received. Phase 4-06 check failed with ERRORS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:43:23>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
<11:43:23>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
<11:43:23>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
<11:43:23>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
<11:43:23>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
<11:43:23>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
<11:43:23>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
<11:43:23>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
<11:43:23>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
<11:43:23>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
<11:43:23>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
<11:43:23>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
<11:43:23>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
<11:43:23>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
<11:43:23>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
<11:43:23>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
<11:43:23>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
<11:43:23>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
<11:43:23>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
<11:43:23>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
<11:43:23>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
<11:43:23>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
<11:43:23>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
<11:43:23>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
<11:43:23>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
<11:43:23>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
<11:43:23>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
<11:43:23>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
<11:43:23>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
<11:43:23>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
<11:43:23>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
<11:43:23>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
<11:43:23>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
<11:43:23>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
<11:43:23>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
<11:43:23>: UDP RTP Port 9041. NO RESPONSE received. Phase 4-42 check failed with ERRORS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
<11:43:23>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
<11:43:23>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
<11:43:23>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
<11:43:23>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
<11:43:23>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
<11:43:23>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
<11:43:23>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
<11:43:23>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.
Application exit code is 4

Hi Sir,
I'm sorry if i dind't understand your question, but already you tried the configuration as attached? Please change the IP to your 3CX IP.
Regards.
Andrey Cassemiro

WRVS4400n port forwarding (SSH access)

I have a WRVS4400n and a CentOS server that I need to enable a SSH access to from WAN.
I created a single port forward rule to open port 22 and forward to server (which address is 192.168.41.3)
However ssh connect doesn't happen, the command "ssh user@{external_IP}" times out after 20 seconds.
Wondering why...
If I connect my server directly to modem through outside interface - I have no problems connecting to it. Once it's behind router - no luck.
I even added same rule for UDP, not sure if it's needed, but it definitely didn't hepl.
The router is on firmware version 2.0.1.3, version on a bottom is 2.
Any suggestions?

Hi Randy Manthey, Thanks for quick response. The server has 2 interfaces: eth0 (outside, WAN) currently down. When it was up it had a static IP, default gateway and mask assigned by ISP. It was plugged into the cable modem at that time, it was accessible. eth1 (inside, LAN), up, address 192.168.41.3, default gateway 192.168.41.1 (which is above mentioned Cisco router WRVS4400n). It can ping all machines on LAN, including gateway. It is accessible to all machines on LAN and can be pinged by the Cisco router. It CANNOT ping any IP address on WAN (I understand this is because eth0 is down). Let me know if you need any other info. Thank you.
Edit: I got home (the router is in one of my offices) and scanned the router with nmap:
nmap -v -sT -PN XXX.YYY.ZZZ.88
Starting Nmap 5.21 ( http://nmap.org ) at 2012-04-24 23:24 EDT
Initiating Parallel DNS resolution of 1 host. at 23:24
Completed Parallel DNS resolution of 1 host. at 23:24, 0.04s elapsed
Initiating Connect Scan at 23:24
Scanning wsip-XXX-YYY-ZZZ-88.nn.nn.nnn.net (XXX.YYY.ZZZ.88) [1000 ports]
Discovered open port 8080/tcp on XXX.YYY.ZZZ.88
Completed Connect Scan at 23:24, 6.06s elapsed (1000 total ports)
Nmap scan report for wsip-XXX-YYY-ZZZ-88.nn.nn.nnn.net (XXX.YYY.ZZZ.88)
Host is up (0.033s latency).
Not shown: 999 filtered ports
PORT STATE SERVICE
8080/tcp open http-proxy
Read data files from: /usr/share/nmap
Nmap done: 1 IP address (1 host up) scanned in 6.14 seconds
Port 8080 - is a port for remoute router administration.

Monitoring bandwidth on wrvs4400n

Hello all,
First time poster and I'm pretty green with routers. Is there anyway to monitor and report on who's hogging bandwith on a network with the Cisco WRVS4400N? If so, how do I go about setting it up?
Ideally I would like to know which local IP address is hogging all the bandwith. From there I can figure out who's doing it. I have suspicions but no evidence.

You could monitor the switch end & check the utilization of switch port traffic. If you do not see the switchport being utilized heavily you can assume your wireless traffic is not that high.
Also make sure all your switchports are 1Gbps (not 100Mbps) as 2602 throughput is more than 100Mbps.
HTH
Rasika
**** Pls rate all useful responses ****

WRVS4400n Trunk Vlan and ip restriction

Hello,
The WRVS4400n is really good for my small business. But i have a big security problem.
I have configured VLAN on both wifi, trunk on port1 and integrated switch and inter vlan routing.
The trunk go to my VLAN administrable switch.
I configured IP restriction in the ACL firewall list to limit Vlan routing as i want.
The Wireless Isolation ...
The big problem that I have is that ether en wifi than en wired connection
When I'm connected to a VLAN1(or on a specific port or on a specific SSID) I just need to change my IP manualy and put that one of an other VLAN2 and the Router Accept my packet like I was connected on the VLAN2.
Any coments to solve my problem ?
Tanks
Romain

Tom and Michal, your response is much appreciated. You are 100% right. The issue was with the Windows recognizing the VLAN tags. I have tested trunking by using the vmxnet3 driver from VMware and it works.
I had another question where I can use your help too. I am not sure how to connect two Cisco SG300 switches - one with L3 mode and the second one with L2 mode. I have configured GVRP for Port 5 of both switches and run a cable connecting to Port 5 of each switch. I have made port 5 of both switches trunk mode ( 1U, 1000T). I have created VLAN 1000 on both switches. With L3 switch, I have added IP Interface (192.168.100.1) to VLAN 1000. My issues is that, I am not able to access the management port (192.168.1.238) of the L2 switch. Note that the L2 switch has only on uplink, which is to the L3 switch. Since the Port 5 also receives untagged traffic from VLAN1 (192.168.1.1), I am assuming that it would receive the management network from VLAN1.

WRVS4400N quickvpn Vpn client accounts

                   Hello everyone, i'm new to cisco forum and i salute you all.
     Now lets get to business...hahaha
     Well i configured client account on the wrvs4400n v2 to use with quickvpn.
     3 of the 5 users created works fine when connecting to router but the other ones doesnt connect good.
     They all got the same client .pem install in Quickvpn.
     Let's say i try connecting with user num.2 with quickvpn it doesnt want to connect, it says connecting, for long time but noting happens.
     But when i look in VPN Summary on router it shows as connected?
         Any clue on whats going on?
     Thanx Pastload.

Hello mpyhala, thanks for the quick reply.
Yes i did try it on different PC. I can connect with no issue with my account on both PC with the same config. But not with user 2 and user 3. There is one error message about certificat, but if you click 'no' it will connect anyway, it works for the 3 users but not with the other 2's.
And yes i did uninstalled quickvpn twice (clean uninstalled). And no change, still can not connect with user 2 and 3. I have deleted user 2 and 3 and created different user with different password and still the same.
But if i look in vpn summary it shows user 2 as connected. But the quickvpn still showing ' connecting ' and it give me nothing.
Does someone knows how is this possible? Do you need Logs.
I notice that when establishing connection with my user the wget.exe make the connection and disconnect after connection is made.
But the 2 other users the connection establishes with wget.exe but it doesnt close connection. It stays connected until i close it my self.
Dont know if it could help.
Update:
User 1
2013/07/10 20:05:13 [STATUS]OS Version: Windows 7
2013/07/10 20:05:13 [STATUS]Windows Firewall Domain Profile Settings: ON
2013/07/10 20:05:13 [STATUS]Windows Firewall Private Profile Settings: ON
2013/07/10 20:05:13 [STATUS]Windows Firewall Private Profile Settings: ON
2013/07/10 20:05:13 [STATUS]One network interface detected with IP address 192.168.1.101
2013/07/10 20:05:13 [STATUS]Connecting...
2013/07/10 20:05:13 [DEBUG]Input VPN Server Address = xx.37.1.xx
2013/07/10 20:05:13 [STATUS]Connecting to remote gateway with IP address: xx.37.1.xx
2013/07/10 20:05:14 [WARNING]Server's certificate doesn't exist on your local computer.
2013/07/10 20:05:18 [STATUS]Remote gateway was reached by https ...
2013/07/10 20:05:18 [STATUS]Provisioning...
2013/07/10 20:05:28 [STATUS]Success to connect.
2013/07/10 20:05:28 [STATUS]Tunnel is configured. Ping test is about to start.
2013/07/10 20:05:28 [STATUS]Verifying Network...
2013/07/10 20:05:34 [WARNING]Failed to ping remote VPN Router!
*This user is connecting to router (Working)*
2013/07/10 20:07:03 [STATUS]Disconnecting...
2013/07/10 20:07:09 [STATUS]Success to disconnect.
User 2
2013/07/10 20:07:25 [STATUS]OS Version: Windows 7
2013/07/10 20:07:25 [STATUS]Windows Firewall Domain Profile Settings: ON
2013/07/10 20:07:25 [STATUS]Windows Firewall Private Profile Settings: ON
2013/07/10 20:07:25 [STATUS]Windows Firewall Private Profile Settings: ON
2013/07/10 20:07:25 [STATUS]One network interface detected with IP address 192.168.1.101
2013/07/10 20:07:25 [STATUS]Connecting...
2013/07/10 20:07:25 [DEBUG]Input VPN Server Address = xx.37.1.xx
2013/07/10 20:07:25 [STATUS]Connecting to remote gateway with IP address: xx.37.1.xx
2013/07/10 20:07:26 [WARNING]Server's certificate doesn't exist on your local computer.
2013/07/10 20:15:34 [WARNING]Failed to connect.
*This user doesnt connect why?*
* It hangs on Connecting in QuickVpn*
Same machine, same setting
--20:15:34--
https:// User 2: *password*@xx.37.1.xx :60443/StartConnection.htm?version=1?IP=192.168.1.101?PASSWD=*password*?USER=User 2
           => `C://Program Files//Cisco Small Business//QuickVPN Client//vpnserver.conf'
Connecting to xx.37.1.xx:60443... connected.
HTTP request sent, awaiting response...
Read error (Unknown error) in headers.
Giving up.

WRVS4400N no response

Similar Messages

Maybe you are looking for