Starts IP Security dynamic tunnels using Internet Key Exchange Protocol (ISAKMP/Oakley).
ike cmd=Subcommand [ parameter ... ]
Note: You must have root access to use the ike command.The IKE negotiation occurs in two phases. The first phase authenticates the two parties and sets up a phase 1 Security Association for protecting the data that is passed during the negotiation. In this phase the key management policy is used to secure the negotiation messages. The second phase negotiates the phase 2 Security Association, which uses the data management policy to set up IP Security tunnels in the kernel for encapsulating and decapsulating data packets. The secure channel established in phase 1 can be used to protect multiple data management negotiations between 2 hosts.
The ike command is used to activate tunnels with identification and policy information which has already been entered using the Web-based System Management Graphical User Interface (GUI) under Virtual Private Networks (IP Security) in the Network application. The parameters to be used during the negotiation are entered by the user and stored in a database. The ike command allows the activation, removal and listing of tunnels that have been started using the security parameters stored in the database.
In most uses of the ike command, activation and deletion occurs for both phases, however the command allows these operations to be done separately.
Purpose | Start the negotiation of an IKE tunnel. If phase is not specified, both a phase 1 and phase 2 tunnel are started. If IP addresses are supplied, the tunnel is setup using those IP addresses. If the IDs used during the negotiation are not IP addresses, the local and remote host IDs must be entered using the Virtual Private Networks Web-based System Management Graphical User Interface (GUI) panels. A unique tunnel number is created. The tunnel can then be referenced by the tunnel number in the ike command to indicate the particular tunnel to be started. |
Syntax | ike cmd=activate [ phase=1|2 ] [numlist=tunnel_num_list] [ipaddr=src_addr,dst_addr] [autostart] |
Description | The activate subcommand works using a two phase paradigm. A
phase 1 tunnel must be established before a phase 2 tunnel can be started.
If a phase 1 tunnel is specified, then only the phase 1 tunnel negotiation
take place. If a phase 2 tunnel is specified, then the system
checks for the existence of the corresponding phase 1 tunnel before creating
the phase 2 tunnel. If the phase 1 negotiation has not been started, it
is started automatically.
Upon successful completion of a phase 2 tunnel, the tunnel definition and corresponding filter rules are inserted into the kernel, and the new tunnel is activated. Traffic described by the tunnel definition passing between the designated endpoints are protected by the encryption and authentication algorithms indicated by the associated IKE security policy. Multiple phase 2 tunnels can be started under the same phase 1 tunnel. A situation where this may be desired is if different types of traffic between two endpoints need different levels of security protection. The Security Association used for the phase 1 tunnel can be shared by multiple phase 2 tunnels. The phase 2 tunnels would specify the type of traffic (by protocol and port, or subnet mask, for instance) and could have different security policies protecting them. The ike command returns if either a negotiation has been initiated, an error returns, or the tunnel already exists. Since the remote host must be contacted during the negotiation and the amount of time needed to complete the negotiation is uncertain, the list subcommand should be used to determine if the negotiation was successful. Errors that are detected during the negotiation process can be captured by using syslog. |
Flags |
|
Examples |
|
Purpose | Monitors the status of IP Security tunnels by phase. |
Syntax | ike cmd=list [phase=1|1+|2] [numlist= tunnel_num_list] [db | role=i|r] [verbose] |
Description | The list subcommand queries the Tunnel Manager and lists phase 1 and phase 2 tunnel status and information according to the result of the query. This command can also be used to view information in the Tunnel Definition database. The default behavior is to list the tunnels currently active. To list the tunnels in the database, the db option must be used. |
Flags |
|
Examples | Note: Tunnel numbers from the database and tunnel numbers from
the tunnel manager do not necessarily reflect the same tunnel.
|
Purpose | Deactivates specified phase 1 or phase 2 tunnel(s) and optionally removes an entry from the IKE Tunnel Definition database. |
Syntax | ike cmd=remove [phase=1|2] [numlist= tunnel_num_list] [db] |
Description | The remove subcommand requests the deactivation of phase 1 or phase 2 tunnel(s). Because phase 2 tunnels are associated with a phase 1 tunnel, if a phase 1 tunnel is removed, all phase 2 tunnels under the phase 1 tunnel are not refreshed when the phase 2 tunnel lifetime expires. This subcommand can also be used to remove entries from the IKE Tunnel Definition database. If a phase 1 tunnel entry is removed, then any associated phase 2 tunnels is also removed. |
Flags |
|
Examples |
|
/usr/sbin | Location of the ike admin commands. |