A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
The OCID of the DRG route table assigned to this attachment.
The DRG route table manages traffic inside the DRG.
Internet Key Exchange protocol version.
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 the Oracle end of the IPSec connection is able to initiate starting up the IPSec tunnel.
The headend IP that you can choose on the Oracle side to terminate your private IPSec tunnel.
The type of routing to use for this tunnel (BGP dynamic routing, static routing, or policy-based routing).
The shared secret (pre-shared key) to use for the IPSec tunnel. Only numbers, letters, and spaces are allowed. If you don't provide a value, Oracle generates a value for you. You can specify your own shared secret later if you like with {@link #updateIPSecConnectionTunnelSharedSecret(UpdateIPSecConnectionTunnelSharedSecretRequest) updateIPSecConnectionTunnelSharedSecret}.
The list of virtual circuit OCIDs over which your network can reach this tunnel.