tailscale VS OpenVPN

Tailscale - Built on WireGuard. Easy to use. Control server is closed source. Client code available with a BSD3 license + separate patents file.

Tailscale

I'm using the GitHub version of tailscaled on one of my Macs as a background daemon launched at boot. To upgrade to the latest version, try the following:

Tailscale is a VPN service that makes the devices and applications you own accessible anywhere in the world, securely and effortlessly. It enables encrypted point-to-point connections using the open source WireGuard® protocol, which means only devices on your private network can communicate with each other.

Might be possible to do using a VPN as long as you can get broadcast/multicast packets forwarded.

Tailscale unfortunately doesn't support it...yet?

https://github.com/tailscale/tailscale/issues/1013

Tailscale - Make depaware output patch compatible

Tailscale is another way of doing it. I'm using it to access my Pi's Samba shares from my phone but it works from Windows as well.

OpenVPN is hiring! https://openvpn.net/

C++ Developer in the United States. Full-time| Fully remote| Flexible work schedules

Link to look at vacancy details and apply:

How you connect to your modem will depend on the device you are using, but for windows laptops as an example you download the OpenVPN program and input your modem details there, much like you would any other vpn service. I think there would be some guides on youtube. https://openvpn.net/

I just started playing with CloudConnexa for remotely managing my second pFSense. Really nice and is free for up to 3 concurrent users. https://openvpn.net. Can also self-host OpenVPN access server with a free 2 concurrent license.

If anyone is being blocked check out free OpenVPN

It is likely an issue with the 'cipher' options, if any, that are in your ".opvn" file. This is telling you that the opvn setting is not finding a matching cipher it is allowed to use. The fix per the message would be to add the Servers cipher to your options. https://github.com/OpenVPN/openvpn-gui/issues/381 https://github.com/OpenVPN/openvpn/blob/master/doc/man-sections/cipher-negotiation.rst

I too haven't used the client-nat directive in some years (I currently implement 1:1 NAT with pfsense to access my network because I'm too lazy to change the networks subnet from the default) so I decided to retest and it does appear that OpenVPN Connect clients do not properly support the client-nat directive but the traditional OpenVPN server/clients still do. I've just tested this on OpenVPN 2.6.3 Server, OpenVPN 2.6.1 GUI for Windows from openvpn.net, and OpenVPN Connect iOS 3.3.3 and only the OpenVPN Connect client has any difficulty. Difficulty being that you can use client-nat successfully but it has to be configured server-side it can't be pushed to or setup on the client (OpenVPN Connect) side. The Server and Windows (non-OpenVPN Connect) clients work an any setup whether it's configured server-side, pushed to the client, or set up in the client config.

Ask openvpn.net for commercial support: https://support.openvpn.com/

OpenVPN is a VPN client that I used primarily for work. We used VPN to connect to the dev server and we are using VPN. I also sometimes used that to open websites that got blocked in Indonesia like Reddit.

I connect all the servers with secure OpenVPN private network. And block unused ports anywhere with ufw.