Arch Linux

Lockheed

Member

Registered: 2010-03-16

Posts: 1,542

openresolve does not update resolve.conf after resume

I have been using hostsblock with WICD and dnsmasq and it has been working fine.

However, this solution has one weak point - WICD. It takes way to long to reconnect to a network after, for example, the computer is resumed.
So I started using connman, but then I lost all my hostsblocking because, unlike WICD,  it no longer added appropriate entries to /etc/resolve.conf

I researched the issue and found a solution - Openresolve. I configured it and it seems to be working fine after it run

sudo resolvconf -u

but that is precisely the problem. I need the resolve.conf to be updated automatically after connman connects, and as it is now - it only happens if I run the above command.

How can I get this to update automatically after connecting? My first though was a resolveconf or openresolve systemd service, but does not seem to be any.

Last edited by Lockheed (2014-08-27 07:51:31)

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: openresolve does not update resolve.conf after resume

connman may not support resolvconf.

dhcpcd on the other hand does I think NetworkManager does as well.
Basically, the "manager" needs to support resolvconf.

Have you looked into using dhcpcd-gtk in place of WICD?

Lockheed

Member

Registered: 2010-03-16

Posts: 1,542

Re: openresolve does not update resolve.conf after resume

The whole purpose of resolvconf is to be agnostic with regards to connection manager.

And it seems that in fact it does work with connman. There is a slight delay - which caused this whole thread - but it appears that up to a minute after booting or reconnecting, resolve.conf is properly adjusted by Openresolve even though no further configuration (beyond what was described in the first post) was made.

Lockheed

Member

Registered: 2010-03-16

Posts: 1,542

Re: openresolve does not update resolve.conf after resume

After using it for some time, I must say the problem is not solved.

It is true that within 1-2 minutes after system boots, /etc/resolve.conf is populated by entries from openresolve.

However, if I suspend and then resume - which causes connman to disconnect/reconnect from a network - resolve.conf is reset, and those entries are frequently NOT added again.