[Resolvconf-devel] Bug#791978: interfaces-order is being ignored
jdthood at gmail.com
Fri Jul 10 20:50:04 UTC 2015
> resolvconf is not putting the tun0 resolvers
> below that of eth* even though tun* is supposed to take precedence
I don't understand this. If tun* is supposed to take precedence over eth*
then resolvconf *shouldn't* put the tun0 resolver addresses *below* those
of eth* in resolv.conf; resolvconf should put the tun0 resolver addresses
*above* those of eth*.
And resolvconf does what it should do. According to interface-order, tun*
is listed before eth*. The record /run/resolvconf/interface/tun0.f5
whereas the record /run/resolvconf/interface/eth0.f5 contains
and the record /run/resolvconf/interface/eth3.dhclient contains the
The information from tun0.f5 should take precedence. And that is what we
see in resolv.conf.
# Dynamic resolv.conf(5) file for glibc resolver(3) ...
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES ...
If there is a problem then the problem is with the contents of the
record /run/resolvconf/interface/tun0.f5 which comes from the program
that calls resolvconf to create that record. Which interface
configuration utility writes that record? What is "f5"?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Resolvconf-devel