On Fri, Oct 7, 2016 at 10:44 PM, Martin Pitt <email address hidden>
wrote:
>> To fix the problem
>
> Please tell us what actually *is* the problem.
My apologies, I should have said "To work around the problem" in the
last comment.
>> I need to manually edit /etc/resolv.conf and replace dnsmasq's
> 127.0.0.1 with resolve's 127.0.0.53
>
> So are you trying to not use NM's dnsmasq instance because that stops
> working after suspend/resume?
It looks like it, yes. As I (obliquely) mentioned in comment 3, dnsmasq
seems to stop responding to UDP requests on 127.0.0.1 after resume.
On Fri, Oct 7, 2016 at 10:44 PM, Martin Pitt <email address hidden>
wrote:
>> To fix the problem
>
> Please tell us what actually *is* the problem.
My apologies, I should have said "To work around the problem" in the
last comment.
>> I need to manually edit /etc/resolv.conf and replace dnsmasq's
> 127.0.0.1 with resolve's 127.0.0.53
>
> So are you trying to not use NM's dnsmasq instance because that stops
> working after suspend/resume?
It looks like it, yes. As I (obliquely) mentioned in comment 3, dnsmasq
seems to stop responding to UDP requests on 127.0.0.1 after resume.
-- mjog.vee. net/>
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://