My apologies for the delay in responding. Pesky life and all that.
The proposed interface-order in #11 does work for my particular case. I
do have some thoughts on the bigger picture though.
> eth*([^.]).inet6
> eth*([^.]).inet
> eth*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc)
> eth*([^.]).@(dhclient|dhcpcd|pump|udhcpc)
In the case of static IPv4 but automatic IPv6, this will still result in
the IPv4 taking precedence. eg:
---
iface eth0 inet static
...
dns-nameservers 1.2.3.4
iface eth0 inet6 auto
dhcp 1
--
Would produce a resolv.conf with:
--
nameserver 1.2.3.4
nameserver 2001:db8:1234::1
--
I propose that the order list all of the IPv6 items before the IPv4.
eth*([^.]).inet6
eth*([^.]).ip6.@(dhclient|dhcpcd|pump|udhcpc)
eth*([^.]).inet
eth*([^.]).@(dhclient|dhcpcd|pump|udhcpc)
Like you I'm on the fence about switching the static vs dynamic order.
Some of our more learned colleagues may need to chime in here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094345
Title:
IPv6 DHCP record too late, and other irregularities, in resolvconf
interface-order
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1094345/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
