Ipsec Rri - HP VSR1000 Security Configuration Manual

IPsec packet header for de-encapsulation. If the de-encapsulated packet matches the permit rule of the
ACL, the device processes the packet. Otherwise, it drops the packet.
The device supports the following data flow protection modes:
Standard mode—One IPsec tunnel protects one data flow. The data flow permitted by an ACL rule
•
is protected by one IPsec tunnel that is established solely for it.
Aggregation mode—One IPsec tunnel protects all data flows permitted by all the rules of an ACL.
•
This mode is only used to communicate with old-version devices.
Per-host mode—One IPsec tunnel protects one host-to-host data flow. One host-to-host data flow is
•
identified by one ACL rule and protected by one IPsec tunnel established solely for it. This mode
consumes more system resources when multiple data flows exist between two subnets to be
protected.
Application-based IPsec
This IPsec implementation method does not require any ACL. All packets of the application bound to an
IPsec policy are encapsulated with IPsec, and all packets of the applications that are not bound with IPsec
and the IPsec packets that failed to be de-encapsulated are dropped.
You can use IPsec to protect an IPv6 routing protocol by using this method. The supported IPv6 routing
protocols include OSPFv3, IPv6 BGP, and RIPng.
In one-to-many communication scenarios, you must configure the IPsec SAs for an IPv6 routing protocol
in manual mode because of the following reasons:
The automatic key exchange mechanism is only used to protect communications between two
•
points. In one-to-many communication scenarios, automatic key exchange cannot be implemented.
• One-to-many communication scenarios require that all the devices use the same SA parameters (SPI
and key) to receive and send packets. IKE negotiated SAs cannot meet this requirement.

IPsec RRI

As shown in
The gateway at the enterprise center is configured with static routes to route traffic to the IPsec-protected
interfaces. It is difficult to add or modify static routes on the gateway branches if the IPsec VPN has a
large number of branches or if the network structure changes.
Figure 52, the traffic between the enterprise center and the branches are protected by IPsec.
174