![\"REBOOT.\"](\"http:\/\/www.chesnok.com\/daily\/wp-content\/uploads\/2013\/10\/TurningitOffandOnAgain1.jpg\")
<\/a><\/p>\nFortunately, I had an easy (for me) work-around for most of my VPN needs: use SSH and a jump-host for getting to servers. I found it annoying when I wanted to look at a website on protected network space, or had a service on an unusual port that I wanted to test things against. I would work around with SSH tunnels, or I would fire up my Mac, whose VPN settings worked flawlessly.<\/p>\n
That all said, I thought today, a sunny, lovely fall day in Portland, I would fix my VPN.<\/p>\n
And so, my buddy @uberj_<\/a> helped me get things sorted.<\/p>\n The root cause of all my VPN heartache was the However, they leave out one important step: killing off the existing dnsmasq process. For the unlucky, restarting So, to find and kill dnsmasq, do the following:<\/p>\n Then, start your VPN and check out the contents of the Sadly, this was not the end of my story.<\/p>\n After a few minutes, NetworkManager started So, like any reasonable sysadmin, I opened up the I ran I tried also uninstalling While editing this blog post, A clue as to what was happening was in It turns out that And I found this thread<\/a>, and this sample configuration file<\/a>. In the output for the I dug into the thread, and the suggestion was to set And then I got this in my syslog:<\/p>\n FINALLY.<\/p>\n I’ve been having problems with VPN, DNS and Ubuntu for a year. But, I’m also pretty lazy when it comes to spending time on configuration. And configuring VPNs is like last on my list of ways I’d like to spend … Continue reading →<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[146],"tags":[],"class_list":["post-5027","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts\/5027","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/comments?post=5027"}],"version-history":[{"count":10,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts\/5027\/revisions"}],"predecessor-version":[{"id":5044,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/posts\/5027\/revisions\/5044"}],"wp:attachment":[{"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/media?parent=5027"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/categories?post=5027"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.chesnok.com\/daily\/wp-json\/wp\/v2\/tags?post=5027"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}dnsmasq<\/code> daemon controlling my DNS. And, related, network-manager<\/code>. There are a few places that document exactly how to disable dnsmasq<\/code><\/p>\n\n
network-manager<\/code> does not kill off dnsmasq<\/code>.<\/p>\n sudo service network-manager stop\n kill `ps -C dnsmasq -o pid=`\n sudo service network-manager start\n<\/code><\/pre>\n\/etc\/resolv.conf<\/code>. If all went well, you’ve got nameserver addresses other than 127.0.0.1<\/code> in the file.<\/p>\n<\/a><\/p>\ndnsmasq<\/code> up again!<\/p>\n<\/a><\/p>\n\/etc\/NetworkManager\/NetworkManager.conf<\/code> file, uncommented the dns=dnsmasq<\/code> line, and replaced it with dns=\/dev\/null<\/code>. My guess was that you can probably put just about anything other than dnsmasq into that line to permanently disable the plugin.<\/p>\nsudo service network-manager restart<\/code>, checked \/etc\/resolv.conf<\/code> and felt pretty smug.<\/p>\ndnsmasq-base<\/code> package, but unfortunately that takes out a number of other packages I appear to need. So, I left \/dev\/null in my NetworkManager.conf, and updated this blog post.<\/p>\n<\/a><\/p>\ndnsmasq<\/code> took over my DNS settings again.<\/p>\n\/var\/log\/syslog<\/code>:<\/p>\nOct 18 10:20:10 localhost dnsmasq[30535]: started, version 2.59 cache disabled\nOct 18 10:20:10 localhost dnsmasq[30535]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN\nOct 18 10:20:10 localhost dnsmasq[30535]: DBus support enabled: connected to system bus\nOct 18 10:20:10 localhost dnsmasq[30535]: warning: no upstream servers configured\n<\/code><\/pre>\ndnsmasq<\/code> was still getting revived by NetworkManager<\/code>. Why NetworkManager doesn’t seem to care about configuration settings was beyond my willingness to investigate today. So, I did some more searching about truly killing of dnsmasq for good.<\/p>\ndnsmasq<\/code> process from ps:<\/p>\nnobody 30777 30759 0 10:21 ? 00:00:00 \/usr\/sbin\/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=\/var\/run\/sendsigs.omit.d\/network-manager.dnsmasq.pid --listen-address=127.0.0.1 --conf-file=\/var\/run\/nm-dns-dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus --conf-dir=\/etc\/NetworkManager\/dnsmasq.d\n<\/code><\/pre>\nport=0<\/code> in the config. I created a file called custom<\/code> in \/etc\/NetworkManager\/dnsmasq.d<\/code>. And ran sudo service network-manager restart<\/code>.<\/p>\nOct 18 10:21:10 localhost dnsmasq[30777]: started, version 2.59 DNS disabled\n<\/code><\/pre>\n<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
![this thread<\/a>, and](\"http:\/\/www.chesnok.com\/daily\/wp-content\/uploads\/2013\/10\/7512696366_76be236667.jpg\"){kind=link}