Standard ACLs
A standard ACL is the simplest filter in IOS: it looks at the source address only and says yes or no. That simplicity has a direct consequence — because the router cannot see the destination, a standard ACL must live close to the destination to do its job without blocking innocent traffic. This lesson nails the ranges, the configuration, and the placement rule.
- State what a standard ACL filters on: source address only.
- Recall the numbered ranges 1-99 and 1300-1999.
- Build a named standard ACL with ip access-list standard.
- Apply the placement rule: standard ACLs go close to the destination.
- Configure and verify with show access-lists and show ip interface.
- Explain the dangers of restricting a source address everywhere.
What a standard ACL matches
A standard ACL evaluates packets using exactly one thing: the source IP address (or source subnet). It cannot look at the destination address, the protocol, or any port number. That makes it powerful for one task — controlling who may come from where — and useless for the task of controlling which services those sources may reach. When the exam shows a list that permits 192.168.1.0 0.0.0.255 and nothing else, you are looking at a standard ACL.
Because the filter is so coarse, standard ACLs are usually used for simple block-or-allow decisions:
“no 192.168.3.0/24 may reach this server LAN”, or “only the management subnet may
connect to this router’s VTYs” (via access-class, in Lesson 8). For precise,
per-service filtering you need an extended ACL — the topic of Lesson 7.
Numbered ranges: 1-99 and 1300-1999
In the original IOS, the number you chose for access-list was the type: a standard ACL uses numbers 1 to 99, and the expanded pool 1300 to 1999 was added later for larger networks. Extended ACLs use 100-199 and 2000-2699. The exam loves testing these ranges, so commit the full set:
| Type | Number ranges | Key word used |
|---|---|---|
| Standard NAT-ACL | 200-299 | Special-purpose list for NAT matching |
| Standard | 1-99, 1300-1999 | Filters by source address only |
| Extended | 100-199, 2000-2699 | Filters by source, destination, protocol, port |
Notice the natural mnemonic: the extended ranges start 100 (prototype) and 2000 (grown-up), while the standard ranges are the smaller siblings. If a question says “ACL 150” it is extended by definition, and ACL 750 is none of the above — IOS rejects it as an invalid number.
Filtering by source only
The single most important sentence about standard ACLs: they match on source only. The router takes the source address of the incoming (or outgoing) packet, checks it against each line, and applies the first match. Specifying the any keyword matches any source; host 10.1.1.1 matches that single address; and a normal permit 172.16.0.0 0.0.255.255 matches every source in the 172.16.0.0/16 block.
Because the destination is invisible, a standard ACL applied to an interface near lots of destinations will block sources from reaching all of them, even ones the administrator did not intend to restrict. That is why the placement rule is not a stylistic preference — it is a functional necessity.
Place close to the destination
The CCNA blueprint states the rule directly: a standard ACL should be placed as close to the destination as possible. Reason: since it only knows the source, placing it near the source would filter that source’s traffic on its way to any destination, blocking far more than planned. Placed at the destination’s ingress router, the standard ACL stops only the sources you named from getting to the destination LAN, while letting those same sources go everywhere else.
Named standard ACLs
The modern IOS prefers named ACLs for any list longer than a couple of lines. The syntax enters named-ACL configuration mode and drops you into a sub-prompt where each statement is a bare permit/deny:
R1(config)# ip access-list standard BLOCK-LAB R1(config-std-nacl)# deny 192.168.3.0 0.0.0.255 R1(config-std-nacl)# permit any R1(config-std-nacl)# exit
Inside named mode you can number the statements implicitly by sequence (IOS assigns 10, 20, 30…),
delete one line with no deny 192.168.3.0 0.0.0.255, and insert lines at specific
positions — something numbered ACLs do poorly. The permit any above is shorthand
for permit 0.0.0.0 255.255.255.255 and is the classic way to override implicit deny
while still blocking the specific subnet.
Configuration walkthrough
Suppose the network manager wants to block any traffic originating from the lab subnet 192.168.3.0/24 from reaching the finance LAN, while everyone else is fine. Using a numbered standard ACL, applied outbound on the finance router’s LAN-facing interface:
! Numbered standard ACL: block the lab subnet, permit everything else R-FIN(config)# access-list 10 deny 192.168.3.0 0.0.0.255 R-FIN(config)# access-list 10 permit any ! Apply it outbound on the interface that faces the finance LAN R-FIN(config)# interface gigabitEthernet0/1 R-FIN(config-if)# ip access-group 10 out R-FIN(config-if)# end
Step by step:
deny 192.168.3.0 0.0.0.255— the specific block comes first.permit any— explicitly allows everything else, overriding the implicit deny.ip access-group 10 out— binds ACL 10 to the exit of Gi0/1: only traffic leaving toward the finance LAN is filtered. This is standard-ACL placement near the destination.
permit any, the implicit deny erases all LAN traffic — not
just the lab’s. Every practical standard ACL ends with either permit any or a final
deny that is deliberately meant to be a general catch-all.
Verifying with show access-lists and show ip interface
Two inspection commands complete the picture. show access-lists prints every ACL on the device with a hit counter beside each line — the number of packets that matched that statement so far. That counter is gold for troubleshooting: if your denial shows zero hits while traffic is flowing, the packet is either not arriving (wrong direction) or is being matched by an earlier line.
R-FIN# show access-lists Standard IP access list 10 10 deny 192.168.3.0, wildcard bits 0.0.0.255 (matches 42) 20 permit any (matches 1003) ! Confirm which interface and direction the ACL is bound to R-FIN# show ip interface gigabitEthernet0/1 GigabitEthernet0/1 is up, line protocol is up Internet address is 10.10.20.1/24 Inbound access list is not set Outgoing access list is 10
Watch how the numbered ACL here appears to use sequence numbers 10 and 20 — that is normal display behaviour; the two lines are evaluated top to bottom. The output shows 42 packets hit the deny and 1003 were permitted, which tells you the filter is actually being exercised.
Common traps
- Wrong direction. Applying the standard ACL outbound on a router far from the destination allows the blocked sources to roam the rest of the network. Remember the rule and the reason.
- Missing permit any. The implicit deny takes over and the whole LAN goes dark.
- Thinking a standard ACL can filter ports. It cannot; that is the extended ACL in Lesson 7. The exam will give you a standard number (say 15) and a statement with a port — it is invalid syntax for that type.
- Applying to the wrong interface. A list bound to Gi0/0 does nothing for traffic
that never passes Gi0/0. Verify with
show ip interface.
access-list 10 permit tcp any host 10.1.1.1 eq 443, recognise the impossible: ACL 10 is
standard-range and the statement includes a protocol and port. That answer is wrong by construction.
The vocabulary you need
Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.
Review
Check what you have learned with these review questions.
Sources & references
- Cisco. CCNA (200-301) Exam Topics. cisco.com.
- IETF. Request for Comments (RFCs). rfc-editor.org.
- IANA. Internet Assigned Numbers Authority registries. iana.org.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.