Why is my ethernet interface called enp0s10 instead of eth0? The 2019 Stack Overflow Developer...
Is every episode of "Where are my Pants?" identical?
different output for groups and groups USERNAME after adding a username to a group
Is it ok to offer lower paid work as a trial period before negotiating for a full-time job?
What's the point in a preamp?
What do I do when my TA workload is more than expected?
Can I visit the Trinity College (Cambridge) library and see some of their rare books
Match Roman Numerals
Why not take a picture of a closer black hole?
1960s short story making fun of James Bond-style spy fiction
Button changing its text & action. Good or terrible?
Presidential Pardon
"is" operation returns false even though two objects have same id
Is this wall load bearing? Blueprints and photos attached
Did the UK government pay "millions and millions of dollars" to try to snag Julian Assange?
How to read αἱμύλιος or when to aspirate
What is the role of 'For' here?
Can the Right Ascension and Argument of Perigee of a spacecraft's orbit keep varying by themselves with time?
Didn't get enough time to take a Coding Test - what to do now?
Is there a writing software that you can sort scenes like slides in PowerPoint?
Homework question about an engine pulling a train
Working through the single responsibility principle (SRP) in Python when calls are expensive
Identify 80s or 90s comics with ripped creatures (not dwarves)
University's motivation for having tenure-track positions
Single author papers against my advisor's will?
Why is my ethernet interface called enp0s10 instead of eth0?
The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
2019 Community Moderator Election Resultseth0: ERROR while getting interface flags: No such devicedisable persistent network device namingWhat's the difference between `en0` and `eth0`?Why is my nic ethN suddenly called p18pN?No network capabilities in CentOSMy ethernet device has strange name on UbuntuHow to enable “Predictable Network Interface Names”?Bridging ethernet interfaceHow to setup VLAN on same subnet as Ethernet?What does the eth0 interface name mean in Linux?Problem with network interfaceifconfig ethernet (eth0) no data floweth0: supported portsWhy can't set eth0 to be my target?Packets not moving through linux ethernet bridgeWhy my Raspberry pi receive no packets using Ethernet?Why does Linux network traffic only go through eth0?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
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
add a comment |
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
4
ifconfig
is deprecated. Think about moving toip
fromiproute2
soon.
– solsTiCe
Jun 13 '15 at 8:21
add a comment |
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
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
linux networking udev ethernet
edited Feb 6 '18 at 2:11
muru
37.6k589165
37.6k589165
asked Jun 4 '14 at 15:33
Nico RodsevichNico Rodsevich
440159
440159
4
ifconfig
is deprecated. Think about moving toip
fromiproute2
soon.
– solsTiCe
Jun 13 '15 at 8:21
add a comment |
4
ifconfig
is deprecated. Think about moving toip
fromiproute2
soon.
– solsTiCe
Jun 13 '15 at 8:21
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
add a comment |
2 Answers
2
active
oldest
votes
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
6
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 |
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
5
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
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
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
6
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 |
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
6
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 |
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
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
edited Jun 12 '15 at 23:48
answered Jun 4 '14 at 15:43
BraiamBraiam
23.8k2078143
23.8k2078143
6
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 |
6
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
6
6
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 |
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
5
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |
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
5
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |
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
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 7 hours ago
answered Sep 23 '16 at 12:38
DIG mblDIG mbl
72165
72165
5
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
add a comment |
5
Came looking for this.
– ffledgling
Mar 7 '17 at 8:38
5
5
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 |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
4
ifconfig
is deprecated. Think about moving toip
fromiproute2
soon.– solsTiCe
Jun 13 '15 at 8:21