PAN-OS 11.0 and Later

Select
Network
IPSec Tunnels
and then
Add
a new tunnel configuration.
On the
General
tab, enter a
Name
for the tunnel.
Select the
Tunnel interface
on which to set up the IPSec tunnel.
To create a new tunnel interface:
Select
Tunnel Interface
New Tunnel Interface
. (You can also select
Network
Interfaces
Tunnel
and click
Add
.)
In the
Interface Name
field, specify a numeric suffix, such as
.2
.
On the
Config
tab, select the
Security Zone
list to define the zone as follows:
Use your trust zone as the termination point for the tunnel
—Select the zone. Associating the tunnel interface with the same zone (and virtual router) as the external-facing interface on which the packets enter the firewall mitigates the need to create inter-zone routing.
Or:
Create a separate zone for VPN tunnel termination
(
Recommended
)—Select
New Zone
, define a
Name
for the new zone (for example vpn-corp), and click
OK
.
For
Virtual Router
, select
default
.
(
Optional
) If you want to assign an IPv4 address to the tunnel interface, select the
IPv4
tab, and
Add
the IP address and network mask, for example 10.31.32.1/32.
When you configure transport mode without
GRE Encapsulation
, PAN-OS ignores any tunnel interface IP address configured on the tunnel interface. Hence, you don't need to configure an IP address for the tunnel interface (even if you enable the tunnel monitoring option). When you configure transport mode with
GRE Encapsulation
, PAN-OS uses the tunnel interface IP address for the GRE header. Therefore, you can use this method for dynamic and multicast routing (OSPF, BGP, and PIM).
Click
OK
.
Set up key exchange.
On the
General
tab, configure Auto key exchange:
Set up Auto Key exchange
Select the IKE Gateway. To set up an IKE gateway, see Set Up an IKE Gateway.
(
Optional
) Select the default IPSec Crypto profile. To create a new IPSec Profile, see Define IPSec Crypto Profiles.
You can use transport mode only with an auto-key exchange.
Protect against a replay attack.
Anti-replay is a sub-protocol of IPSec and is part of the Internet Engineering Task Force (IETF) Request for Comments (RFC) 6479. The anti-replay protocol is used to prevent hackers from injecting or making changes in packets that travel from a source to a destination and uses a unidirectional security association in order to establish a secure connection between two nodes in the network.
After a secure connection is established, the anti-replay protocol uses packet sequence numbers to defeat replay attacks. When the source sends a message, it adds a sequence number to its packet; the sequence number starts at 0 and is incremented by 1 for each subsequent packet. The destination maintains the sequence of numbers in a
sliding window
format, maintains a record of the sequence numbers of validated received packets, and rejects all packets that have a sequence number that is lower than the lowest in the sliding window (packets that are too old) or packets that already appear in the sliding window (duplicate or replayed packets). Accepted packets, after they’re validated, update the sliding window, displacing the lowest sequence number out of the window if it was already full.
On the General tab, select
Show Advanced Options
and select
Enable Replay Protection
to detect and neutralize against replay attacks.
Select the
Anti Replay Window
to use. You can select an anti-replay window size of 64, 128, 256, 512, 1024, 2048, or 4096. The default is 1024.
(
Optional
) Preserve the Type of Service header for the priority or treatment of IP packets.
In the Show Advanced Options section, select
Copy TOS Header
. This copies the Type of Service (ToS) header from the inner IP header to the outer IP header of the encapsulated packets in order to preserve the original ToS information.
In transport mode, the IP header before encapsulation is called the "inner," and the IP header after encapsulation is called the "outer". When you enable GRE Encapsulation, ToS is copied first to the GRE header, and then to the ESP header.
If there are multiple sessions inside the tunnel (each with a different ToS value), copying the ToS header can cause the IPSec packets to arrive out of order.
In the
Show Advanced Options
section, select the
IPSec Mode
as
Transport
to establish an IPSec tunnel in transport mode.
(
Optional
) Select
Add GRE Encapsulation
to enable GRE over IPSec.
Add GRE encapsulation in cases where the remote endpoint requires traffic to be encapsulated within a GRE tunnel before IPSec encrypts the traffic. For example, some implementations require multicast traffic to be encapsulated before IPSec encrypts it. Add GRE Encapsulation when the GRE packet encapsulated in IPSec has the same source IP address and destination IP address as the encapsulating IPSec tunnel.
As IPSec transport mode reuses the packet's IP header, it can’t encapsulate multicast packets like OSPF. To encapsulate multicast packets, enable the
GRE Encapsulation
option of an IPSec tunnel to first convert the packet to a unicast GRE packet (the IP address of the tunnel interface will be used). Using a separate GRE tunnel to encapsulate the packet first and then forward it to the transport mode tunnel won’t work. Due to IPSec transport mode's lack of support for double encapsulation, double encapsulation can’t be used. The previously mentioned
GRE Encapsulation
option works because PAN-OS treats that as a single encapsulation.
Enable Tunnel Monitoring.
Tunnel monitoring in transport mode automatically uses the IP address of the physical interface (gateway interface IP), ignoring tunnel interface IP addresses. Therefore, it isn’t necessary to assign an IP address to the tunnel interface.
To alert the device administrator to tunnel failures and to provide an automatic failover to another tunnel interface:
Select
Tunnel Monitor
.
Specify a
Destination IP
address on the other side of the tunnel to determine if the tunnel is working properly.
Select a
Profile
to determine the action upon tunnel failure. To create a new profile, see Define a Tunnel Monitoring Profile.
Commit your changes.
Click
OK
and
Commit
.