islandbad.blogg.se - Mullvad open vpn

I still have a few months left with proton but just not having to type every time I want to connect to a specific IP is worth it. I noticed that not only do pages load faster but annoying prompts like "are you human?" like I would get with newegg don't happen any more on both my phone and desktop. I can delete my clipboard entries TG.įor ~$5.50/month regardless of how many months it's also feasible. No more terminal window BS command line nonsense. It will run at boot automatically AND run minimized complete with tray icon. Once I did that the MullvadVPN-2020.8-beta2_b worked perfect. Mx makes that easy as a simple boot option. The ONLY thing I had to do to get mullvad to work was boot MX in systemd mode.

I tried updating to their beta "client" but all their commands were specific to an ubuntu based debian distro so that was a failed nightmare. Proton just recently made their split-tunneling option useable but still have no linux gui. I am going crazy.I permanently switched to Mullvad VPN from ProtonVPN today.

Copied below are settings for OpenVPN, NAT port forward, NAT outbound, Firewall rules, logs, and wireshark dumps.

The config below shows status with "dont pull routes" enabled, meaning that port forward does not work.

The only way I can get ports to successfully forward is by pulling all routes, and redirecting all traffic to VPN gateway (which I don't want to do).

The port forward function does not work for VPN clients.

Both LAN and VPN clients are able to access the internet on the correct gateway.

VPN traffic is tagged, floating rule blocks this traffic at WAN.

VPN clients have separate subnet, and should use VPN gateway only (192.168.65.0/24).

Question: How can I add the necessary routes to enable port forwarding without pulling routes from Mullvad VPN? If I uncheck "Don't pull routes" then both LAN and VPN clients can access the internet through their gateways, but ports are not forwarded to VPN clients anymore.

If I leave "Don't pull routes" unchecked, then my normal "LAN" traffic cannot access WAN. I have spent several days now trying to tinker with pfsense settings to allow Mullvad VPN to port forward.