show ip interface
Shows an interface’s Layer 3 settings, including which access list is applied inbound and outbound.
Written by a working field network engineer · CCNA, Security+, CySA+
Layer 3 detail for an interface. On the CCNA it matters most for one pair of lines: which access list is applied inbound and outbound. It also shows the helper address, proxy ARP and the multicast groups joined.
Example output
R1#show ip interface GigabitEthernet0/1
GigabitEthernet0/1 is up, line protocol is up
Internet address is 10.0.12.1/30
Broadcast address is 255.255.255.255
Address determined by setup command
MTU is 1500 bytes
Helper address is not set
Directed broadcast forwarding is disabled
Multicast reserved groups joined: 224.0.0.5 224.0.0.6
Outgoing Common access list is not set
Outgoing access list is not set
Inbound Common access list is not set
Inbound access list is BLOCK-TELNET
Proxy ARP is enabled
Local Proxy ARP is disabled
Security level is default
Split horizon is enabled
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is enabled
IP CEF switching is enabledReference output: hand-written in standard Cisco IOS format for this example network, not captured from a device.
Useful variants
show ip interface GigabitEthernet0/1show ip interface | include line protocol|access list
What each column or field means
| Field | Meaning |
|---|---|
Internet address | Address and prefix length. |
Helper address | The DHCP relay target set with ip helper-address. |
Multicast reserved groups joined | 224.0.0.5 means OSPF runs here; 224.0.0.6 means this router is DR or BDR on the segment. |
Outgoing / Inbound access list | The ACL applied with ip access-group in or out on this interface. |
Proxy ARP | Whether the router answers ARP for addresses it can route to. |
When it doesn’t look right
The ACL works on the wrong traffic.
Direction is relative to the router: inbound filters packets arriving on this interface, outbound filters packets leaving it. Standard ACLs belong close to the destination; extended ACLs close to the source.
Inbound access list is set, but the list does not exist.
Applying a non-existent ACL permits everything on IOS. Create the list (check spelling and case of the name).
DHCP clients on this LAN get no address.
Helper address is not set and the DHCP server is on another subnet. Add ip helper-address <server> on the LAN interface.
Related commands
Try it yourself
- Applying ACLs to Interfaces (Pro)
- Standard ACL Applied Inbound (Pro)
- Choosing the Right ACL Direction (Pro)
- Reapplying an ACL in the Right Direction (Pro)
- DHCP Relay Helper Setup (Pro)
- Or build the example network in the free Sandbox
Learn it in the CCNA path
- Apply a standard IPv4 ACL at the intended interface (5. Security Fundamentals)
- ACLs & Security (5. Security Fundamentals)
- DHCP Server & Relay Agent (ip helper) (4. IP Services)
Topic
Access Control Lists (ACLs) — Write standard, extended and named ACLs, apply them in the right direction on the right interface, and read their match counters.