signaturesilikon.blogg.se - Openvpn tunnelblick dns fail

13:43:20.583233 *Tunnelblick: Established communication with OpenVPN down /Applications/Tunnelblick.app/Contents/Resources/ -9 -d -f -m -w -ptADGNWradsgnw route-up /Applications/Tunnelblick.app/Contents/Resources/client.up.tunnelblick.sh -9 -d -f -m -w -ptADGNWradsgnw management 127.0.0.1 54780 /Library/Application Support/Tunnelblick/lobglbllpkjmegfngnhddlfmngmekkkmgmedbpfl.mip setenv TUNNELBLICK_CONFIG_FOLDER /Library/Application Support/Tunnelblick/Users/jbye/PROD.tblk/Contents/Resources config /Library/Application Support/Tunnelblick/Users/jbye/PROD.tblk/Contents/Resources/config.ovpn cd /Library/Application Support/Tunnelblick/Users/jbye/PROD.tblk/Contents/Resources log /Library/Application Support/Tunnelblick/Logs/-SUsers-Sjbye-SLibrary-SApplication .769_0_1_0_ Applications/Tunnelblick.app/Contents/Resources/openvpn/openvpn-2.4.7-openssl-1.0.2r/openvpn 13:43:20.564603 *Tunnelblick: openvpnstart log:Ĭommand used to start OpenVPN (one argument per displayed line): 13:43:20.180806 Need hold release from management interface, waiting. 13:43:20.008177 *Tunnelblick: openvpnstart starting OpenVPN 13:43:19.942329 *Tunnelblick: Attempting connection with PROD using shadow copy Set nameserver = 769 monitoring connection

NSWindow Frame SUUpdateAlert = 2090 588 67ĭetailsWindowFrame = ĭetailsWindowConfigurationsTabIdentifier = logĪdvancedWindowTabIdentifier = connectingAndDisconnecting SkipWarningAboutSimultaneousConnections = 1ĭoNotShowDisconnectedNotificationWindows = 1ĬonnectionWindowDispla圜riteria = showWhenConnecting allowChangesToManuallySetNetworkSettings = 0 notOKToCheckThatIPAddressDidNotChangeAfterConnection = 1 "Sanitized" condensed configuration file for /Users/jbye/Library/Application Support/Tunnelblick/Configurations/PROD.tblk: Tunnelblick should correctly save and restore the DNS state, regardless of the number of VPNs that connect/disconnect. Observe that DNS is left in a bad state and internet access no longer works, even though both VPNs are disconnected.

Disconnect from one VPN, observe that DNS is still functional.

Create two VPN configurations, making sure both are set to "Set nameserver" and use the default up/down scripts that are included in Tunnelblick.

It appears that the "saved Tunnelblick DNS information" is removed by the first disconnect, and the second disconnect is unable to use that saved information to correctly restore the DNS state.