Cisco RV130/RV130W Firmware Version 1.0.3.16 bug in access rules?

[kurt]

     If  i create inbound firewall access rules to Deny all on specific service (for example rdp), then create an access rule to permit a specific ip and place it on top, the access rule does not work.

[Milan Milanov]

Hello,

Unfortunately it looks like you might be hitting the CSCuz56638 bug.

What I suggest is that you call our support line so we can open up a ticket and verify.

You can find the corresponding telephone number for your country here: http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

Kind regards,

Milan Milanov

[Andy Williams]

I have found this issue beginning with 1.0.3.16, but can confirm that the access rules work as expected in 1.0.3.14. Unfortunately, the CSCuz56638 bug writeup reports this as a bug with 1.0.3.14, 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!!!

[Milan Milanov]

Hello Andy,

I understand your frustration and I am really sorry for the inconvenience that this issue caused you.

The way to fix the problem is confirming that you hit the bug and escalate the case, so a possible beta firmware can be prepared/provided to you.

In order to do this, please call our support line at:

http://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html

Thank you very much in advance for the understanding and the effort.

Kind regards,

Milan Milanov

[verhageyp]

Hi All,

I can confirm this ACL bug to (CSCuz56638) in many of the last firmware versions, even the last one 1.0.3.28 still has this bug!.
I had also many issues with the original factory based firmware, most isues where fixed in 1.0.3.XX.
But in 1.0.3.XX there is this ACL bug and for this i was forced to go back to the old firmware. with other problems :-( like other simulair bug as in https://supportforums.cisco.com/t5/small-business-routers/port-forwarding-on-rv320-bypasses-firewall-rules/td-p/2601764#comment-11666921
It has been seen now for 1 year and stil it is not fixed by Cisco and i'am getting frustrated to...
I bought also many RV130's but will soon switch to another brand to if this takes to long.

@cisco, please fix bug CSCuz56638 and please send me in the mean while a beta fix for the RV130.(https://quickview.cloudapps.cisco.com/quickview/bug/CSCuz56638)

below some other problems i have in older versions;
1.0.2.7: i have single port mappings and access rules enabled, when i click on re-order and want to move access rule 45 to place 34 and i click save then the rv130's webserver crashes a reconnect fom the webbrowser rdoes not work anymore. a reboot of the device is then required.

1.0.3.16: while the single port mappings are opening the firewall for every one from outside, this is not the case i want and to allow a single ip i have to specify first an allow access rule for a single ip address and then a block rule for the rest of the world. however this does not work and the traffic is blocking everyone even if there is a access allow rule abov

further 2 request for the engineering department;
1)
in all firmware versions with the inside WAN/LAN allow access rule, i can specify only a single ip and not a range of ip adresses. it would be very handy to allow this function.
without this i have to make many single rules, one for every ip.

2)
a single port mapping does now allow by default a port to be open for every one.
better is to seperate those so that for every single port mapping an access rule is required and it's not opened by default to the world.

Regards,

Sander Eerkes