Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Interface names
Interface names
Hello
Iam using fresh installation of Debian 9 on older server and i noticed strange behaviour while naming network interfaces. Iam not looking for answer how to rename them using 70-persistent-net.rules after bit of a change in grub, but iam mainly interested why the naming convention is not applies here ate all:
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:**********:42 brd ff:ff:ff:ff:ff:ff
3: rename3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:*******:43 brd ff:ff:ff:ff:ff:ff
4: rename4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ************:44 brd ff:ff:ff:ff:ff:ff
inet 10.1.***** brd 10.1.***** scope global rename4
valid_lft forever preferred_lft forever
inet6 ************* scope link
valid_lft forever preferred_lft forever
5: rename5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether *********:45 brd ff:ff:ff:ff:ff:ff
Not sure where eno1 is coming from but mainly, why are interfaces named "rename". Each of them are unique interfaces with MAC addreses, oddly same until las digit which is incremented by one (ergo :42 / :43 / :44 ....). Everything is working normally, you can see rename4 is normally obtaining address via DHCP (which needed to be added manually to network/interface, since sometimes after reboot he did not regained it, sometime it did, but thats just FYI, to be complete)
I would not mind ens**, iam just wondering what is this about? It was not tampered with, its simply state after install.
Iam using fresh installation of Debian 9 on older server and i noticed strange behaviour while naming network interfaces. Iam not looking for answer how to rename them using 70-persistent-net.rules after bit of a change in grub, but iam mainly interested why the naming convention is not applies here ate all:
2: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:**********:42 brd ff:ff:ff:ff:ff:ff
3: rename3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether 00:*******:43 brd ff:ff:ff:ff:ff:ff
4: rename4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether ************:44 brd ff:ff:ff:ff:ff:ff
inet 10.1.***** brd 10.1.***** scope global rename4
valid_lft forever preferred_lft forever
inet6 ************* scope link
valid_lft forever preferred_lft forever
5: rename5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
link/ether *********:45 brd ff:ff:ff:ff:ff:ff
Not sure where eno1 is coming from but mainly, why are interfaces named "rename". Each of them are unique interfaces with MAC addreses, oddly same until las digit which is incremented by one (ergo :42 / :43 / :44 ....). Everything is working normally, you can see rename4 is normally obtaining address via DHCP (which needed to be added manually to network/interface, since sometimes after reboot he did not regained it, sometime it did, but thats just FYI, to be complete)
I would not mind ens**, iam just wondering what is this about? It was not tampered with, its simply state after install.
Re: Interface names
This might help.chargejan wrote:I would not mind ens**, iam just wondering what is this about? It was not tampered with, its simply state after install.
https://www.freedesktop.org/wiki/Softwa ... faceNames/
Did you add your own rules to udev?
Re: Interface names
I did not, i now realize the last sentence was bit off my goal. I know there is a lot of people interested exactly why new convention needed to be adopted and why it look as it does, but iam really more baffled why my interfaces are named "rename2" etc. by default, which looks odd. I did not played with udev at all.
Re: Interface names
just this
https://www.supermicro.com/products/mot ... -ln4f_.cfm
Intel® i350 Quad Port Gigabit Ethernet
Virtual Machine Device Queues reduce I/O overhead
Supports 10BASE-T, 100BASE-TX, and 1000BASE-T, RJ45 output
1x Realtek RTL8201N PHY (dedicated IPMI)
I may just settle down with the naming it gave, but would like to have answer for my senior admin since it baffled him too )
https://www.supermicro.com/products/mot ... -ln4f_.cfm
Intel® i350 Quad Port Gigabit Ethernet
Virtual Machine Device Queues reduce I/O overhead
Supports 10BASE-T, 100BASE-TX, and 1000BASE-T, RJ45 output
1x Realtek RTL8201N PHY (dedicated IPMI)
I may just settle down with the naming it gave, but would like to have answer for my senior admin since it baffled him too )
Re: Interface names
adding this:to your linux boot command will get you back those old interface names like eth1 etc.
Code: Select all
net.ifnames=0
- Head_on_a_Stick
- Posts: 14114
- Joined: 2014-06-01 17:46
- Location: London, England
- Has thanked: 81 times
- Been thanked: 133 times
Re: Interface names
Do you have /etc/udev/rules.d/70-persistent-net.rules on your system?chargejan wrote:iam really more baffled why my interfaces are named "rename2" etc. by default, which looks odd. I did not played with udev at all.
See https://askubuntu.com/questions/354783/ ... as-rename3
Use journalctl(1) to check if there are any problems in the logs.
deadbang
Re: Interface names
I used this
1) Edit your /etc/default/grub change GRUB_CMDLINE_LINUX="" to :
GRUB_CMDLINE_LINUX="net.ifnames=0"
from
https://unix.stackexchange.com/question ... ian-jessie
And it worked, now my interfaces are eth0 and so on. I think iam happy now. Thanks guys
1) Edit your /etc/default/grub change GRUB_CMDLINE_LINUX="" to :
GRUB_CMDLINE_LINUX="net.ifnames=0"
from
https://unix.stackexchange.com/question ... ian-jessie
And it worked, now my interfaces are eth0 and so on. I think iam happy now. Thanks guys
Re: Interface names
You did good!chargejan wrote:..., now my interfaces are eth0 and so on. I think iam happy now. Thanks guys
Just in the interest of completeness, that
freedesktop.org wiki link I posted also shows the other two methods of avoiding "predictable" interface names. In case others want to do it with a different method.
Re: Interface names
I have sad addon, the running interface is still rename4 but i think iam giving up, its just stubborn system, i respect it :/
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:25:90:f4:**:42 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:25:90:f4:**:43 brd ff:ff:ff:ff:ff:ff
4: rename4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:25:90:f4:**:44 brd ff:ff:ff:ff:ff:ff
inet 10.1*** brd 10.1.**5 scope global rename4
valid_lft forever preferred_lft forever
inet6 fe80::225:**4/64 scope link
valid_lft forever preferred_lft forever
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:25:90:f4:**:45 brd ff:ff:ff:ff:ff:ff
Or mabye i can try biosdevname=0 after installing it, not sure about that tho
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:25:90:f4:**:42 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:25:90:f4:**:43 brd ff:ff:ff:ff:ff:ff
4: rename4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:25:90:f4:**:44 brd ff:ff:ff:ff:ff:ff
inet 10.1*** brd 10.1.**5 scope global rename4
valid_lft forever preferred_lft forever
inet6 fe80::225:**4/64 scope link
valid_lft forever preferred_lft forever
5: eth3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 00:25:90:f4:**:45 brd ff:ff:ff:ff:ff:ff
Or mabye i can try biosdevname=0 after installing it, not sure about that tho
Re: Interface names
You are probably best off renaming them using
But you would need to create one file per device as /etc/systemd/network/$dev.link, so you could do
And I think it should work.
It's all rather complicated, but yeah.
You would end up with devices eth0, eth1, eth2 and eth3 according to their mac address.
Code: Select all
man systemd.link
Code: Select all
[Match]
MACAddress=.....
[Link]
NamePolicy=
Name=.....
Code: Select all
for d in 0 1 2 3; do
cat > /etc/systemd/network/eth$d.link <<- EOF
[Match]
MACAddress=.....:$(( 42 + d ))
[Link]
NamePolicy=
Name=eth$d
EOF
done
update-initramfs -u
It's all rather complicated, but yeah.
You would end up with devices eth0, eth1, eth2 and eth3 according to their mac address.
Re: Interface names
The new interface names are some silliness aren't they! Devuan has gotten rid of them, so no need to have to revert manually.chargejan wrote:I used this
1) Edit your /etc/default/grub change GRUB_CMDLINE_LINUX="" to :
GRUB_CMDLINE_LINUX="net.ifnames=0"
from
https://unix.stackexchange.com/question ... ian-jessie
And it worked, now my interfaces are eth0 and so on. I think iam happy now. Thanks guys
May the FORK be with you!
Re: Interface names
Well, personally I don't find them that "predictable" but don't you remember the days when sometime disks and interfaces didn't always get enumerated in the same order when there were multiples?golinux wrote: Devuan has gotten rid of them, so no need to have to revert manually.
But forgive me if all you want to do is make another plug for Devuan, I don't mind if you do that.
Re: Interface names
I never had a problem using uuid or labels.Thorny wrote:Well, personally I don't find them that "predictable" but don't you remember the days when sometime disks and interfaces didn't always get enumerated in the same order when there were multiples?golinux wrote: Devuan has gotten rid of them, so no need to have to revert manually.
That's a rather cynical and judgmental conclusion. You could happily substitute the name any distro that does the same thing. Users have a right to know that the madness is NOT a fait accompli in all Debian-based distros.Thorny wrote:But forgive me if all you want to do is make another plug for Devuan, I don't mind if you do that.
May the FORK be with you!
Re: [OT]Interface names
[OT]
However, I was writing about the days when we used hdx terminology for designating HDDs. You know, before UUIDs.
And, I don't have a problem with using LABELS either, I can never remember UUIDs.
I did write that I didn't mind if you want to plug Devuan.
No surprise there, I am both cynical and judgmental (sic), pedantic too.golinux wrote: That's a rather cynical and judgmental conclusion. You could happily substitute the name any distro that does the same thing. Users have a right to know that the madness is NOT a fait accompli in all Debian-based distros.
However, I was writing about the days when we used hdx terminology for designating HDDs. You know, before UUIDs.
And, I don't have a problem with using LABELS either, I can never remember UUIDs.
I did write that I didn't mind if you want to plug Devuan.
Re: Interface names
OpenSUSE also doesn't enable "Predictable" Interface Names by default.
These names are the worst invention in Linux thus far, after SystemD.
These names are the worst invention in Linux thus far, after SystemD.
Re: Interface names
Well, I kind of like the number two way of avoiding the "predictable interface naming" shown in the link I posted.
[edit] Yes, dryden, I am aware you mentioned that.
It is similar to the use of LABEL for drives. However it also does not happen automagically and of course wouldn't be useful for those who don't use systemd.2. You create your own manual naming scheme, for example by naming your interfaces "internet0", "dmz0" or "lan0". For that create your own .link files in /etc/systemd/network/, that choose an explicit name or a better naming scheme for one, some, or all of your interfaces. See systemd.link(5) for more information.
[edit] Yes, dryden, I am aware you mentioned that.
Re: Interface names
The idea of 'sorted' interface names itself is not bad, the implementation is just defunct.
There is no sensible reason why, in the booting of the system, they could not have implemented a choke point like network.target at which the 'biosdevnames' could not be enumerated into a logical list.
And if that's not possible for hot-pluggable devices like 3g modems, then use device ID strings or let the user assign a number to each device (as has of course been implemented).
It should be easy enough to have some software that lists the devices and where you can say "device "string" set number 2".
It only requires 2 commands but we don't have it.
Maybe OpenSUSE has it (with YaST) I don't know.
I mean it's so utterly simple to provide a user-friendly solution, but apparently that is not difficult enough and you can't call yourself a genius for solving such a problem; however if you make the solution utterly complex you can make a career out of solving the problems your own solutions produced.
(Lots of people in the world are employed in such systems).
There is no sensible reason why, in the booting of the system, they could not have implemented a choke point like network.target at which the 'biosdevnames' could not be enumerated into a logical list.
And if that's not possible for hot-pluggable devices like 3g modems, then use device ID strings or let the user assign a number to each device (as has of course been implemented).
It should be easy enough to have some software that lists the devices and where you can say "device "string" set number 2".
It only requires 2 commands but we don't have it.
Maybe OpenSUSE has it (with YaST) I don't know.
I mean it's so utterly simple to provide a user-friendly solution, but apparently that is not difficult enough and you can't call yourself a genius for solving such a problem; however if you make the solution utterly complex you can make a career out of solving the problems your own solutions produced.
(Lots of people in the world are employed in such systems).