Page MenuHomeVyOS Platform
Create Task
Maniphest T1903

Implementation udev predefined interface naming
Closed, ResolvedPublic
Actions

Description

Exist many problem with order interfaces for some HW and VM. e.g. if VMWare use more 4 interfaces, then interfaces sequence will be various.
We can use udev rules for these and other platforms.
Detect by dmi/board_name or dmi/sys_vendor and following rules

For VMWare

ATTR{[dmi/id]sys_vendor}!="VMware, Inc.", GOTO="end_vmware_nic"

ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:0b:00.0", ENV{VYOS_IFNAME}="eth0"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:13:00.0", ENV{VYOS_IFNAME}="eth1"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:1b:00.0", ENV{VYOS_IFNAME}="eth2"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:04:00.0", ENV{VYOS_IFNAME}="eth3"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:0c:00.0", ENV{VYOS_IFNAME}="eth4"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:14:00.0", ENV{VYOS_IFNAME}="eth5"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:1c:00.0", ENV{VYOS_IFNAME}="eth6"

LABEL="end_vmware_nic"

For Edge-Core model SAF51015I-0318-EC

ATTR{[dmi/id]board_name}!="SAF51015I-0318-EC", GOTO="end_ec_nic"

ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:02:00.0", ENV{VYOS_IFNAME}="eth1"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:03:00.0", ENV{VYOS_IFNAME}="eth2"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:04:00.0", ENV{VYOS_IFNAME}="eth3"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:05:00.0", ENV{VYOS_IFNAME}="eth4"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:06:00.0", ENV{VYOS_IFNAME}="eth5"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:06:00.1", ENV{VYOS_IFNAME}="eth6"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:06:00.2", ENV{VYOS_IFNAME}="eth7"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:06:00.3", ENV{VYOS_IFNAME}="eth8"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:0a:00.0", ENV{VYOS_IFNAME}="eth9"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:0a:00.1", ENV{VYOS_IFNAME}="eth10"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:0b:00.0", ENV{VYOS_IFNAME}="eth11"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:0b:00.1", ENV{VYOS_IFNAME}="eth12"

LABEL="end_ec_nic"

Details

Version
1.2.4-epa1
Is it a breaking change?
Unspecified (possibly destroys the router)

Related Objects

Event Timeline

Unknown Object (User) created this task.Dec 24 2019, 1:57 PM
Unknown Object (User) changed the task status from Open to In progress.
Unknown Object (User) added a comment.EditedDec 24 2019, 2:01 PM

PR for CRUX branch https://github.com/vyos/vyatta-cfg-system/pull/112

Unknown Object (User) added a comment.Dec 25 2019, 8:02 AM

Note: If we have interfaces with description on device panel, like WAN, DMZ, etc, we can use predefined alias in this case.

ec.jpg (1×4 px, 2 MB)

Simple rules:

vyos@QAT-R1:~$ sudo cat /lib/udev/rules.d/64-vyos-SAF51003I-net.rules 
ATTR{[dmi/id]board_name}!="SAF51003I", GOTO="end_ec_nic"

ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:02:00.0", ENV{VYOS_IFNAME}="eth1",  ATTR{ifalias}="LAN1"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:02:00.1", ENV{VYOS_IFNAME}="eth2",  ATTR{ifalias}="LAN2"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:02:00.2", ENV{VYOS_IFNAME}="eth3",  ATTR{ifalias}="LAN3"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:02:00.3", ENV{VYOS_IFNAME}="eth4",  ATTR{ifalias}="LAN4"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:05:00.0", ENV{VYOS_IFNAME}="eth5",  ATTR{ifalias}="LAN5"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:05:00.1", ENV{VYOS_IFNAME}="eth6",  ATTR{ifalias}="LAN6"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:05:00.2", ENV{VYOS_IFNAME}="eth7",  ATTR{ifalias}="LAN7"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:05:00.3", ENV{VYOS_IFNAME}="eth8",  ATTR{ifalias}="LAN8"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:08:00.0", ENV{VYOS_IFNAME}="eth9",  ATTR{ifalias}="DMZ"
ACTION=="add", SUBSYSTEM=="net", KERNELS=="0000:08:00.1", ENV{VYOS_IFNAME}="eth10", ATTR{ifalias}="WAN"

LABEL="end_ec_nic"

show interfaces will display helpful interfaces aliases.

vyos@QAT-R1:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface        IP Address                        S/L  Description
---------        ----------                        ---  -----------
eth1             -                                 u/D  LAN1 
eth2             -                                 u/D  LAN2 
eth3             -                                 u/D  LAN3 
eth4             -                                 u/D  LAN4 
eth5             -                                 u/D  LAN5 
eth6             -                                 u/D  LAN6 
eth7             -                                 u/D  LAN7 
eth8             -                                 u/D  LAN8 
eth9             -                                 u/D  DMZ 
eth10            -                                 u/u  WAN 
lo               127.0.0.1/8                       u/u  
                 ::1/128
Unknown Object (User) added a comment.Dec 26 2019, 1:18 PM

Successfully tested on 1.3. PR for current branch https://github.com/vyos/vyatta-cfg-system/pull/113

jjakob subscribed.Dec 26 2019, 7:09 PM

Is this only for crux or also for equuleus? There is also
https://phabricator.vyos.net/T1499
https://phabricator.vyos.net/T1584
https://phabricator.vyos.net/T291

Unknown Object (User) added a comment.Dec 26 2019, 7:12 PM

@jjakob for equuleus too, wait for merge PR. We have also some ideas how we can improve net naming, and fix issues with renameX interfaces after boot.

pasik subscribed.Dec 27 2019, 9:55 AM
syncer moved this task from Needs Triage to In Progress on the VyOS 1.2 Crux (VyOS 1.2.5) board.Jan 1 2020, 1:10 PM
syncer closed this task as Resolved.Jan 1 2020, 1:13 PM
syncer edited projects, added VyOS 1.2 Crux (VyOS 1.2.4); removed VyOS 1.2 Crux (VyOS 1.2.5).
syncer moved this task from Need Triage to Finished on the VyOS 1.3 Equuleus board.
syncer moved this task from Needs Triage to Finished on the VyOS 1.2 Crux (VyOS 1.2.4) board.
dmbaturin removed a project: VyOS 1.3 Equuleus.Sep 10 2021, 2:25 PM