| Summary: | net-vpn/networkmanager-openvpn and net-dns/openresolv: unexpected(?) DNS order | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Benjamin Schindler <beschindler> |
| Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | alexander, andreacerisara, bkohler |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Benjamin Schindler
2017-03-14 13:14:49 UTC
What's the name of your tun/tap interface? I prefer to give names to vpn interfaces like "tun_${some meaningful name}" so I had to change dynamic_order in resolvconf.conf:
$ grep dynamic_order /etc/resolvconf.conf
dynamic_order="${dynamic_order} tun_*"
You should define the metric in the route: --route network/IP [netmask] [gateway] [metric] This will enable you to control the route metrics and also if prioritize will affect the DNS metrics. Hey, sorry for not getting back earlier. I did not receive notification about your answers here.
I think I am getting to the bottom of this - resolvconf has two interfaces listed - eth0.dhcp and NetworkManager. The resolv.conf for eth0.dhcp just contained 192.168.1.1 (changed ip's in the meantime) and the one from NetworkManager contained the correct order:
nameserver 192.168.141.10
nameserver 192.168.141.250
nameserver 192.168.1.1
And in addition, eth0.dhcp hat a metric, NetworkManager didn't. So what I did is this in resolvconf.conf:
interface_order="NetworkManager ${interface_order}"
I consider this to be a quite ugly hack, so my question is: where does eth0.dhcp come from? Is this systemd (I did not mention that I am using systemd) fighting against NetworkManager?
(In reply to Benjamin Schindler from comment #3) > I consider this to be a quite ugly hack, so my question is: where does > eth0.dhcp come from? Is this systemd (I did not mention that I am using > systemd) fighting against NetworkManager? You probably have NetworkManager configured with dhcpcd. Try to disable resolv.conf hook: add "nohook resolv.conf" into /etc/dhcpcd.conf. Note that this is just my guess. I think that's where .dhcp suffix came from (/lib/dhcpcd/dhcpcd-run-hooks):
case "$reason" in
ROUTERADVERT)
ifsuffix=".ra";;
INFORM6|BOUND6|RENEW6|REBIND6|REBOOT6|EXPIRE6|RELEASE6|STOP6)
ifsuffix=".dhcp6";;
IPV4LL)
ifsuffix=".ipv4ll";;
*)
ifsuffix=".dhcp";;
esac
ifname="$interface$ifsuffix"
(In reply to Benjamin Schindler from comment #3) > Hey, sorry for not getting back earlier. I did not receive notification > about your answers here. > > I think I am getting to the bottom of this - resolvconf has two interfaces > listed - eth0.dhcp and NetworkManager. The resolv.conf for eth0.dhcp just > contained 192.168.1.1 (changed ip's in the meantime) and the one from > NetworkManager contained the correct order: > > nameserver 192.168.141.10 > nameserver 192.168.141.250 > nameserver 192.168.1.1 > > And in addition, eth0.dhcp hat a metric, NetworkManager didn't. So what I > did is this in resolvconf.conf: > > interface_order="NetworkManager ${interface_order}" > > I consider this to be a quite ugly hack, so my question is: where does > eth0.dhcp come from? Is this systemd (I did not mention that I am using > systemd) fighting against NetworkManager? Can you confirm if you are using networkmanager with dhcpcd? |
