Re: [PROPOSAL]: Alias names for network interfaces

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Narendra_K@xxxxxxxx wrote:
Also, in case of large scale image based deployment scenarios embedding
HWADDR in config files or udev rules is not an option. Though HWADDR
helps in ensuring persistency in naming, it doesn't help in achieving expected
naming.

HWADDR is not the only way to use udev to name a network interface. You can do something like:

SUBSYSTEM=="net", SUBSYSTEMS=="pci", KERNELS=="0000:04:00.0", NAME="eth0"
SUBSYSTEM=="net", SUBSYSTEMS=="pci", KERNELS=="0000:06:00.0", NAME="eth1"



--
**********************************************************************
Marco Innocenti              Dipartimento Sistemi E Tecnologie
CINECA                       phone:+39 0516171553 / fax:+39 0516132198
Via Magnanelli 6/3           e-mail: innocenti@xxxxxxxxx
40033 Casalecchio di Reno    Bologna (Italia)
**********************************************************************
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netfitler Users]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux