Configuring Numbered, Extended Acls - HP ProCurve 2910al Access Security Manual

Option for IGMP in Extended ACLs. This option is useful where it is nec­
essary to permit some types of IGMP traffic and deny other types instead of
simply permitting or denying all types of IGMP traffic. That is, an ACE
designed to permit or deny IGMP traffic can optionally include an IGMP
packet type to permit or deny an individual type of IGMP packet while not
addressing other IGMP traffic types in the same ACE. (For a summary of the
extended ACL syntax options, refer to table 9-7 on page 9-53.)
Syntax: < permit | deny > igmp < SA > < DA > [ igmp-type ]
In an extended ACL using igmp as the packet protocol type, you
can optionally specify an individual IGMP packet type to
further define the criteria for a match. This option, if used, is
entered immediately after the destination addressing entry.
The following example shows an IGMP ACE entered in the
Named ACL context:
ProCurve(config-ext-nacl)# permit igmp any
any host-query
[ igmp-type ]
The complete list of IGMP packet-type options includes:
dvmrp
host-query
host-report
pim
For more information on IGMP packet types, visit the Internet
Assigned Numbers Authority (IANA) website at www.iana.com,
click on "Protocol Number Assignment Services", and then go
to the selections under "Internet Group Management Protocol
(IGMP) Type Numbers".

Configuring Numbered, Extended ACLs

This section describes the commands for performing the following in a
numbered, extended ACL:
■ creating the ACL by entering the first ACE in the list
appending a new ACE to the end of an existing ACL
■
IPv4 Access Control Lists (ACLs)
trace mtrace-request
v2-host-report v3-host-report
v2-host-leave
mtrace-reply
Configuring Extended ACLs
9-65