Why is my interface now wlp2s0 instead of wlan0? [duplicate]
up vote
20
down vote
favorite
This question already has an answer here:
Network interface name changes after update to 15.10 - udev changes
6 answers
Everything works fine I just want to know why would my interface change to wlp2s0 by default instead of the usual wlan0
networking wireless interface
marked as duplicate by bain, Pilot6, David Foerster, Charles Green, Eric Carvalho Jan 21 '16 at 4:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
20
down vote
favorite
This question already has an answer here:
Network interface name changes after update to 15.10 - udev changes
6 answers
Everything works fine I just want to know why would my interface change to wlp2s0 by default instead of the usual wlan0
networking wireless interface
marked as duplicate by bain, Pilot6, David Foerster, Charles Green, Eric Carvalho Jan 21 '16 at 4:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
up vote
20
down vote
favorite
up vote
20
down vote
favorite
This question already has an answer here:
Network interface name changes after update to 15.10 - udev changes
6 answers
Everything works fine I just want to know why would my interface change to wlp2s0 by default instead of the usual wlan0
networking wireless interface
This question already has an answer here:
Network interface name changes after update to 15.10 - udev changes
6 answers
Everything works fine I just want to know why would my interface change to wlp2s0 by default instead of the usual wlan0
This question already has an answer here:
Network interface name changes after update to 15.10 - udev changes
6 answers
networking wireless interface
networking wireless interface
asked Nov 24 '15 at 23:45
Pepe
3432616
3432616
marked as duplicate by bain, Pilot6, David Foerster, Charles Green, Eric Carvalho Jan 21 '16 at 4:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
marked as duplicate by bain, Pilot6, David Foerster, Charles Green, Eric Carvalho Jan 21 '16 at 4:09
This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
23
down vote
accepted
A new naming scheme has been introduced, to solve problems that arose from the old (eth0, wlan0) naming standards.
Here is a short introduction and explanation of the concept:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Basically, the first two letter describe the type of interface. 'wl' for wlan, 'en' for ethernet. The following code is often a description of the physical placement of the device in your computer - p2 is likely PCI bus 2, and s0 is likely slot 0.
as kyodake pointed out, this new standard was introduced when Ubuntu moved to systemd.
add a comment |
up vote
0
down vote
Why Ubuntu with systemd have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's the default.
The following different naming schemes for network interfaces are now supported by udev natively:
(1) Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
(2) Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
(3) Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
(4) Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
(5) Classic, unpredictable kernel-native ethX naming (example: eth0)
By default, systemd will now name interfaces following policy:
(1) if that information from the firmware is applicable and available, falling back to:
(2) if that information from the firmware is applicable and available, falling back to:
(3) if applicable, falling back to:
(5) in all other cases.
Policy (4) is not used by default, but is available if the user chooses so.
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
23
down vote
accepted
A new naming scheme has been introduced, to solve problems that arose from the old (eth0, wlan0) naming standards.
Here is a short introduction and explanation of the concept:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Basically, the first two letter describe the type of interface. 'wl' for wlan, 'en' for ethernet. The following code is often a description of the physical placement of the device in your computer - p2 is likely PCI bus 2, and s0 is likely slot 0.
as kyodake pointed out, this new standard was introduced when Ubuntu moved to systemd.
add a comment |
up vote
23
down vote
accepted
A new naming scheme has been introduced, to solve problems that arose from the old (eth0, wlan0) naming standards.
Here is a short introduction and explanation of the concept:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Basically, the first two letter describe the type of interface. 'wl' for wlan, 'en' for ethernet. The following code is often a description of the physical placement of the device in your computer - p2 is likely PCI bus 2, and s0 is likely slot 0.
as kyodake pointed out, this new standard was introduced when Ubuntu moved to systemd.
add a comment |
up vote
23
down vote
accepted
up vote
23
down vote
accepted
A new naming scheme has been introduced, to solve problems that arose from the old (eth0, wlan0) naming standards.
Here is a short introduction and explanation of the concept:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Basically, the first two letter describe the type of interface. 'wl' for wlan, 'en' for ethernet. The following code is often a description of the physical placement of the device in your computer - p2 is likely PCI bus 2, and s0 is likely slot 0.
as kyodake pointed out, this new standard was introduced when Ubuntu moved to systemd.
A new naming scheme has been introduced, to solve problems that arose from the old (eth0, wlan0) naming standards.
Here is a short introduction and explanation of the concept:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
Basically, the first two letter describe the type of interface. 'wl' for wlan, 'en' for ethernet. The following code is often a description of the physical placement of the device in your computer - p2 is likely PCI bus 2, and s0 is likely slot 0.
as kyodake pointed out, this new standard was introduced when Ubuntu moved to systemd.
answered Jan 20 '16 at 0:59
sverker wahlin
408210
408210
add a comment |
add a comment |
up vote
0
down vote
Why Ubuntu with systemd have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's the default.
The following different naming schemes for network interfaces are now supported by udev natively:
(1) Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
(2) Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
(3) Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
(4) Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
(5) Classic, unpredictable kernel-native ethX naming (example: eth0)
By default, systemd will now name interfaces following policy:
(1) if that information from the firmware is applicable and available, falling back to:
(2) if that information from the firmware is applicable and available, falling back to:
(3) if applicable, falling back to:
(5) in all other cases.
Policy (4) is not used by default, but is available if the user chooses so.
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
add a comment |
up vote
0
down vote
Why Ubuntu with systemd have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's the default.
The following different naming schemes for network interfaces are now supported by udev natively:
(1) Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
(2) Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
(3) Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
(4) Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
(5) Classic, unpredictable kernel-native ethX naming (example: eth0)
By default, systemd will now name interfaces following policy:
(1) if that information from the firmware is applicable and available, falling back to:
(2) if that information from the firmware is applicable and available, falling back to:
(3) if applicable, falling back to:
(5) in all other cases.
Policy (4) is not used by default, but is available if the user chooses so.
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
add a comment |
up vote
0
down vote
up vote
0
down vote
Why Ubuntu with systemd have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's the default.
The following different naming schemes for network interfaces are now supported by udev natively:
(1) Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
(2) Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
(3) Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
(4) Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
(5) Classic, unpredictable kernel-native ethX naming (example: eth0)
By default, systemd will now name interfaces following policy:
(1) if that information from the firmware is applicable and available, falling back to:
(2) if that information from the firmware is applicable and available, falling back to:
(3) if applicable, falling back to:
(5) in all other cases.
Policy (4) is not used by default, but is available if the user chooses so.
Why Ubuntu with systemd have added native support for a number of different naming policies into systemd/udevd proper and made a scheme similar to biosdevname's the default.
The following different naming schemes for network interfaces are now supported by udev natively:
(1) Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
(2) Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
(3) Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
(4) Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
(5) Classic, unpredictable kernel-native ethX naming (example: eth0)
By default, systemd will now name interfaces following policy:
(1) if that information from the firmware is applicable and available, falling back to:
(2) if that information from the firmware is applicable and available, falling back to:
(3) if applicable, falling back to:
(5) in all other cases.
Policy (4) is not used by default, but is available if the user chooses so.
answered Nov 25 '15 at 0:11
kyodake
9,57011932
9,57011932
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
add a comment |
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
I don't really understand this.
– Pepe
Nov 28 '15 at 6:28
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
Ubuntu with systemd have added native support for a number of different naming policies
– kyodake
Nov 28 '15 at 13:31
add a comment |