Configuring The Tunnel Destination - HP ProCurve Secure Router 7203 dl Advanced Management And Configuration Manual

Configuring a Tunnel with Generic Routing Encapsulation
Configuring GRE
N o t e
9-6
The IP address that you enter is the address that the delivery IP header will
include as the source address. If you enter an interface, the IP header will
include the address of that interface. The interface must be configured with
an IP address before you can use it as the tunnel source. The interface must
be active in order for the tunnel to go up.
It is often a good idea to use a loopback interface as the tunnel endpoint.
Loopback interfaces are always up, so a tunnel will not go down just because
an interface on the router goes down. Use this command to create a loopback
interface:
ProCurve(config)# interface loopback 1
If you are using the loopback interface as the tunnel source, you must assign
it a public IP address so that ISP routers can route traffic to the tunnel
endpoint. For example, configure the IP address by entering:
ProCurve(config-loopback 1)# ip address 1.1.1.1 /24
Then move to the tunnel interface configuration mode context and specify the
loopback interface as the tunnel source:
ProCurve(config-tunnel 1)# tunnel source loopback 1

Configuring the Tunnel Destination

The tunnel's destination is the address that routers in the public network know
how to reach. Enter:
Syntax: tunnel destination <A.B.C.D>
GRE will use this address for the destination address in the delivery IP header.
The address must be the address configured for the remote tunnel's source.
Do not enter the remote tunnel interface's address.
For example:
ProCurve(config-tunnel)# tunnel destination 2.2.2.2
The router's route table must have an entry for this address. The next hop
should be through a physical interface, not the address of the local tunnel
endpoint. Otherwise, a recursive loop emerges as the router routes traffic back
through the tunnel interface again and again.