Felix,
Let me tighten the problem definition.
1) I am able to change the name of the interface
2) This interface does NOT come up at boot time.
3) Manually configuring the interface produces an interface that is up and sort of functional. The host command produces some DNS information but when I try to use the interface with wget, I get error messages.
fc34-bash 5.0 ~# ifconfig eth0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 54:04:a6:10:61:87 txqueuelen 1000 (Ethernet) RX packets 7590 bytes 455400 (444.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
fc34-bash 5.0 ~# export interface=eth0
fc34-bash 5.0 ~# ifconfig "$interface" 10.28.0.2 netmask 255.255.255.0 broadcast 255.255.255.255 up fc34-bash 5.0 ~# route add default gw 10.28.0.1 "$interface"
fc34-bash 5.0 ~# cp resolv.conf /etc 'resolv.conf' -> '/etc/resolv.conf'
fc34-bash 5.0 ~# host yahoo.com yahoo.com has address 98.137.11.164 yahoo.com has address 74.6.143.25 yahoo.com has address 74.6.143.26 yahoo.com has address 74.6.231.20 yahoo.com has address 74.6.231.21 yahoo.com has address 98.137.11.163 yahoo.com has IPv6 address 2001:4998:124:1507::f000 yahoo.com has IPv6 address 2001:4998:124:1507::f001 yahoo.com has IPv6 address 2001:4998:24:120d::1:0 yahoo.com has IPv6 address 2001:4998:24:120d::1:1 yahoo.com has IPv6 address 2001:4998:44:3507::8000 yahoo.com has IPv6 address 2001:4998:44:3507::8001 yahoo.com mail is handled by 1 mta5.am0.yahoodns.net. yahoo.com mail is handled by 1 mta6.am0.yahoodns.net. yahoo.com mail is handled by 1 mta7.am0.yahoodns.net.
fc34-bash 5.0 ~# ping yahoo.com ping: yahoo.com: Name or service not known <========= problem
fc34-bash 5.0 ~# getvb #!/bin/bash -xv
cd /isos + cd /isos
/usr/bin/wget https://www.virtualbox.org/wiki/Testbuilds -O www.virtualbox.org+wiki+Testbuilds-index.html + /usr/bin/wget https://www.virtualbox.org/wiki/Testbuilds -O www.virtualbox.org+wiki+Testbuilds-index.html --2020-12-24 21:02:56-- https://www.virtualbox.org/wiki/Testbuilds
# below is another or maybe the same problem:
Resolving www.virtualbox.org (www.virtualbox.org)... failed: Name or service not known. wget: unable to resolve host address ‘www.virtualbox.org’
----------------------------------------------------------------------
Date: Sat, 26 Dec 2020 14:39:22 -0500 From: Felix Miata mrmazda@earthlink.net Subject: Re: Trying to rename enp5s0 to eth0 fails To: test@lists.fedoraproject.org Message-ID: fe04e6d0-f802-e5c3-ec3f-288a003934ef@earthlink.net Content-Type: text/plain; charset=UTF-8
George R Goffe via test composed on 2020-12-26 17:39 (UTC):
I don't any instructions in your post.
Felix Miata composed on 2020-12-26 02:45 (UTC-0500):
No problem doing it my way:
# uname -r 5.10.0-0.rc6.20201204git34816d20f173.92.fc34.x86_64
# cat /proc/cmdline
... net.ifnames=0 ...
^^^^^^^^^^^^^
# ls -Gg /etc/udev/rules.d/ total 0 # ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 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 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff altname enp0s31f6 inet 192.168.xxx.xxx/24 brd 192.168.xxx.xxx scope global noprefixroute eth0 valid_lft forever preferred_lft forever
The above shows configuration and some consequences of using option #3 at the bottom of: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
That's all I do, though I do disable ipv6, but that has nothing to do with having eth0 assigned to the NIC. The kernel does all the work based upon that cmdline option.
George, I got your email from 2020-12-25 01:32 (UTC), and sent you a reply, but yahoo.com and earthlink.net do not play nice together. Email between the two very often disappears into the ether.