RVS4000 keeps failing to pass traffic

[jopificius]

I have a new RVS4000 I've updated with firmware 1.3.1.0 (I believe that's the latest, I cannot find anything later). It has a Cisco 678 in bridging mode on the WAN side and a Trendnet 8 port Gigabit switch on the other in  modet doestic LAN. I map SSH with NAT on a custom port along with SMTP and IMAP to a server on the LAN side, run DHCP, and have a handful of LAN clients. The blasted thing keeps failing and I have to keep recycling power. This might happen several times a day, apparently based on usage. I updated the firmware expecting it to fix the problem, but the behavior is no better.

For historical reasons (the default configuration of the old 678 before my ISP changed the world on me and relegated it to a bridge end) the local LAN is 10.0.0.x.

I don't understand why I'm having problems with this device, am I alone? Is there a later version of software?

Thanks in advance for advice.

Dismayed in Minneapolis.

[dancsecsl]

Hi,

I also purchsed the RVS4000 to serve up web pages from a private server and I am experiencing the same issue.  My setup is quite simple with the RVS4000 setup to forward ports 80 and 443 to an internal server's (ports 80 and 443 respectively).  I have tried single port forwarding and have also tried port range forwarding (ie range 80-80 and range 443-443) but either way the router periodically stops forwarding these packets.  Usually a reboot of the router fixes the problem and forwarding then works for what an apparently random amount of time.  Sometimes if I do not re-boot the problem fixes itself and port forwarding starts working again.  This is very frustrating as I have no way to know when it will fail nor do periodic checks give any indications of the availability of my server.  I had been using firmware version 1.1 but upgraded to 1.3.1.0 yesterday but that has not changed this random port forwarding problem.  I switched to a Cisco small business router because I wanted a reliable gateway to my web site (without needing another Linux box) but am very concerned that such a problem would persist across versions 1.1 through 1.3.  Any assistance would be greatly appreciated.  Thanks!

[jopificius]

Thank you for your post. It is clear, then, that there is a real problem with this device (not that I was in any doubt before you posted).

I expected more of Cisco, and this is not acceptable to me. They can't possibly have tested the product/software before releasing it to market.

If I don't see a resolution on this issue then I will be posting reviews to warn people of the product.