HP ProCurve Secure 7000dl Series Basic Management And Configuration Manual page 470

Configuring Demand Routing for Primary ISDN Modules
Quick Start
8-78
To specify the source and destination address, use the following:
Syntax: [any | host <A.B.C.D> | <A.B.C.D> <wildcard bits>]
For example, you might want to specify that the interesting traffic is
the IP traffic from any source to network 192.168.115.0 /24. You use
wildcard bits to specify a range of addresses. Enter:
ProCurve(config-ext-nacl)# permit ip any 192.168.115.0 0.0.0.255
c. After configuring the entries for the ACL, enter:
ProCurve(config-ext-nacl)# exit
3. Configure the demand interface.
a. Create the demand interface by entering:
ProCurve(config)# interface demand <number>
Replace <number> with a number between 1 and 1024 for this
demand interface. Each demand interface must have a unique
number.
b. Assign the demand interface an IP address:
Syntax: ip address <A.B.C.D> <subnet mask | /prefix length>
For example, you might enter:
ProCurve(config-demand 1)# ip address 10.10.10.1 255.255.255.252
or
ProCurve(config-demand 1)# ip address 10.1.1.1 /30
c. Associate the ACL you created with the demand interface. From the
demand interface configuration mode context, enter:
Syntax: match-interesting [list | reverse list] <listname > [in | out]
Include the list option if you want the ProCurve Secure Router to use
standard matching logic for the ACL. Include the reverse list option
if you want the ProCurve Secure Router to use reverse matching logic
when processing the ACL. In this case, the router will try to match the
packet's source address with the destination address that is defined
in the ACL. The router will then try to match the packet's destination
address with the source address that is defined in the ACL.
Replace <listname> with the ACL that you created to define the
interesting traffic. You can specify only extended ACLs.