@Kevin: Can you please test the interface-order file I posted in comment
#11? Let me know if the file works properly for you.
--
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
The proposed new interfaces-order file that I just posted (comment #11)
can be compared with the current one.
=== BEGIN ===
# interface-order(5)
lo.inet*
lo.dnsmasq
lo.pdnsd
lo.!(pdns|pdns-recursor)
lo
tun*
tap*
hso*
em+([0-9])?(_+([0-9]))*
p+([0-9])p+([0-9])?(_+([0-9]))*
eth*
ath*
wlan*
ppp*
*
Consider eth0 with inet, inet6, dhclient and ip6.dhclient records. These
are currently ordered (alphabetically) as follows.
eth0.dhclient
eth0.inet
eth0.inet6
eth0.ip6.dhclient
Observations:
* IPv4 comes before IPv6
* The prioritization of *dhclient versus inet* is inconsistent.
This workaround is confirmed to work. Thanks much!
I personally believe, in light of the World IPv6 Launch and the
continued adoption of IPv6, that this behavior should be the norm. I
look forward to the continued discussion on this.
Thanks again.
--
You received this bug notification because
Not sure if this needs a separate bug report, but I have a machine in a
similar configuration that uses a bridge for virtual machines, so it is
br0 rather than eth0. I added a
br*([^.]).ip6.dhclient
to the interface-order file and it works as expected. Is this something
you will want to address
An additional note on ordering policy: when using NetworkManager the
IPv6 records are listed first.
--
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 is too late in
Is this something you will want to address in the package as well
Yes, the behavior should be consistent across interface types.
when using NetworkManager the IPv6 records are listed first
That certainly lends weight to the proposal that resolvconf also put
IPv6 records first.
--
You
