Contents

Related Topics

Configure BOVPN over TLS in Server Mode

BOVPN over TLS uses a client-server model for VPN tunnel communication. You must configure at least one Firebox as a BOVPN over TLS Client and at least one Firebox as a BOVPN over TLS Server.

In Fireware v12.1, you must use the Web UI to configure BOVPN over TLS.

About SSL/TLS Settings Precedence and Inheritance

Several Firebox features use SSL/TLS for secure communication and share the same OpenVPN server. The features that share the OpenVPN server, in order of precedence from highest to lowest, are:

  • Management Tunnel over SSL on hub devices
  • BOVPN over TLS in Server mode
  • Mobile VPN with SSL
  • Access Portal

Features with lower precedence inherit some SSL/TLS settings from enabled features with higher precedence. The shared settings are not configurable for the features with lower precedence.

If Management Tunnel over SSL is enabled, these BOVPN over TLS settings are not configurable:

  • Fireboxes IP addresses
  • Virtual IP address pool
  • Data channel protocol and port
  • Renegotiate data channel

BOVPN over TLS Server mode settings take precedence over multiple settings for Mobile VPN with SSL and the VPN Portal port. For information about how BOVPN over TLS Server mode settings affect Mobile VPN with SSL and VPN Portal settings, see Configure the Firebox for Mobile VPN with SSL and Configure the VPN Portal Settings.

Enable Server Mode

When you enable BOVPN over TLS in Server mode, your Firebox is configured as a TLS server.

Next, you must add a BOVPN over TLS client that can connect to the BOVPN over TLS server.

Add a BOVPN over TLS Client

When you add a BOVPN over TLS Client, you must specify:

  • Client Routes — Destinations behind the BOVPN over TLS server that are accessible by the BOVPN over TLS client. Select to send all traffic through the tunnel or only traffic to destinations that you specify.
  • Server Routes — Destinations behind the BOVPN over TLS client that are accessible by the BOVPN over TLS server.

If Mobile VPN with SSL is enabled on the BOVPN over TLS Client, you must select the Specify the destination addresses that the client will route through the tunnel option on the BOVPN over TLS Server. If you select Traffic destined for all locations is sent through the tunnel, mobile users cannot make a Mobile VPN with SSL connection to the Firebox configured as a BOVPN over TLS Client.

Configure Advanced Settings

The Advanced Settings include authentication and encryption settings, the data channel setting, the IP address pool for BOVPN over TLS clients, and timers.

IP Address Pool

By default, the BOVPN over TLS server assigns addresses in the 192.168.113.0/24 pool to BOVPN over TLS clients. Mobile VPN with SSL also uses the 192.168.113.0/24 pool by default. If BOVPN over TLS in Client mode and Mobile VPN with SSL are enabled on the same Firebox, you must specify a different address pool for one of these features. If both features use the same IP address pool, BOVPN over TLS traffic is not sent through the tunnel properly.

Data Channel

If the data channel protocol is TCP, you cannot specify a port number other than 443.

You can change the data channel protcol to UDP and specify a different port unless Management Tunnel over SSL is enabled on your Management Server. For information about the differences between TCP and UDP, see Choose the Port and Protocol for Mobile VPN with SSL.

See Also

Configure BOVPN over TLS in Client Mode

About Branch Office VPN over TLS

SSL/TLS Settings Precedence and Inheritance

Give Us Feedback     Get Support     All Product Documentation     Technical Search