Yosemite no longer runs mDNSResponder, Tunnelblick up-script fails

[seb...@gmail.com]

I'm trying to get bonjour to work over my otherwise fully functional bridged VPN. Turns out the Tunnelblick up-script is looking for mDNSResponder utility to flush the cache. However, in Yosemite this has been replaced by discoveryd. The error in the script can be found at around line 1060 in client.up.tunnelblick.sh. Flushing should be done like so:

/usr/bin/discoveryutil mdnsflushcache

or in combination with flushing UDNS too:

/usr/bin/discoveryutil mdnsflushcache;/usr/bin/discoveryutil udnsflushcaches

regards

Sebastian

[jkbull...gmail.com]

What version of Tunnelblick are you using, and what is the "Set DNS/WINS" setting that you are using?

Changes to do this on Yosemite were committed to the source code as r3149 on Nov 18, 2014, so they are included in Tunnelblick 3.4.2 and 3.5beta02.

You must also use "Set nameserver" for the "Set DNS/WINS" setting. Other settings are not recommended and are included only for backward compatibility with old systems. They are not updated for new versions of OS X.

Output from the Tunnelblick 3.5beta02 log shows the following:

                                        Flushed the DNS cache via dscacheutil

                                        Will flush the DNS cache via discoveryutil udnsflushcaches...

                                        Flushed the DNS cache via discoveryutil udnsflushcaches

                                        Will flush the DNS cache via discoveryutil mdnsflushcache...

                                        Flushed the DNS cache via discoveryutil mdnsflushcache

                                        No matching processes were found

                                        mDNSResponder not running. Not notifying it that the DNS cache was flushed

(The "No matching processes were found" message refers to a check for a process named "HandsOffDaemon". If "HandsOffDaemon" is running, mDNSResponder should **not** be notified that the cache was flushed because doing so causes "HandsOffDaemon" to crash the OpenVPN process.)

[seb...@gmail.com]

Yes, I noticed this just after submitting. I have tried the beta and it seems to flush correctly now.

However, what you you mean by "You must also use "Set nameserver" for the "Set DNS/WINS" setting? EDIT: I am using "Set nameserver"

I have noticed that a LAN connected host running Mavericks will automatically find my VPN client running Yosemite. But not the other way around. I do see the traffic on tap0 on client but it seems to get ignored by discoveryd or something? Do you have any ideas why this is so?

[jkbull...gmail.com]

On Tuesday, December 23, 2014 1:42:25 PM UTC-5, Sebastian B wrote:

Yes, I noticed this just after submitting. I have tried the beta and it seems to flush correctly now.

However, what you you mean by "You must also use "Set nameserver" for the "Set DNS/WINS" setting? EDIT: I am using "Set nameserver"

DNS flushing is only done if "Set DNS/WINS" is set to "Set nameserver". Other settings of "Set DNS/WINS" do not do DNS flushing (unless you have custom scripts that do so).

 

I have noticed that a LAN connected host running Mavericks will automatically find my VPN client running Yosemite. But not the other way around. I do see the traffic on tap0 on client but it seems to get ignored by discoveryd or something? Do you have any ideas why this is so?

Sorry, I have no idea. That's really an OpenVPN or OpenVPN on OS X question. Consult OpenVPN resources such as

• OpenVPN FAQ
• OpenVPN HOWTO
• OpenVPN 2.3 Man Page
• OpenVPN Documentation
• Using OpenVPN
• OpenVPN Users Forum
• OpenVPN Users Mailing List

 

On Tuesday, December 23, 2014 7:32:20 PM UTC+1, jkbull...gmail.com wrote: