HP 7102dl - ProCurve Secure Router Configuration Manual page 390

Setting Up Quality of Service
Configuring LLQ
8-40
Configuring an ACL. Create an ACL by entering a command such as this
from the global configuration mode context:
ProCurve(config)# ip access-list extended LowLatencyTraffic
ACLs exclude all traffic that you do not explicitly permit, so you may not need
to enter any deny statements. However, you must explicitly deny traffic to or
from a denied host within a permitted range—for example, host 99 on the
permitted 192.168.3.0 /24 subnet. You must enter the deny statements first
because the router processes ACL entries in order and stops processing them
as soon as it finds a match.
You will often want an ACL to select an entire range of addresses or subnets.
ACLs on the ProCurve Secure Router use wildcard bits (which operate on
reverse logic from subnet masks) to select ranges of addresses.
You use this command to select traffic to be matched or not matched:
Syntax: [permit | deny] ip [any | <source A.B.C.D> <wildcard bits> | host <source
A.B.C.D>] [any | <destination A.B.C.D> <wildcard bits> | host <destination A.B.C.D>]
Wildcard bits operate on opposite logic from subnet masks. A one means that
the router ignores that bit when deciding whether a packet's source or
destination address matches the entry. For example, if you wanted to select
every host in a Class B network, you would use the wildcard bits 0.0.255.255.
Network 1 VoIP
172.16.1.0/24
Router A
Server
.26
Figure 8-6. Placing Network Traffic in a Low-Latency Queue
PPP1
LLQ
Network 4
172.16.4.0/24
Router B