[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2015-04-21 Thread Thomas Hood
The original problem was fixed in resolvconf 1.70 which has since been merged to Vivid. ** Changed in: resolvconf (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2015-04-20 Thread Kevin Otte
I just discovered another gotcha. The new interface-order in #17 doesn't handle bridge interfaces. I've added those above the eth* for the following new file: # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo tun* tap* hso* em+([0-9])?(_+([0-9]))*

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2013-02-09 Thread Thomas Hood
Done in recently released Debian resolvconf 1.70. -- 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

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2013-01-28 Thread Thomas Hood
@Kevin: On second thought I think your suggestion in comment #14 is right; I now propose to release Debian resolvconf 1.70 with the following. Comments still more than welcome, of course. # interface-order(5) lo.inet6 lo.inet lo.@(dnsmasq|pdnsd) lo.!(pdns|pdns-recursor) lo tun* tap* hso*

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2013-01-19 Thread Thomas Hood
If there are no further comments then I'll prepare Debian resolvconf 1.70 according to the proposal from #11. -- 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,

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2013-01-13 Thread Thomas Hood
In the case of static IPv4 but automatic IPv6, this will still result in the IPv4 taking precedence. [...] I propose that the order list all of the IPv6 items before the IPv4. Hmm, are there reasons for preferring either one over the other? This may be one of those changes where the problems

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2013-01-11 Thread Kevin Otte
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)

[Bug 1094345] Re: IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order

2013-01-05 Thread Thomas Hood
** Summary changed: - IPv6 DHCP record is too late in resolvconf interface-order + IPv6 DHCP record too late, and other irregularities, in resolvconf interface-order -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.