interface-order needs definitions for systemd predictable names

Bug #1610479 reported by Kevin Otte
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Another release, another round of interface name changes.

This time systemd has gotten into the fray to make things even more interesting.

https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

As such, IPv4 resolvers are now being preferred over IPv6 again on these new interface names.

kjotte@flounder:~$ grep '' /run/resolvconf/interface/ens3.*
/run/resolvconf/interface/ens3.dhclient:search nivex.lan.
/run/resolvconf/interface/ens3.dhclient:nameserver 172.31.3.30
/run/resolvconf/interface/ens3.ip6.dhclient:search home.nivex.net.
/run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:121::10
/run/resolvconf/interface/ens3.ip6.dhclient:nameserver fd60:e0:a0f4:321::4

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Aug 5 19:53:25 2016
InstallationDate: Installed on 2016-08-04 (1 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
ProcEnviron:
 TERM=vt220
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Kevin Otte (nivex) wrote :
Revision history for this message
Thomas Hood (jdthood) wrote :

Hi and thanks for the report. How 'bout a patch?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in resolvconf (Ubuntu):
status: New → Confirmed
Revision history for this message
Kevin Otte (nivex) wrote :

Pattern matching and I have never been fast friends, but this appears to work in my one little test case.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "interface-order.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Kevin Otte (nivex) wrote :

Previous patch did not fully account for PCI bus description. New patch attached.

Changed in resolvconf (Ubuntu):
importance: Undecided → Wishlist
Revision history for this message
Kevin Otte (nivex) wrote :

I'm curious why this has been given such an abysmally low priority (wishlist) when a similar bug (#1094345) was fixed quickly a few years ago and a patch has been submitted.

Changed in resolvconf (Ubuntu):
importance: Wishlist → High
Revision history for this message
Kevin Otte (nivex) wrote :

Is there anything else you need from me to be able to merge this patch?

Revision history for this message
Thomas Hood (jdthood) wrote :

I revised the patch slightly (to put the wl* names with the wifi* names) and have applied it to the Debian package which I plan to release soon.

Revision history for this message
Suho Meso (kunalija) wrote :

Hi,

I've an issue using resolvconf in combination with rdnssd. The host is getting the nameserver stuff via RDNSS, not DHCPv6.
The interface order doesn't cover the rdnssd method?! Interface name should be ens3.

/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::47
/run/resolvconf/interface/000.rdnssd:nameserver 2a02:...::48
/run/resolvconf/interface/ens3.dhclient:domain abz.com
/run/resolvconf/interface/ens3.dhclient:search abz.com
/run/resolvconf/interface/ens3.dhclient:nameserver 10.x.x.47

root@host:/etc/resolvconf# cat /etc/network/interfaces
# Interface lo
auto lo
iface lo inet loopback
# Interface lo_ipv6
iface lo inet6 loopback
# Interface ens3
auto ens3
iface ens3 inet dhcp
# Interface ens3_ipv6
iface ens3 inet6 auto

root@host:/etc/resolvconf# dpkg -l | grep resolvconf
ii resolvconf 1.78ubuntu6 all name server information handler
root@host:/etc/resolvconf# dpkg -l | grep rdnssd
ii rdnssd 1.0.1-1ubuntu2 amd64 IPv6 recursive DNS server discovery daemo

root@host:/etc/resolvconf# cat /etc/issue
Ubuntu 16.04.4 LTS \n \l

root@host:/etc/resolvconf# uname -a
Linux ermscn01 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package resolvconf - 1.82

---------------
resolvconf (1.82) unstable; urgency=medium

  [ Andrej Shadura ]
  * Update the debconf translation templates (Closes: #947164).
  * Update translations.

  [ Helge Kreutzmann ]
  * Update German debconf translation (Closes: #947171).

  [ Frans Spiesschaert ]
  * Update Dutch debconf translation (Closes: #948037).

 -- Andrej Shadura <email address hidden> Fri, 03 Jan 2020 18:32:03 +0100

Changed in resolvconf (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.