Openvpn on 20.04

[Karl Auer]

On Fri, 2021-08-13 at 23:52 +0200, Bo Berglund wrote:
> Better use something like 10.217.113.x, which is much less likely to
> be duplicated elsewhere.

Good advice, but you cannot guarantee no conflicts ever unless you
acquire your own IP address range and use that (nowadays very difficult
in the IPv4 space). Failing that, a random RFC1918 (private) network
range is your best bet. Some people like to use subnets from
172.16.0.0/12, because that range is rarely used by manufacturers.

> However the windows machine I use with the watch guard client does
> not have that issue. It just worked.  
> 
> This might be caused by DNS if you are pinging or trying to connect
> via names rather than IP address.

I don't think so. Addresses are addresses. I think some kind of
additional NATting was happening with the Windows client. If the
software at each end is from the same vendor, it could well be
cooperating with the server in ways not available to the standard
software.

Another possibility is that the server (along with the resources you
are accessing in the remote network) is IPv6 capable, and the Windows
client is just using IPv6 instead of IPv4.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer (kauer at biplane.com.au)
http://www.biplane.com.au/kauer

GPG fingerprint: 61A0 99A9 8823 3A75 871E 5D90 BADB B237 260C 9C58
Old fingerprint: 2561 E9EC D868 E73C 8AF1 49CF EE50 4B1D CCA1 5170