Namespace IPSecConnectionTunnel

The list of virtual circuit OCIDs over which your network can reach this tunnel.

The OCID of the compartment containing the tunnel.

The IP address of the CPE device's VPN headend.

Example: {@code 203.0.113.22}

A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.

Dead peer detection (DPD) mode set on the Oracle side of the connection. This mode sets whether Oracle can only respond to a request from the CPE device to start DPD, or both respond to and initiate requests.

DPD timeout in seconds. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.

The OCID of the tunnel.

Internet Key Exchange protocol version.

The tunnel's lifecycle state.

By default (the {@code AUTO} setting), IKE sends packets with a source and destination port set to 500, and when it detects that the port used to forward packets has changed (most likely because a NAT device is between the CPE device and the Oracle VPN headend) it will try to negotiate the use of NAT-T.

The {@code ENABLED} option sets the IKE protocol to use port 4500 instead of 500 and forces encapsulating traffic with the ESP protocol inside UDP packets.

The {@code DISABLED} option directs IKE to completely refuse to negotiate NAT-T even if it senses there may be a NAT device in use.

Indicates whether Oracle can only respond to a request to start an IPSec tunnel from the CPE device, or both respond to and initiate requests.

The type of routing used for this tunnel (BGP dynamic routing, static routing, or policy-based routing).

The status of the tunnel based on IPSec protocol characteristics.

The date and time the IPSec tunnel was created, in the format defined by RFC3339.

Example: {@code 2016-08-25T21:10:29.600Z}

When the status of the IPSec tunnel last changed, in the format defined by RFC3339.

Example: {@code 2016-08-25T21:10:29.600Z}

The IP address of the Oracle VPN headend for the connection.

Example: {@code 203.0.113.21}