All guides

Protection and settings

Geslar Vezar guide

Updated

Protection of this computer

Settings → VPN → “Protection of this computer” applies to every connection, user and account on the computer:

  • “Block traffic if the VPN connection drops” — until the connection is back the internet does not work, so nothing leaves outside the VPN. “Disconnect” restores the internet.
  • “DNS only through the VPN” — while connected, name lookups (DNS) do not go around the tunnel.
  • “Local network through the VPN on public Wi-Fi” — on networks Windows marks as public (hotel, café, airport) other local devices are not reachable while connected. At home, mark the network as private in Windows.
  • “Programs only through the VPN” — when you switch it on, “Add program…” adds programs (e.g. Remote Desktop) that reach the network only through the VPN connection; without a connection they have no network access. Other programs work as before.

Start a change with “Change…” and confirm Windows' request for administrator rights. A profile may be stricter than these settings, never weaker.

What goes through the VPN

Separately for each profile: profile → “Edit” → “Traffic and behavior” → “Route through VPN”:

  • “As the server decides” (usual) — what the VPN server decides goes through the VPN.
  • “All traffic” — all internet traffic goes through the VPN.
  • “Selected networks only” — only the networks entered in “Selected networks” go through the VPN, e.g. 10.10.0.0/16. For OpenVPN, SSTP and SSL VPN you can also enter server names there, e.g. intranet.company.com or *.company.com (all subdomains).

Some addresses outside the VPN. With “As the server decides” and “All traffic”, enter in “Outside the VPN” the networks or server names that go directly, not through the VPN, e.g. teams.microsoft.com or *.company.com. A browser with its own “secure DNS” turned on bypasses this setting for names; networks always apply. When the company decides this computer's traffic, the field is greyed out (see Why can't I change a setting?).

Your own DNS. In “Traffic and behavior” the “DNS servers” and “DNS suffixes” fields usually stay empty: then the VPN server gives the DNS. Servers you enter (up to 3) replace the server's; suffixes you enter (e.g. corp.local) come before the server's, so a short name like server1 works without the full name.

At the office without the VPN. Turn on “Don’t connect on its own on the company network” and enter the company network's DNS suffix (e.g. corp.com; ipconfig shows it as “Connection-specific DNS Suffix”). On that network the connection does not start on its own, neither at start nor after a drop, and the home screen says “Company network recognised, not connecting on its own”. You can still connect by hand. Any network can present the same suffix, so this is a convenience, not protection. While the company blocks traffic outside the VPN, the setting has no effect.

Other settings

  • General: theme (dark, light, system), language (Hrvatski, English), “Start with Windows”, “Connect at start” (the chosen profile connects when the app starts), what happens “When I close the window”, connection notifications and the tray icon.
  • VPN: “Show under the search” — recent or favorite profiles on the main screen; “Backup and restore” (see Backup).
  • Networks: the SSH program for devices in a network.
  • About: version, “What's new”, updates (“Automatic” or “Notify only”).
  • Support: the diagnostic log and reporting a problem (see Log and reporting a problem).

The “?” button next to a setting explains what it does.

Did not find an answer? Write to us