resolvconf is unaware of biosdevname NIC names

Bug #949473 reported by Jared Dominguez on 2012-03-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resolvconf (Ubuntu)

Bug Description

resolvconf is unaware of how to handle biosdevname NIC names, which are of the form em* and p*p*.

In the resolvconf (1.63ubuntu9) source package, bin/list-records lacks these entries, and line 27 of etc/resolvconf/interface-order lacks them as well:

PATTERNS="lo* eth* ath* wlan* ppp* *"

I am not sure of the preferred ordering to fix this.

Related branches

Thomas Hood (jdthood) wrote :

Hmm, must read up on biosdevnames.... At we learn:

Embedded devices: emX_Y (X = embedded LOM ID, Y = NPAR NIC index) -- e.g., em1_1, em1_2, em2, ....
Add-in cards: pXpY_Z (X=PCI slot, Y=port#, Z = NPAR NIC index) -- e.g., p6p1_1, p6p1_2, p6p2_1, ....

Thomas Hood (jdthood) wrote :

Here's a patch I have just applied to the Debian package (in git) to add the biosdevnames patterns. Beyond that it fixes a documentation bug.

The attachment "Patch to add biosdevnames patterns and tweak documentation" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

tags: added: patch

The portion including and after the "_" is only for Network Partitioning (NPAR) enabled NICs when the NPAR feature is enabled. On a typical machine with biosdevname enabled without NPAR, you will see em* and p*p*. For one with an NPAR-enabled NIC, you may see em*_* or p*p*_*.

Thomas Hood (jdthood) wrote :

OK, thanks for the clarification. Here's an updated patch.

Stéphane Graber (stgraber) wrote :

Patch looks good, though I'm wondering if it shouldn't be expanded to support other devices like brides (br*) and bonds (bond*) for what's commonly used.

I must admit I haven't read through the whole script so I'm not sure if bridges and bonds are also relevant to that part of the code.

I agree with Stéphane that bridges and bonds probably should be supported. Also, while I don't think there are any systems with more than ten embedded NICs, PCI slots, ports per PCI card or NPAR virtual interfaces, it might be a good idea to support this.

Thomas Hood (jdthood) on 2012-03-13
Changed in resolvconf (Ubuntu):
status: New → Confirmed
status: Confirmed → In Progress
Steve Langasek (vorlon) on 2012-03-17
Changed in resolvconf (Ubuntu):
status: In Progress → Fix Committed
importance: Undecided → Medium
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package resolvconf - 1.63ubuntu10

resolvconf (1.63ubuntu10) precise; urgency=low

  * debian/config: handle 'inet6 dhcp' interfaces the same as 'inet dhcp'
    ones for detecting dynamic DNS information.
  * bin/list-records, etc/resolvconf/interface-order: cherry-pick upstream
    support for biosdevname-style interface names. Thanks, Thomas!
    LP: #949473.
  * man/resolvconf.8: point to the right directory for dhcp hooks.
    LP: #953257.
 -- Steve Langasek <email address hidden> Sat, 17 Mar 2012 12:13:34 -0700

Changed in resolvconf (Ubuntu):
status: Fix Committed → Fix Released

Thank you Thomas and Steve!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers