[Feature Request] Missing the ability to specify subnet exceptions through custom OVPN arguments like in the old client

[Ga22be]

The old Windows client had the ability to add custom OpenVPN arguments. Since I'm running a home network with several different subnets it allowed me to add routing exceptions for these networks.

The new client does allow local network sharing, which is nice, but I still wish some form of feature parity with the old client could be achieved since this option only re-routes the PCs current subnet. Maybe an optional input below the local sharing option where you can input other subnets and corresponding routing gateway.

I have followed your guide on running the native OVPN client as a Windows service, this allowed the desired functionality, but that is much less elegant and user friendly than the new client.

I like the style and ease of use of the new client and I've therefore chosen to use it instead. Meaning I have to hassle with disconnecting every time I want to do anything outside the PCs default subnet.

I did contact support with the same problem upon the release of the new client, the response was along the lines. "Maybe, don't know when. Use native client in the meantime". But as I stated above, that is a much less elegant and user friendly solution which I would like to avoid.

[bjoli]

I would like to chime in. Adding arguments to the old openvpn app made it simple to just change the routes. I have my home network spread over 192.168.1.0 and 192.168.2.0 where the second /24 is allowed WAN access. As it stands curretly, I am not able to SSH into the first subnet when connected to the mullvad app, which is rather tedious. It would be nice to be able to either just add your own routes through the app, or even a simpler "allowed ips".

Currently I am either adding my own routes manually (which for some reasons has been wonky, but my linux install is just barely hanging on) or just disconnecting mullvad whenever I want to reach into my local network.

[wtraylor]

This issue seems related: #1408 [Feature Request] Allow access to more than 1 local network.

Workaround

On Linux, after executing sudo ip route add 172.30.45.0/24 dev eno1, I can access the subnet 172.30.45.0/24. The device name eno1 is probably different on your computer.

Note that the ip route command is not persistent, but will need to be executed again after reboot. Here is a tutorial for how to use ip route and make it persistent on Red Hat and Ubuntu. For Archlinux look in the Wiki.

[faern]

That is not a workaround. That is the proper solution. The VPN app is not responsible for properly routing your LAN. If you have a LAN you have to set up your routing table to know of this LAN. Usually this is done automatically as the LAN uses DHCP. But depending on your setup, maybe these routes are not automatic. Then you have to do it yourself.

All the app does if you allow local network access is to not explicitly block the private IP ranges in the firewall any more. It's your (or your DHCP server's) job to route to those networks.