Page MenuHomeVyOS Platform
Create Task
Maniphest T1058

hw-id is ignored when naming interfaces
Closed, ResolvedPublic
Actions

Description

My machine has several network interfaces defined using the hw-id value.

e.g.,

interfaces {
  ethernet eth0 {
    hw-id 11:11:11:11:11:11
  }
  ethernet eth1 {
    hw-id 11:11:11:11:11:12
  }
  ethernet eth2 {
    hw-id 22:22:22:22:22:2a
  }
  ethernet eth3 {
    hw-id 22:22:22:22:22:2b
  }
}

eth0 and eth1 are both onboard interfaces while eth2 and eth3 are ports on a dual port Intel 82571EB adapter.

For whatever reason, the 82571EB adapter parts are being named eth0 and eth1 while the onboard ports are named eth2 and eth3. 'ip addr' reports that the eth names match the MAC addresses but this is incorrect.

I've tried the following:

  • Adding udev rules (doesn't work)
  • Moving the hw-id values around (doesn't work)

I've physically moved the cables in order to get the network back up. This very same configuration works correctly in Vyos 1.1.8.

Details

Difficulty level
Unknown (require assessment)
Version
1.2.0-r9
Why the issue appeared?
Will be filled on close
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Bug (incorrect behavior)

Related Objects

Event Timeline

kris240376 created this task.Nov 29 2018, 4:04 AM
kris240376 created this object in space S1 VyOS Public.
syncer assigned this task to UnicronNL.Dec 1 2018, 6:21 PM
syncer triaged this task as Normal priority.
syncer edited projects, added VyOS 1.3 Equuleus; removed VyOS 1.2 Crux (VyOS 1.2.0-rc10).
syncer added subscribers: UnicronNL, syncer.

@UnicronNL we need to have ability to create link files and update initrd with them

pasik added a subscriber: pasik.Mar 12 2019, 6:08 PM
rps added a subscriber: rps.Sep 5 2019, 10:31 PM

I'm able to reproduce this bug.

Might also be related to the issue described here:

https://forum.vyos.io/t/vyos-1-2-0-is-not-working-with-supermicro-motherboards/3598

I just ran into this on a reference box when testing 1.2.3-epa1 and verify that it's a problem in 1.2.1 and 1.2.2 as well.

In this case using an Intel 82599ES dual-port 10GbE adapter on a Supermicro Atom C2000 with 4 x on-board Intel I354 interfaces which is identical to the forum post.

In my case eth0 through eth3 should be the on-board NICs, and eth4 and eth5 the PCIe card. Attempts to manually add interfaces to config.boot with correct hw-id's fails somewhere in the process. No order I've attempted results in successful configuration.

On a different Supermicro reference platform using the newer Atom C3000 series I also have 4 x on-board interfaces and a dual-port 40GbE PCIe card. I do not experience the interface ordering issue on this configuration.

In this case the PCIe card is using the Intel XL710 chipset and on-board devices make use of Intel 15c8.

Unknown Object (User) added a subscriber: Unknown Object (User).Sep 23 2019, 9:31 AM
rps added a comment.Dec 5 2019, 4:02 PM

Just a quick note that this issue remains in 1.2.4-epa1

This has made 1.2 unusable for my deployment and has kept me on 1.1. I'm sure others are running into it.

rps mentioned this in T577: Unconfigured Ethernet interface discovery partial failure on boot.Dec 18 2019, 3:03 PM
jjakob mentioned this in T2337: hw-id gone missing from interfaces after upgrade to 1.3-rolling-202004191028.Apr 19 2020, 12:55 PM
erkin set Is it a breaking change? to Unspecified (possibly destroys the router).Aug 31 2021, 7:16 PM
erkin set Issue type to Bug (incorrect behavior).
syncer edited projects, added VyOS 1.3 Equuleus (1.3.0); removed VyOS 1.3 Equuleus.Nov 6 2021, 11:25 AM
dmbaturin reassigned this task from UnicronNL to Unknown Object (User).Nov 11 2021, 2:20 PM
Unknown Object (User) closed this task as Resolved.Nov 11 2021, 6:42 PM

This issue should be fixed after these changes https://phabricator.vyos.net/T1970 (udevadm settle)
Tested on EdgeCore SAF51015I with generic ISOs.

syncer moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus (1.3.0) board.Aug 30 2022, 2:17 PM