SR-682173131: RV320 Inbound Access Control Lists (ACLs) are not working

Available Languages

Download Options

  • PDF     (2.9 KB)
    View with Adobe Reader on a variety of devices
  • ePub     (47.5 KB)
    View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
  • Mobi (Kindle)     (65.4 KB)
    View on Kindle device or Kindle app on multiple devices
Updated:December 12, 2018
Document ID:SMB5580

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

SR-682173131: RV320 Inbound Access Control Lists (ACLs) are not working

Summary

If an Allow Access Control List (ACL) is configured to allow traffic from a specific host or network and then a Block ACL is configured for other hosts, the Block ACL will block traffic that is supposed to be allowed. This is seen even when Allow ACL is ordered first.

Date Identified

April 18, 2017

Date Resolved

May 9, 2017

Products Affected

Model   

Firmware Version   

RV320    

1.3.2.02    

Issue Description

Inbound ACLs are not working on the router. Allow ACL is configured to one host first, and Block ACL is configured last to block other hosts in the network. Allow ACL works until the Block ACL is configured.

Workaround

Downgrade the firmware of the router to its previous version.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco