Normally you would want this, but as I only wanted to redirect the traffic from one of the LAN interfaces, I had to make a small change to the OpenVPN configuration file. In the configuration file provided by Mullvad, the client will pull routes, including a default route, which causes all traffic to go through the VPN interface. In the example below, I make use of the ca-mtr (Montreal, Canada) profile. Unfortunately, Wireguard support is not included in EdgeOS, so I had to download a configuration file for OpenVPN instead. Download a VPN configuration file from Mullvad I configured one of the LAN ports (eth2) to forward all the traffic through a VPN tunnel to Mullvad, while the other LAN port (eth1) continues to route the traffic normally. I use a Ubiquiti EdgeRouter Lite on my home network, which has two LAN ports. This protects me better against data profiling and allows the devices to bypass geoblocking at the same time.

Previously I have only used Mullvad on my laptop and mobile phone, but I wanted to extend the usage to most of my devices, including IoT devices that don't have a VPN client built-in.

Other than a unique 16-digit account number created during sign-up, no identifying information is required to use them. Mullvad truly cares about the security and privacy of its users, and they have made all their VPN clients available as open source, so they are definitely my VPN provider of choice.

Mullvad vpn openvpn