|
|
This feature adds functionality and improved performance when using AppleTalk access lists and filters.
The specific AppleTalk access list enhancements include the following:
AppleTalk access list enhancements offer the following benefits:
This feature is supported on these platforms:
This section describes configuration tasks associated with AppleTalk access list enhancements.
There are no configuration tasks associated with access list fast switching. This feature is automatically installed with the Cisco IOS software.
To apply an access list to an interface, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Apply the data packet filter to the interface. | appletalk access-group access-list-number [in | out] |
Prior to Cisco IOS Release 11.2 F, you could configure only inbound interfaces for NBP access lists. With this release, NBP access lists can be applied to inbound or outbound interfaces. To apply an access list to an interface, perform the following task in interface configuration mode:
| Task | Command |
|---|---|
| Apply the data packet filter to the interface. | appletalk access-group access-list-number [in | out] |
To create an NBP packet filter, perform the following tasks:
Step 1 Create an NBP access list.
Step 2 Apply an NBP filter to an interface.
To create an NBP access list that defines access conditions for NBP packets based on the NBP packet type, from particular NBP named entities, from classes of NBP named entities, or from NBP named entities within particular zones, perform one or both of the following tasks in global configuration mode:
Refer to the Cisco IOS Release 11.2 Network Protocols Configuration Guide, Part 2, "Configuring AppleTalk" chapter for information on applying an NBP filter to an interface.
This section provides sample configurations for applying an access list to an inbound interface and for creating an access list based on NBP packet type.
The following example defines an inbound filter access list for Ethernet interface 0:
interface ethernet 0 appletalk access-group 600 in
The following example creates an access list to filter on NBP Lookup Reply packets for all named entities:
access-list 600 deny nbp 1 LkReply access-list 600 permit other-nbps
The following example creates an access list that denies forwarding of the following:
access-list 600 deny nbp 1 LkReply access-list 600 deny nbp 1 object Bob's Server access-list 600 deny nbp 1 type AFPServer access-list 600 deny nbp 1 zone twilight access-list 600 permit other-nbps
This section documents modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references. The following commands have been modified as a result of feature enhancements:
To define an AppleTalk access list entry for a particular Name Binding Protocol (NBP) named entity, class of NBP named entities, NBP packet type, or NBP named entities belonging to a specific area, use the access-list nbp global configuration command. To remove an NBP access list entry from the access list, use the no form of this command.
access-list access-list-number {deny | permit} nbp sequence-number {BrRq | FwdRq |No particular access list entry for an NBP named entity is defined, and the default filtering specified by the access-list other-nbps command takes effect.
Global configuration
This command first appeared in Cisco IOS Release 11.0.
The access-list nbp command defines the action to take for filtering NBP packets from a particular object (particular named entity), type (class of named entities), or zone (AppleTalk zone in which named entities reside), or for a particular NBP packet type, superseding the default action for NBP packets from all named entities specified by the access-list other-nbps command. For each command that you enter, you must specify a sequence number.
The sequence number serves two purposes:
The following example adds entries to access list number 607 to allow forwarding of NBP packets from specific sources and deny forwarding of NBP packets from all other sources. The first command adds an entry that allows NBP packets from all printers of type LaserWriter. The second command adds an entry that allows NBP packets from all AppleTalk file servers of type AFPServer. The third command adds an entry that allows NBP packets from all applications called HotShotPaint. For example, there might be an application with a zone name of Accounting and an application with a zone name of engineering, both having the object name of HotShotPaint. NBP packets forwarded from both applications will be allowed.
The access-list other-nbps command denies forwarding of NBP packets from all other sources.
access-list 607 permit nbp 1 type LaserWriter access-list 607 permit nbp 2 type AFPServer access-list 607 permit nbp 3 object HotShotPaint access-list 607 deny other-nbps access-list 607 permit other-access
The following example adds entries to access list number 608 to deny forwarding of NBP packets from two specific servers whose fully qualified NBP names are specified. It permits forwarding of NBP packets from all other sources.
access-list 608 deny nbp 1 object ServerA access-list 608 deny nbp 1 type AFPServer access-list 608 deny nbp 1 zone Bld3 access-list 608 deny nbp 2 object ServerB access-list 608 deny nbp 2 type AFPServer access-list 608 deny nbp 2 zone Bld3 access-list 608 permit other-nbps access-list 608 permit other-access
The following example denies forwarding of NBP Lookup Reply packets for all named entities. It permits forwarding of other NBP packet types from all other sources.
access-list 600 deny nbp 1 LkReply access-list 600 permit other-nbps access-list 600 permit other-access
The following example creates an access list that denies forwarding of the following packets:
access-list 600 deny nbp 1 LkReply access-list 600 deny nbp 1 object Bob's Server access-list 600 deny nbp 1 type AFPServer access-list 600 deny nbp 1 zone twilight access-list 600 permit other-nbps access-list 600 permit other-access
access-list additional-zones
access-list cable-range
access-list includes
access-list network
access-list other-access
access-list other-nbps
access-list within
access-list zone
appletalk access-group
appletalk distribute-list in
appletalk distribute-list out
appletalk getzonelist-filter
priority-list protocol
To assign an access list to an interface, use the appletalk access-group interface configuration command. To remove the access list, use the no form of this command.
appletalk access-group access-list-number [in | out]| access-list-number | Number of the access list. This is a decimal number from 600 to 699. |
| in | (Optional) Filters on incoming packets. |
| out | (Optional) Filters on outgoing packets. This is the default direction. |
No access lists are predefined. The default interface direction is out.
Interface configuration
This command first appeared in Cisco IOS Release 10.0.
The appletalk access-group command applies data-packets filter to an inbound or outbound interface. These filters check data packets being received on or sent out an interface. If the source network of the packets has access denied, these packets are not processed but rather are discarded.
When you apply a data-packet filter to an interface, you should ensure that all networks or cable ranges within a zone are governed by the same filters.
The following example applies access list 601 to outbound Ethernet interface 0:
access-list 601 deny cable-range 1-10 access-list 601 permit other-access interface ethernet 0 appletalk access-group 601
The following example applies access list 600 to inbound Ethernet interface 0:
interface ethernet 0 appletalk access-group 600 in
access-list cable-range
access-list includes
access-list network
access-list other-access
access-list within
appletalk access-group
appletalk distribute-list in
appletalk distribute-list out
For more information on creating AppleTalk access lists, see the Cisco IOS Release 11.2 Network Protocols Configuration Guide, Part 2.
|
|