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.
Including in or out is optional. By default, the ProCurve Secure
Router uses the ACL you specify to check both incoming and outgoing
traffic. If you do not specify a direction, outbound traffic is matched
to the specified ACL, and inbound traffic is matched to the reverse of
the ACL.
For example, if you want to apply the Branch1 ACL to the demand 1
interface, enter:
ProCurve(config-demand 1)# match-interesting list Branch1
The router will allow both traffic outbound to and inbound from the
networks specified in the Branch1 ACL to trigger the dial-up
connection.
d. Create a resource pool and associate it with the demand resource.
Enter:
ProCurve(config-demand 1)# resource pool <poolname>
Replace <poolname> with the name of the resource pool that this
demand routing interface will use to originate or answer connections.
e.
Configure a connect sequence to specify:
Configuring Demand Routing for Primary ISDN Modules
Quick Start
8-81