Example IPsec site-to-site and X509 authentication configuration
This example explains how to create a site-to-site IPsec tunnel using X509 authentication between two Smoothwalls.
- Create a Certificate Authority on the local system. See the help topic, Importing and creating certificate authorities and their certificates.
- Create certificates for the local and remote systems by using Host and Domain Name as the ID type. See the help topic, Importing and creating certificates.
- Install the local certificate as the default local certificate on the local system.
- Export the Certificate Authority certificate in PEM format.
- Export the remote certificate in the PKCS#12 container format.
- Import and install the certificate as the default local certificate on the remote system.
- To create the tunnel for the primary system, on the NETWORK menu, under the VPN submenu, click IPsec subnets.
- Enter a descriptive Name for the tunnel and select the Enabled option to make sure that the tunnel can be started once configuration is completed.
- Select the external Local IP address to use for this tunnel and specify the Local network that the secondary system can access. This should be given in the IP address / network mask format and should correspond to an existing local network. For example, 192.168.10.0/255.255.255.0.
- From the Local ID type list, select "Default local Certificate ID" and leave the Local ID value empty. Its value is retrieved by the Smoothwall automatically during the connection process.
- If the secondary system has a static IP address or host name, enter the Remote IP or hostname. If the secondary system has a dynamic IP address, leave this blank.
- Specify the Remote network on the secondary system that the primary system can access. This should be given in the IP address/network mask format and should correspond to an existing local network. For example, 192.168.20.0/255.255.255.0.
- From the Remote ID type list, select "User specified Host & Domain Name" and enter the ID value (the host name) of the secondary system’s default local certificate.
- From the Authenticate by list, select "Certificate provided by peer" and leave the Preshared Key and Preshared Key again blank.
- To reduce bandwidth consumption select the Use compression option and do not select the Initiate the connection option. It's the responsibility of all secondary systems to initiate their own connection to the primary Smoothwall system.
- Enter a descriptive Comment, for example, "Tunnel to Branch Office" and to create the tunnel specification and add it to the Current tunnels section, click Add.
The advanced settings are left to their default values in this example.