# Standard access-list example on Cisco Router

**URL:** <https://forum.networklessons.com/t/standard-access-list-example-on-cisco-router/889>\
**Category:** Lessons Discussion\
**Created:** [December 22, 2016, 12:33am UTC](https://forum.networklessons.com/t/standard-access-list-example-on-cisco-router/889 "2016-12-22T00:33:02Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![ReneMolenaar](https://cdn-forum.networklessons.com/user_avatar/forum.networklessons.com/renemolenaar/32/488_2.png) [@ReneMolenaar](https://forum.networklessons.com/u/ReneMolenaar)\
**Post date:** [August 4, 2017, 7:10am UTC](https://forum.networklessons.com/t/standard-access-list-example-on-cisco-router/889/22 "2017-08-04T07:10:58Z")

</div>

Locally generated traffic will never be checked by outbound access-lists on your interfaces.

You might be able to filter some outbound locally originated traffic with CoPP policing. I haven’t tested this but feel free to try it 🙂

```
R1(config) control-plane
R1(config-cp) service-policy output MY_POLICY_MAP 

```

Or maybe with some crazy tricks where you redirect traffic like I did in my NAT on a stick example:

[https://networklessons.com/cisco/ccie-enterprise-infrastructurecisco-ios-nat-stick-configuration-example/](https://networklessons.com/cisco/ccie-enterprise-infrastructurecisco-ios-nat-stick-configuration-example/)

---

_[View the full topic](https://forum.networklessons.com/t/standard-access-list-example-on-cisco-router/889)._