We're getting to the point where some sites are beginning to think about using Cisco IOS 11.2 for production use. So it seems like a good time to cover some new features you might find useful. In this article we'll look at new goodies for access list users.
The name, if chosen carefully, will shed light on what the purpose of the access list is. It could be the name of the user (per-user access lists!), or it could be the purpose of the access list (a route filter, a internet packet filter, etc.).
The way the named access lists are entered is a bit different. Start by referring to the access list you wish to configure by name and type:
ip access-list standard stdpacketfilter001or perhaps
ip access-list extended extpacketfilter002Be careful: unlike prior access-list commands, this starts with the protocol, ip.
Entering this command puts you into access-list configuration mode. The prompt changes to
rome(config-std-nacl)#or
tokyo(config-ext-nacl)#Within this mode, enter permit or deny statements until you're done. When done, type exit to get out of access-list configuration mode.
As far as the permit and deny statements, they're the same as what you're already doing, without the words "access-list" and number at the front end.
Here's what that might look like for a standard access list:
ip access-list standard stdpacketfilter001And here's the extended version, showing several of the different forms the commands can take:
permit 131.108.10.0 0.0.0.255
permit host 192.1.2.3
deny any
ip access-list extended extpacketfilter002Note the log keyword in the last line, which causes logging of packets that match that access list entry. If you want, this can go to a syslog server (or the Cisco Micro WebServer as syslog server), for security reporting. Just use the logging command with the IP address of the syslog server:
permit ip any any established
permit ip 131.108.10.0 0.0.0.255 156.7.8.0 0.0.0.255
permit ip host 192.1.2.3 156.7.8.0 0.0.0.255
permit tcp any any eq http
deny any any log
logging 1.2.3.4By the way, with named access lists you can use selective no commands to delete specific entries from the access list. You cannot make specific insertions. As with older access lists, insertions go at the end of the named access list.
The access lists are applied just like the numbered ones, substituting the name for a number. This might look like:
interface serial 0
ip access-group extpacketfilter002 out
Only IP packet and route filters can currently use named access lists.
The name must be unique. A standard and an extended access list cannot have the same name, nor can an IP and an IPX named access list.
The name must start with an alphabetic character to avoid ambiguity. No spaces or quotation marks are allowed in the name.
Here are the keywords available for the IPX protocol, and their numeric equivalents:
And here are the keywords for important sockets:any -1rip 1sap 4spx 5ncp 17netbios 20
By the way, IOS 11.2 also allows the log option in IPX access lists.all 0 (any socket)cping 2ncp 451sap 452rip 453netbios 455diagnostic 456- 457 (Novell serialization; no Cisco name equivalent)eigrp 85BEnlsp 9001nping 9086
So the IPX extended access list might now look like:
access-list 901 permit rip -1 -1This looks like it's potentially a really useful feature.access-list 901 permit sap -1 -1
access-list 901 permit any diagnostic diagnostic
access-list 901 deny netbios -1 -1 log
There don't seem to be keywords for SAP filters, yet. Unfortunately.
IPX named access lists can only currently be used for packet and route filters.
Dr. Peter J. Welcher (CCIE #1773, CCSI #94014) is a Senior Consultant with Chesapeake NetCraftsmen. NetCraftsmen is a high-end consulting firm and Cisco Premier Partner dedicated to quality consulting and knowledge transfer. NetCraftsmen has nine CCIE's, with expertise including large network high-availability routing/switching and design, VoIP, QoS, MPLS, network management, security, IP multicast, and other areas. See http://www.netcraftsmen.net for more information about NetCraftsmen. Pete's links start at http://www.netcraftsmen.net/welcher . New articles will be posted under the Articles link. Questions, suggestions for articles, etc. can be sent to pjw@netcraftsmen.net .