NAME<\/a> ifrename \u2212 rename network interfaces based on various static criteria<\/p>\n ifrename [-c configfile] [-p] [-d] [-u] [-v] [-V] [-D] [-C] Ifrename<\/b> is a tool allowing you to assign a consistent name to each of your network interface.<\/p>\n By default, interface names are dynamic, and each network interface is assigned the first available name (eth0<\/i>, eth1<\/i>…). The order network interfaces are created may vary. For built-in interfaces, the kernel boot time enumeration may vary. For removable interface, the user may plug them in any order.<\/p>\n Ifrename<\/b> allow the user to decide what name a network interface will have. Ifrename<\/b> can use a variety of selectors<\/i> to specify how interface names match the network interfaces on the system, the most common selector is the interface MAC address<\/i>.<\/p>\n Ifrename<\/b> must be run before interfaces are brought up, which is why it\u2019s mostly useful in various scripts (init, hotplug) but is seldom used directly by the user. By default, ifrename<\/b> renames all present system interfaces using mappings defined in \/etc\/iftab<\/i>.<\/p>\n -c<\/b> configfile<\/i><\/p>\n Set the configuration file to be used (by default \/etc\/iftab<\/i>). The configuration file define the mapping between selectors and interface names, and is described in iftab<\/i>(5). -p<\/b><\/p>\n<\/td>\n Probe (load) kernel modules before renaming interfaces. By default ifrename<\/b> only check interfaces already loaded, and doesn\u2019t auto-load the required kernel modules. This option enables smooth integration with system not loading modules before calling ifrename<\/b>.<\/p>\n<\/td>\n<\/tr>\n -d<\/b><\/p>\n<\/td>\n Enable various Debian<\/b> specific hacks. Combined with -p<\/b>, only modules for interfaces specified in \/etc\/network\/interface<\/i> are loaded.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n -i<\/b> interface<\/i><\/p>\n Only rename the specified interface<\/i> as opposed to all interfaces on the system. The new interface name is printed.<\/p>\n -n<\/b> newname<\/i><\/p>\n When used with -i<\/i>, specify the new name of the interface. The list of mappings from the configuration file is bypassed, the interface specified with -i<\/i> is renamed directly to newname<\/i>. The new name may be a wildcard containing a single \u2019*\u2019. -t<\/b><\/p>\n<\/td>\n Enable name takeover support. This allow interface name swapping between two or more interfaces.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n Takeover enable an interface to \u2019steal\u2019 the name of another interface. This works only with kernel 2.6.X and if the other interface is down. Consequently, this is not compatible with Hotplug. The other interface is assigned a random name, but may be renamed later with \u2019ifrename\u2019. -u<\/b><\/p>\n<\/td>\n Enable udev<\/i> output mode. This enables proper integration of ifrename<\/b> in the udev<\/i> framework, udevd<\/b>(8) will use ifrename<\/b> to assign interface names present in \/etc\/iftab<\/i>. In this mode the output of ifrename can be parsed directly by udevd<\/b>(8) as an IMPORT action. This requires udev<\/i> version 107 or later.<\/p>\n<\/td>\n<\/tr>\n -D<\/b><\/p>\n<\/td>\n Dry-run mode. Ifrename won\u2019t change any interface, it will only print new interface name, if applicable, and return.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n In dry-run mode, interface name wildcards are not resolved. New interface name is printed, even if it is the same as the old name. -V<\/b><\/p>\n<\/td>\n Verbose mode. Ifrename will display internal results of parsing its configuration file and querying the interfaces selectors. Combined with the dry-run<\/i> option, this is a good way to debug complex configurations or trivial problems.<\/p>\n<\/td>\n<\/tr>\n -C<\/b><\/p>\n<\/td>\n Count matching interfaces. Display the number of interface matched, and return it as the exit status of ifrename.<\/p>\n<\/td>\n<\/tr>\n<\/table>\n The number of interfaces matched is the number of interface on the system for which a mapping was found in the config file (which is different from the number of interface renamed).<\/p>\n Jean Tourrilhes \u2212 jt@hpl.hp.com<\/p>\n
SYNOPSIS<\/a>
DESCRIPTION<\/a>
PARAMETERS<\/a>
AUTHOR<\/a>
FILES<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
ifrename [-c configfile] [-i interface] [-n newname]<\/b><\/p>\nDESCRIPTION <\/a> <\/h2>\n
PARAMETERS <\/a> <\/h2>\n
If configfile<\/i> is “-“, the configuration is read from stdin.<\/p>\n\n
\n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n
When used without -i<\/i>, rename interfaces by using only mappings that would rename them to newname<\/i>. The new name may not be a wildcard. This use of ifrename is discouraged, because inefficient (-n<\/i> without -i<\/i>). All the interfaces of the system need to be processed at each invocation, therefore in most case it is not faster than just letting ifrename renaming all of them (without both -n<\/i> and -i<\/i>).<\/p>\n\n
\n <\/td>\n \n <\/td>\n \n
The number of takeovers is limited to avoid circular loops, and therefore some complex multi-way name swapping situations may not be fully processed.
In any case, name swapping and the use of this feature is discouraged, and you are invited to choose unique and unambiguous names for your interfaces…<\/p>\n\n
\n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n
Be also aware that some selectors can only be read by root, for example those based on ethtool<\/b>), and will fail silently if run by a normal user. In other words, dry-run mode under a standard user may not give the expected result.<\/p>\n\n
\n <\/td>\n \n <\/td>\n \n \n <\/td>\n \n <\/td>\n \n AUTHOR <\/a> <\/h2>\n
FILES <\/a> <\/h2>\n