Why is my ethernet interface called enp0s10 instead of eth0?
Clash Royale CLAN TAG#URR8PPP
up vote
34
down vote
favorite
12
When I run ifconfig -a, I only get lo and enp0s10 interfaces, not the classical eth0
What does enp0s10 mean? Why is there no eth0?
linux networking udev ethernet
edited Feb 6 at 2:11
muru
33.2k576140
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
add a comment |Â
up vote
34
down vote
favorite
12
When I run ifconfig -a, I only get lo and enp0s10 interfaces, not the classical eth0
What does enp0s10 mean? Why is there no eth0?
linux networking udev ethernet
edited Feb 6 at 2:11
muru
33.2k576140
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
4
ifconfigis deprecated. Think about moving toipfromiproute2soon.
– solsTiCe
Jun 13 '15 at 8:21
1
predictable interface names as is mentioned below. The rpm package that causes this is biosdevname. I often red flag it to prevent its install, I prefer eth0... and ifconfig!
– ron
Aug 1 at 14:59
add a comment |Â
up vote
34
down vote
favorite
12
up vote
34
down vote
favorite
12
12
When I run ifconfig -a, I only get lo and enp0s10 interfaces, not the classical eth0
What does enp0s10 mean? Why is there no eth0?
linux networking udev ethernet
edited Feb 6 at 2:11
muru
33.2k576140
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
When I run ifconfig -a, I only get lo and enp0s10 interfaces, not the classical eth0
What does enp0s10 mean? Why is there no eth0?
linux networking udev ethernet
edited Feb 6 at 2:11
muru
33.2k576140
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
edited Feb 6 at 2:11
muru
33.2k576140
edited Feb 6 at 2:11
muru
33.2k576140
edited Feb 6 at 2:11
muru
33.2k576140
33.2k576140
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
asked Jun 4 '14 at 15:33
Nico Rodsevich
335139
335139
4
ifconfigis deprecated. Think about moving toipfromiproute2soon.
– solsTiCe
Jun 13 '15 at 8:21
1
predictable interface names as is mentioned below. The rpm package that causes this is biosdevname. I often red flag it to prevent its install, I prefer eth0... and ifconfig!
– ron
Aug 1 at 14:59
add a comment |Â
4
ifconfigis deprecated. Think about moving toipfromiproute2soon.
– solsTiCe
Jun 13 '15 at 8:21
1
predictable interface names as is mentioned below. The rpm package that causes this is biosdevname. I often red flag it to prevent its install, I prefer eth0... and ifconfig!
– ron
Aug 1 at 14:59
4
4
ifconfig is deprecated. Think about moving to ip from iproute2 soon.– solsTiCe
Jun 13 '15 at 8:21
ifconfig is deprecated. Think about moving to ip from iproute2 soon.– solsTiCe
Jun 13 '15 at 8:21
1
1
predictable interface names as is mentioned below. The rpm package that causes this is biosdevname. I often red flag it to prevent its install, I prefer eth0... and ifconfig!
– ron
Aug 1 at 14:59
predictable interface names as is mentioned below. The rpm package that causes this is biosdevname. I often red flag it to prevent its install, I prefer eth0... and ifconfig!
– ron
Aug 1 at 14:59
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
33
down vote
accepted
That's a change in how now udevd assigns names to ethernet devices. Now your devices use the "Predictable Interface Names", which are based on (and quoting the sources):
- Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
- Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
- Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
- Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
- Classic, unpredictable kernel-native ethX naming (example: eth0)
The why's this changed is documented in the systemd freedesktop.org page, along with the method to disable this:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
or if you use older versions:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
2
Following the freedesktop,org link, the main point is:The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...
– lepe
Oct 17 '16 at 2:43
add a comment |Â
up vote
30
down vote
Answer on "What does enp0s10 means?" question:
enp0s10:
v | |
en | | -- ethernet
v |
p0 | -- bus number (0)
v
s10 -- slot number (10)
Source: udev-builtin-net_id.c on GitHub
edited Aug 1 at 11:06
hashlash
32
answered Sep 23 '16 at 12:38
DIG mbl
46155
4
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
33
down vote
accepted
That's a change in how now udevd assigns names to ethernet devices. Now your devices use the "Predictable Interface Names", which are based on (and quoting the sources):
- Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
- Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
- Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
- Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
- Classic, unpredictable kernel-native ethX naming (example: eth0)
The why's this changed is documented in the systemd freedesktop.org page, along with the method to disable this:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
or if you use older versions:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
2
Following the freedesktop,org link, the main point is:The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...
– lepe
Oct 17 '16 at 2:43
add a comment |Â
up vote
33
down vote
accepted
That's a change in how now udevd assigns names to ethernet devices. Now your devices use the "Predictable Interface Names", which are based on (and quoting the sources):
- Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
- Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
- Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
- Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
- Classic, unpredictable kernel-native ethX naming (example: eth0)
The why's this changed is documented in the systemd freedesktop.org page, along with the method to disable this:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
or if you use older versions:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
2
Following the freedesktop,org link, the main point is:The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...
– lepe
Oct 17 '16 at 2:43
add a comment |Â
up vote
33
down vote
accepted
up vote
33
down vote
accepted
That's a change in how now udevd assigns names to ethernet devices. Now your devices use the "Predictable Interface Names", which are based on (and quoting the sources):
- Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
- Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
- Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
- Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
- Classic, unpredictable kernel-native ethX naming (example: eth0)
The why's this changed is documented in the systemd freedesktop.org page, along with the method to disable this:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
or if you use older versions:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
That's a change in how now udevd assigns names to ethernet devices. Now your devices use the "Predictable Interface Names", which are based on (and quoting the sources):
- Names incorporating Firmware/BIOS provided index numbers for on-board devices (example: eno1)
- Names incorporating Firmware/BIOS provided PCI Express hotplug slot index numbers (example: ens1)
- Names incorporating physical/geographical location of the connector of the hardware (example: enp2s0)
- Names incorporating the interfaces's MAC address (example: enx78e7d1ea46da)
- Classic, unpredictable kernel-native ethX naming (example: eth0)
The why's this changed is documented in the systemd freedesktop.org page, along with the method to disable this:
ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules
or if you use older versions:
ln -s /dev/null /etc/udev/rules.d/80-net-name-slot.rules
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
edited Jun 12 '15 at 23:48
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
answered Jun 4 '14 at 15:43
Braiam
22.3k1969130
22.3k1969130
2
Following the freedesktop,org link, the main point is:The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...
– lepe
Oct 17 '16 at 2:43
add a comment |Â
2
Following the freedesktop,org link, the main point is:The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...
– lepe
Oct 17 '16 at 2:43
2
2
Following the freedesktop,org link, the main point is:
The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...– lepe
Oct 17 '16 at 2:43
Following the freedesktop,org link, the main point is:
The classic naming scheme for network interfaces applied by the kernel is to simply assign names beginning with "eth" to all interfaces as they are probed by the drivers. As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names is generally not fixed anymore and it might very well happen that "eth0" on one boot ends up being "eth1" on the next. This can have serious security implications...– lepe
Oct 17 '16 at 2:43
add a comment |Â
up vote
30
down vote
Answer on "What does enp0s10 means?" question:
enp0s10:
v | |
en | | -- ethernet
v |
p0 | -- bus number (0)
v
s10 -- slot number (10)
Source: udev-builtin-net_id.c on GitHub
edited Aug 1 at 11:06
hashlash
32
answered Sep 23 '16 at 12:38
DIG mbl
46155
4
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |Â
up vote
30
down vote
Answer on "What does enp0s10 means?" question:
enp0s10:
v | |
en | | -- ethernet
v |
p0 | -- bus number (0)
v
s10 -- slot number (10)
Source: udev-builtin-net_id.c on GitHub
edited Aug 1 at 11:06
hashlash
32
answered Sep 23 '16 at 12:38
DIG mbl
46155
4
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |Â
up vote
30
down vote
up vote
30
down vote
Answer on "What does enp0s10 means?" question:
enp0s10:
v | |
en | | -- ethernet
v |
p0 | -- bus number (0)
v
s10 -- slot number (10)
Source: udev-builtin-net_id.c on GitHub
edited Aug 1 at 11:06
hashlash
32
answered Sep 23 '16 at 12:38
DIG mbl
46155
Answer on "What does enp0s10 means?" question:
enp0s10:
v | |
en | | -- ethernet
v |
p0 | -- bus number (0)
v
s10 -- slot number (10)
Source: udev-builtin-net_id.c on GitHub
edited Aug 1 at 11:06
hashlash
32
answered Sep 23 '16 at 12:38
DIG mbl
46155
edited Aug 1 at 11:06
hashlash
32
edited Aug 1 at 11:06
hashlash
32
edited Aug 1 at 11:06
hashlash
32
32
answered Sep 23 '16 at 12:38
DIG mbl
46155
answered Sep 23 '16 at 12:38
DIG mbl
46155
answered Sep 23 '16 at 12:38
DIG mbl
46155
46155
4
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |Â
4
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
4
4
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f134483%2fwhy-is-my-ethernet-interface-called-enp0s10-instead-of-eth0%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
4
ifconfigis deprecated. Think about moving toipfromiproute2soon.– solsTiCe
Jun 13 '15 at 8:21
1
predictable interface names as is mentioned below. The rpm package that causes this is biosdevname. I often red flag it to prevent its install, I prefer eth0... and ifconfig!
– ron
Aug 1 at 14:59