OpenVPN with separate DHCP server
Posted: Mon May 10, 2021 9:09 pm
I have been running Viscosity on my Mac with an OpenVPN installation for the last two years. It has always worked correctly. Only now, without changing anything in the OpenVPN install or my Viscosity configuration, it is assigning a self generated IP address (169.254.62.xxx) instead of an IP address in the correct range. Therefore I cannot access any of our internal systems, or shared drives.
Colleagues using Windows are still being assigned a correct IP address.
My OpenVPN config is using TAP with the
However, I am sure it has worked in the past. Has anything changed in Viscosity recently? My log file contains:
Colleagues using Windows are still being assigned a correct IP address.
My OpenVPN config is using TAP with the
Code: Select all
configuration. After a lot of Googling I found the following: "Note that only clients that support the binding of a DHCP client with the TAP adapter (such as Windows) can support this mode".server-bridge nogw
However, I am sure it has worked in the past. Has anything changed in Viscosity recently? My log file contains:
Code: Select all
2021-05-10 13:04:52: Viscosity Mac 1.9.3 (1571)
2021-05-10 13:04:52: Viscosity OpenVPN Engine Started
2021-05-10 13:04:52: Running on macOS 11.2.3
2021-05-10 13:04:52: ---------
2021-05-10 13:04:52: State changed to Connecting
2021-05-10 13:04:52: Checking reachability status of connection...
2021-05-10 13:04:52: Connection is reachable. Starting connection attempt.
2021-05-10 13:04:52: OpenVPN 2.4.11 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [MH/RECVDA] [AEAD] built on Apr 21 2021
2021-05-10 13:04:52: library versions: OpenSSL 1.1.1k 25 Mar 2021, LZO 2.10
2021-05-10 13:04:52: Valid endpoint found: 46.144.203.46:4911:tcp-client
2021-05-10 13:04:52: TCP/UDP: Preserving recently used remote address: [AF_INET]46.144.203.46:4911
2021-05-10 13:04:52: Attempting to establish TCP connection with [AF_INET]46.144.203.46:4911 [nonblock]
2021-05-10 13:04:53: TCP connection established with [AF_INET]46.144.203.46:4911
2021-05-10 13:04:53: TCP_CLIENT link local: (not bound)
2021-05-10 13:04:53: TCP_CLIENT link remote: [AF_INET]46.144.203.46:4911
2021-05-10 13:04:53: State changed to Authenticating
2021-05-10 13:04:53: [vpn.easylogic.nl] Peer Connection Initiated with [AF_INET]46.144.203.46:4911
2021-05-10 13:04:54: TUN/TAP device en4 opened
2021-05-10 13:04:54: DHCP enabled on tap interface en4
2021-05-10 13:05:03: Extracted DHCP router address: 172.16.10.2
2021-05-10 13:05:14: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
2021-05-10 13:05:14: Initialization Sequence Completed
2021-05-10 13:05:14: DNS mode set to Split
2021-05-10 13:05:14: DNS Server/s: 172.16.10.11
2021-05-10 13:05:14: WARNING: The DNS server 172.16.10.11 is not routed through the VPN connection. DNS lookups to this server may travel over a different network interface (en0).
2021-05-10 13:05:14: WARNING: Split DNS is being used however no DNS domains are present. The DNS server/s for this connection may not be used. For more information please see: https://www.sparklabs.com/support/kb/article/warning-split-dns-is-being-used-however-no-dns-domains-are-present/
2021-05-10 13:05:14: State changed to Connected