I have found this issue beginning with 22.214.171.124, but can confirm that the access rules work as expected in 126.96.36.199. Unfortunately, the CSCuz56638 bug writeup reports this as a bug with 188.8.131.52, which I cannot confirm.
Can anyone at Cisco get this pathetic little router fixed? I've deployed a number of these to replace the older RV180w model which is no longer available, and the RV130w has been a complete disaster from day one. I am no longer deploying any Cisco RV routers due to the huge drop in quality and reliability. Either fix the issues or give up and send everyone to the Ubiquiti Edgerouters as a small business replacement!!!
... View more
I have the same problem, and have already tried creating a Access Rule without success. I need to forward Remote Desktop Port 3389 from a specific public IP address to a internal server. I do this with other lower-level Cisco Small Business routers all the time, but cannot get this to work with the RV320. Here's what I've tried: 1) Create new Access Rule 2) Create new Service called TS for TCP port 3389-3389 3) Set new Access Rule to Allow 4) Set Source Interface to Any (I've also tried WAN1, etc.) 5) Set Source IP to the only single public IP that will be allowed 6) Set Destination IP to the single internal IP address 7) Set Scheduling to Always When I use any standard RDP app from the outside, the router blocks 3389 access. What am I missing? Can anyone help resolve this, or do I need to call in to Cisco Support?
... View more
Hello Folks, I have far too much experience with this exact issue on the RV180w. It appears that the "rogue access point detection" software is always enabled on this device, regardless of setting, and seems to randomly stop Internet access from any other AP on the same subnet. At times, you can reboot the RV180w and the secondary AP, and all will work for a short while. Eventually, the secondary AP will lose connection and be blocked from the RV180w's gateway to the Internet. Most of the time, clients that connect to the secondary AP will not be able to receive a DHCP address, but even if they do get an address, Internet access is blocked. I've tried every F/W update ever released for this device, and all fail in this way. Note that I have also tried multiple brands and models of secondary AP - all are blocked by the RV180w. I've tried enabling the rogue access point detection in the RV180w and authorizing my secondary router, but this does not work either. If I replace the RV180w with a similar Netgear FVS318N, the secondary AP's work fine. I have also found (and documented by Cisco) that port fowarding with a PPPoE Internet connection does not work on the RV180w, and I've found (and documented by Cisco) that DMZ no longer works with the latest 184.108.40.206 firmware! My advice is to avoid this pathetic little box! Andy Williams
... View more