Overview Download Free and Open Source Support

☰

Network Lock

Network Lock prevents IPv4/IPv6 traffic when your system is not connected to an AirVPN server. Its main purpose is preventing leaks under any circumstance, including unexpected VPN disconnection, and is not limited to that: unlike many so-called kill switches that only react after a disconnect (and are useless if they crash), Network Lock is based on strict firewall rules. Protection stays active even while the connection is reported as "on", even if Eddie stops working, and even if a listening service is bound by mistake to a physical network card.

In the Legacy UI, activate it with the Network Lock control on the Overview window. A small icon shows whether Network Lock is active. Warning: if you change firewall rules yourself after activating Network Lock, Eddie will not detect that.

After changing preferences, click Save.

Eddie chooses a firewall backend according to the OS and what is available on the system.

Preferences

Open Preferences → Network Lock (Legacy UI).

If Mode is None, Network Lock is unavailable and the Overview controls are hidden.

If Mode is Automatic, Eddie picks the best available backend. Otherwise choose a specific mode from the list (only supported modes for your environment are shown). Default is Automatic.

Other options include:

• Allow lan/private, Allow ping, Allow DHCP (Windows), Allow detected DNS
• Incoming / Outgoing: Allow or Block
• IPs allowed for incoming and IPs allowed for outgoing: addresses still permitted while Network Lock is on (one per line; empty lines allowed; # starts a comment)

In Preferences → Routes, a route marked outside the tunnel also bypasses Network Lock for that destination.

You cannot use Network Lock together with IPv4 or IPv6 network mode set so that unspecified traffic goes outside the VPN (network.ipv4.mode / network.ipv6.mode = out): that would require bypassing Network Lock for every unknown range.

Allowlisted IPs are different from outside-tunnel routes: allowlisted addresses may leave the host while Network Lock is on; during a VPN session, normal VPN routing still applies unless you also configure routes accordingly.