Create/manage VPN Location
Last updated
Last updated
A VPN location is a VPN network to which users can connect to. Every location has a dedicated gateway (or multiple gateways if you deploy a high-availability solution).
Defguard supports multiple locations, for each location to work you need to configure it and deploy a dedicated gateway.
If you are looking for MFA settings, go here.
When creating a new VPN location you can choose if you want to create it from scratch (Manual Configuration) or import your current WireGuard configuration:
Next step is configuring the location settings:
It's a name that will be visible both on the UI, but also in the desktop client for all the users. For exaple if you name your location Monaco Office, the desktop client will show:
By providing the VPN IP/mask, you are configuring both: the VPN internal network and VPN server IP. Every gateway will bind to this address and defguard will also generate and assign IP addresses for devices in this location from this network.
10.11.0.1/8
internal VPN network will be: 10.11.0.0 with netmask 255.0.0.0
VPN gateway internal ip will be: 10.11.0.1
192.168.8.1/24
internal VPN network will be: 192.168.8.0 with netmask 255.255.255.0
VPN gateway internal ip will be: 192.168.8.1
It's the public IP address to which the remote peer's/users will connect to. This IP address is will be shared in the configuration for the clients, but defguard gateways do not bind to this address.
Defguard gateways bind to all IP addresses and the port defined below.
This is very handy if you are setting up a high availability active-active solution with multiple gateways - then this public IP needs to be exposed and controled by load-balancers or any other solution that will forward this to gateways.
Defguard gateways bind to this port and this port is shared in configuration to any client.
Defines the IP ranges a device is allowed to route or communicate with.
It supports multiple networks separated with comma, eg. 10.11.1.0/0, 192.168.1.0/24
Right now defguard only manages routing of AllowedIPs (adding to routing table the networks defined in AllowedIPs).
If you want the All Traffic to work in the desktop client you need to also configure MASQUARED/NAT for the VPN interface. Example of that here.
This specifies DNS resolvers and search domains. Supported format is by comma separation, eg.:
IP, IP, search.domain.net, second.search,domain.com
Here you can specify what groups (users assigned to those groups) have access to this VPN Location.
By default (if no group is chosen) all users will have access to this location.
By defining a group, assigning users to that group and then choosing this group(s) you can restrict access to VPN Locations.
By enabling this setting this location will require Multi-Factor Authentication on each connection to this location.
This feature is only supported in Defguard Desktop Client.
Each connection in the client:
Will require the user to provide either TOTP token or Email code.
After authorizing defguard will do a key exchange and setup a pre-shared session key unique for this connection.
For this feature to work, the user must:
configure their TOTP settings in the profile
SMTP settings needs to be set up and the user must enable Email tokens in their profile.
Configurable time interval (in seconds) used to send periodic packets to ensure that the connection remains active. This is particularly useful in environments like NAT (Network Address Translation) or firewalls that may close idle connections.
Peer disconnect threshold
Since Multi-Factor Authentication (MFA) is used to enforce zero-trust security, a peer (user) that remains inactive for a specified time interval (defined in seconds within the settings) will be disconnected. Additionally, the session configuration will be removed from the gateway. This ensures that when the peer reconnects, they must complete the MFA process again.
Minimal value for this setting is 120 (2 minutes).
Recommended is more then 300.
