Skip to content
"Resolver #1" has my ISP's DNS servers, which won't answer when VPN is active.
"Resolver #2" has my VPN connection's valid DNS server, which answers if I manually query "dig @x.x.x.x http://www.google.com A" where x.x.x.x is the DNS server in "Resolver #2".
So it looks like that for some reason GUI apps don't even attempt to use "Resolver #2".
Below is the output (with actual IPs hidden):
Beta: Latest Build of Viscosity for Mac
Viscosity Menu Icon Packs, Two-Factor Scripts, & OpenVPN Config Tool
-
James
- Posts: 2376
- Joined: Thu Sep 04, 2008 9:27 pm
Post
by James » Sat Sep 06, 2014 10:44 pm
Hi donza,
What does your "scutil --dns" output look like while connected to your VPN connection (when you are having DNS trouble)? Information about running this command can be found in the "Checking Which DNS Servers Are Being Used" section at:
http://www.sparklabs.com/support/config ... ins_setti/
Cheers,
James
What does your "scutil --dns" output look like while connected to your VPN connection (when you are having DNS trouble)? Information about running this command can be found in the "Checking Which DNS Servers Are Being Used" section at:
http://www.sparklabs.com/support/config ... ins_setti/
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
-
donza
- Posts: 4
- Joined: Fri Sep 05, 2014 3:04 am
Post
by donza » Sun Sep 07, 2014 6:31 pm
James wrote:Hi donza,Hi James,
What does your "scutil --dns" output look like while connected to your VPN connection (when you are having DNS trouble)? Information about running this command can be found in the "Checking Which DNS Servers Are Being Used" section at:
http://www.sparklabs.com/support/config ... ins_setti/
Cheers,
James
"Resolver #1" has my ISP's DNS servers, which won't answer when VPN is active.
"Resolver #2" has my VPN connection's valid DNS server, which answers if I manually query "dig @x.x.x.x http://www.google.com A" where x.x.x.x is the DNS server in "Resolver #2".
So it looks like that for some reason GUI apps don't even attempt to use "Resolver #2".
Below is the output (with actual IPs hidden):
Code: Select all
DNS configuration
resolver #1
search domain[0] : tun0.viscosity
search domain[1] : Cisco
nameserver[0] : a.a.a.a
nameserver[1] : b.b.b.b
if_index : 4 (en0)
flags : Request A records
resolver #2
domain : tun0.viscosity
nameserver[0] : x.x.x.x
flags : Request A records
reach : Reachable
order : 100400
-
James
- Posts: 2376
- Joined: Thu Sep 04, 2008 9:27 pm
Post
by James » Sun Sep 07, 2014 9:12 pm
Hi donza,
It sounds like you have the "Apply DNS settings simultaneously" option turned on (under Preferences->Advanced). Turning this option off should give you the behaviour you're after.
Cheers,
James
It sounds like you have the "Apply DNS settings simultaneously" option turned on (under Preferences->Advanced). Turning this option off should give you the behaviour you're after.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
-
donza
- Posts: 4
- Joined: Fri Sep 05, 2014 3:04 am
Post
by donza » Sat Sep 13, 2014 6:09 pm
James wrote:Hi donza,Thanks James! I'm not sure when that setting got enabled, but disabling it did the trick.
It sounds like you have the "Apply DNS settings simultaneously" option turned on (under Preferences->Advanced). Turning this option off should give you the behaviour you're after.
Cheers,
James
-
NanoG6
- Posts: 5
- Joined: Tue Nov 04, 2014 6:47 pm
Post
by NanoG6 » Tue Nov 04, 2014 6:49 pm
Hello,
After updated to latest beta release today, I can't connect to server with following error log:
After updated to latest beta release today, I can't connect to server with following error log:
Code: Select all
Any help would be greatly appreciated. Thank you.Nov 04 15:43:35: Viscosity Mac 1.5.3b2 (1244)
Nov 04 15:43:35: Viscosity OpenVPN Engine Started
Nov 04 15:43:35: Running on Mac OS X 10.10
Nov 04 15:43:35: ---------
Nov 04 15:43:35: Checking reachability status of connection...
Nov 04 15:43:35: Connection is reachable. Starting connection attempt.
Nov 04 15:43:35: OpenVPN 2.3.5 x86_64-apple-darwin [SSL (OpenSSL)] [LZO] [PKCS11] [MH] [IPv6] built on Nov 3 2014
Nov 04 15:43:35: library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08
Nov 04 15:43:38: WARNING: No server certificate verification method has been enabled. See http://openvpn.net/howto.html#mitm for more info.
Nov 04 15:43:38: ******* WARNING *******: null cipher specified, no encryption will be used
Nov 04 15:43:38: Assertion failed at crypto_openssl.c:525
-
James
- Posts: 2376
- Joined: Thu Sep 04, 2008 9:27 pm
Post
by James » Wed Nov 05, 2014 3:34 pm
Hi NanoG6,
It appears there is a bug in OpenVPN 2.3.5 if encryption is disabled, which is what you're running into. We'll see if we can come up with a patch or workaround for it - in the meantime I'd recommend dropping back to the stable release which comes with OpenVPN 2.3.4.
Cheers,
James
It appears there is a bug in OpenVPN 2.3.5 if encryption is disabled, which is what you're running into. We'll see if we can come up with a patch or workaround for it - in the meantime I'd recommend dropping back to the stable release which comes with OpenVPN 2.3.4.
Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com
Support: https://www.sparklabs.com/support
Bluesky: https://bsky.app/profile/sparklabs.com