Websites with 10.19.x.x IP doesn't open

[GibMeMyPacket]

Issue report

Operating system: Windows

App version: v2022.5

Issue description

Hello, I am connected to OpenVPN protocol and I would like to open a website which it's IP is 10.19.171.14 but i cannot.
Doesn't matter even if i put the browser/application to Split Tunneling list, It just opens while I'm not connected to VPN.
I'm looking for a solution...

[pinkisemils]

You should try adding routes to the hosts/networks you're trying to reach via a physical interface.

[faern]

Try enabling Local network sharing in the settings. That IP is a private LAN IP and is never reachable via the VPN tunnel and will by default be blocked by our app. Enabling local network sharing should unblock that IP range.

[GibMeMyPacket]

Try enabling Local network sharing in the settings. That IP is a private LAN IP and is never reachable via the VPN tunnel and will by default be blocked by our app. Enabling local network sharing should unblock that IP range.

It was already enabled. no luck with enabling/disabling Local network sharing.

You should try adding routes to the hosts/networks you're trying to reach via a physical interface.

What?!

[pinkisemils]

If you were to run Find-NetRoute -RemoteIPAddress 10.19.0.1 and check the output, you should see that traffic headed for 10.19.0.1 is routed through the tunnel interface. This might be because you do not have a route for that particular destination going anywhere else, or it might be clashing with our tunnel network. This can be worked around by adding a route for the subnet you need. For example, to route traffic to 10.19.0.0/16 through an interface other than our tunnel, you should execute the following command in a shell with elevated privileges:

route add 10.19.0.0 MASK 255.255.0.0 %gateway_ip%`

Take note that %gateway_ip% should be replaced with the IP address of your local router/gateway, you can find the gateway address in the output of ipconfig.

[666Danger-sudo]

Why mullvad don't choose the tunnel subnet automatically at startup by allocating one that is not used? Is there any technical reason for that?

[faern]

The tunnel IP has to match with what the server expects. It's a bit different between OpenVPN and WireGuard. But in general, the client has to use the IP range allowed by the server. And OpenVPN can't just allow any subnet. This is because each server runs many OpenVPN instances, one per allowed port. And these instances need unique subnets each.

So for OpenVPN specifically you can get a different subnet by connecting over a different port. You can configure the port in settings -> VPN settings -> OpenVPN settings. You need to select a transport protocol before a port can be selected.