Debian changing eno0 to eth0 by itself
up vote
0
down vote
favorite
I have Proxmox on site, based on Debian 9.6.
When freshly installed, I had 3 interfaces: eno0, enp0s1 and enp0s2, the network cable is plugged on the physical port marked 0 (zero) on the server, which corresponded to eno0.
On first install, I followed some guide online on how to declare the vmbr0 interface bridged to eno0, only editing /etc/network/interfaces, which I did and it was perfect (all interfaces as manual, vmbr0 as static and the bridge).
The system is often rebooted because of power loss in my country, and our general UPS out of service and waiting to be repaired. One day, the system rebooted and the network interfaces were renamed from what is written above? To eth*, the plugged in port becoming eth0.
The next day, new loss, the interface became eth1. I’m the only root/sudoers around, I didn’t upgrade anything. I’ve read that eth* is the old naming scheme, it became en..., but I don’t understand how it reversed and more importantly, how the numbers are switching.
debian network-interface proxmox
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
asked Nov 22 at 9:58
Max13
13516
add a comment |
up vote
0
down vote
favorite
I have Proxmox on site, based on Debian 9.6.
When freshly installed, I had 3 interfaces: eno0, enp0s1 and enp0s2, the network cable is plugged on the physical port marked 0 (zero) on the server, which corresponded to eno0.
On first install, I followed some guide online on how to declare the vmbr0 interface bridged to eno0, only editing /etc/network/interfaces, which I did and it was perfect (all interfaces as manual, vmbr0 as static and the bridge).
The system is often rebooted because of power loss in my country, and our general UPS out of service and waiting to be repaired. One day, the system rebooted and the network interfaces were renamed from what is written above? To eth*, the plugged in port becoming eth0.
The next day, new loss, the interface became eth1. I’m the only root/sudoers around, I didn’t upgrade anything. I’ve read that eth* is the old naming scheme, it became en..., but I don’t understand how it reversed and more importantly, how the numbers are switching.
debian network-interface proxmox
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
asked Nov 22 at 9:58
Max13
13516
Very briefly: The kernel createsethN,udevrules rename this to the newer predictable network interface names.Systemdmay also have its finger in there in addition. So probably you have someudevrules that are not firing. You can also write customudevrules (google) for your own naming scheme, if that helps.
– dirkt
Nov 22 at 10:18
@dirkt So, the only outcome would be to write my custom rules?
– Max13
Nov 23 at 13:02
There's a number of ways to do it: Write your own custom rules, find out why the existing rules didn't work on reboot, ...
– dirkt
Nov 23 at 13:04
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have Proxmox on site, based on Debian 9.6.
When freshly installed, I had 3 interfaces: eno0, enp0s1 and enp0s2, the network cable is plugged on the physical port marked 0 (zero) on the server, which corresponded to eno0.
On first install, I followed some guide online on how to declare the vmbr0 interface bridged to eno0, only editing /etc/network/interfaces, which I did and it was perfect (all interfaces as manual, vmbr0 as static and the bridge).
The system is often rebooted because of power loss in my country, and our general UPS out of service and waiting to be repaired. One day, the system rebooted and the network interfaces were renamed from what is written above? To eth*, the plugged in port becoming eth0.
The next day, new loss, the interface became eth1. I’m the only root/sudoers around, I didn’t upgrade anything. I’ve read that eth* is the old naming scheme, it became en..., but I don’t understand how it reversed and more importantly, how the numbers are switching.
debian network-interface proxmox
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
asked Nov 22 at 9:58
Max13
13516
I have Proxmox on site, based on Debian 9.6.
When freshly installed, I had 3 interfaces: eno0, enp0s1 and enp0s2, the network cable is plugged on the physical port marked 0 (zero) on the server, which corresponded to eno0.
On first install, I followed some guide online on how to declare the vmbr0 interface bridged to eno0, only editing /etc/network/interfaces, which I did and it was perfect (all interfaces as manual, vmbr0 as static and the bridge).
The system is often rebooted because of power loss in my country, and our general UPS out of service and waiting to be repaired. One day, the system rebooted and the network interfaces were renamed from what is written above? To eth*, the plugged in port becoming eth0.
The next day, new loss, the interface became eth1. I’m the only root/sudoers around, I didn’t upgrade anything. I’ve read that eth* is the old naming scheme, it became en..., but I don’t understand how it reversed and more importantly, how the numbers are switching.
debian network-interface proxmox
debian network-interface proxmox
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
asked Nov 22 at 9:58
Max13
13516
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
asked Nov 22 at 9:58
Max13
13516
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
edited Nov 22 at 10:27
Rui F Ribeiro
38.3k1475126
38.3k1475126
asked Nov 22 at 9:58
Max13
13516
asked Nov 22 at 9:58
Max13
13516
asked Nov 22 at 9:58
Max13
13516
13516
Very briefly: The kernel createsethN,udevrules rename this to the newer predictable network interface names.Systemdmay also have its finger in there in addition. So probably you have someudevrules that are not firing. You can also write customudevrules (google) for your own naming scheme, if that helps.
– dirkt
Nov 22 at 10:18
@dirkt So, the only outcome would be to write my custom rules?
– Max13
Nov 23 at 13:02
There's a number of ways to do it: Write your own custom rules, find out why the existing rules didn't work on reboot, ...
– dirkt
Nov 23 at 13:04
add a comment |
Very briefly: The kernel createsethN,udevrules rename this to the newer predictable network interface names.Systemdmay also have its finger in there in addition. So probably you have someudevrules that are not firing. You can also write customudevrules (google) for your own naming scheme, if that helps.
– dirkt
Nov 22 at 10:18
@dirkt So, the only outcome would be to write my custom rules?
– Max13
Nov 23 at 13:02
There's a number of ways to do it: Write your own custom rules, find out why the existing rules didn't work on reboot, ...
– dirkt
Nov 23 at 13:04
Very briefly: The kernel creates
ethN, udev rules rename this to the newer predictable network interface names. Systemd may also have its finger in there in addition. So probably you have some udev rules that are not firing. You can also write custom udev rules (google) for your own naming scheme, if that helps.– dirkt
Nov 22 at 10:18
Very briefly: The kernel creates
ethN, udev rules rename this to the newer predictable network interface names. Systemd may also have its finger in there in addition. So probably you have some udev rules that are not firing. You can also write custom udev rules (google) for your own naming scheme, if that helps.– dirkt
Nov 22 at 10:18
@dirkt So, the only outcome would be to write my custom rules?
– Max13
Nov 23 at 13:02
@dirkt So, the only outcome would be to write my custom rules?
– Max13
Nov 23 at 13:02
There's a number of ways to do it: Write your own custom rules, find out why the existing rules didn't work on reboot, ...
– dirkt
Nov 23 at 13:04
There's a number of ways to do it: Write your own custom rules, find out why the existing rules didn't work on reboot, ...
– dirkt
Nov 23 at 13:04
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f483405%2fdebian-changing-eno0-to-eth0-by-itself%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
Very briefly: The kernel creates
ethN,udevrules rename this to the newer predictable network interface names.Systemdmay also have its finger in there in addition. So probably you have someudevrules that are not firing. You can also write customudevrules (google) for your own naming scheme, if that helps.– dirkt
Nov 22 at 10:18
@dirkt So, the only outcome would be to write my custom rules?
– Max13
Nov 23 at 13:02
There's a number of ways to do it: Write your own custom rules, find out why the existing rules didn't work on reboot, ...
– dirkt
Nov 23 at 13:04