On Tue, 2014-04-22 at 17:34 +0100, Burton, Ross wrote: > Hi, > > Using openconnect 5.99 on OSX Mavericks (via brew, with vpnc also for > vpnc-script) I can connect to the VPN server, /etc/resolv.conf gets > updated but Chrome can't seem to reach the network and doing DNS > lookups directly using the OSX stack (dns-sd -q foo.com) show that > it's using the non-VPN name servers. Basically, nothing works. > > To recap, where vpn.domain.name is a name that only works on the > internal DNS servers: > > $ host vpn.domain.name > > Works, as /etc/resolv.conf has the VPN name servers in and this tool > reads /etc/resolv.conf directly. > > $ killall mDNSResponder ; dns-sd -q vpn.domain.name > > Fails with no such record. > > I've reached the limit of my knowledge about OSX networking right now, > so has anyone else encountered this or knows the fix? I believe this is now fixed in the vpnc-scripts git repo, thanks to Bj?rn. Please let us know if it's still not doing the right thing for you. -- dwmw2 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5745 bytes Desc: not available URL: <http://lists.infradead.org/pipermail/openconnect-devel/attachments/20150314/bddc843f/attachment.bin>
