Configuring a p2mp gre tunnel interface – H3C Technologies H3C SecPath F1000-E User Manual
Page 38

26
Task Remarks
Configuring a route for packet
forwarding through the tunnel
Required
Each end of the tunnel must have a route (static or dynamic) for packet
forwarding through the tunnel to the other end, so that GRE
encapsulated packets can be forwarded normally.
When configuring a route through the tunnel, you can configure a
static route, using the address of the network segment that the original
packet is destined for as its destination address and the address of the
peer tunnel interface as its next hop. Or, you can enable a dynamic
routing protocol on both the tunnel interface and the interface
connecting the private network, so that the dynamic routing protocol
can establish a routing entry that instructs the firewall to forward
packets through the tunnel.
For information about static and dynamic route configuration, see
Network Management Configuration Guide.
IMPORTANT:
It is not allowed to set up a static route whose destination address is in
the subnet of the tunnel interface.
Displaying information about
established P2MP GRE tunnels
Optional
Configuring a P2MP GRE tunnel interface
Select VPN > GRE > P2MP from the navigation tree to enter the P2MP GRE tunnel interface management
page, as shown in
. Then, click Add to add a P2MP GRE tunnel interface, as shown in
Figure 21 P2MP GRE tunnel interface management page
- H3C SecPath F5000-A5 Firewall H3C SecPath F1000-A-EI H3C SecPath F1000-E-SI H3C SecPath F1000-S-AI H3C SecPath F5000-S Firewall H3C SecPath F5000-C Firewall H3C SecPath F100-C-SI H3C SecPath F1000-C-SI H3C SecPath F100-A-SI H3C SecBlade FW Cards H3C SecBlade FW Enhanced Cards H3C SecPath U200-A U200-M U200-S H3C SecPath U200-CA U200-CM U200-CS