Wired networking down. Fedora 37. [SOLVED]

Atheist

Active Member
Joined
Dec 12, 2021
Messages
105
Reaction score
33
Credits
929
I could really use some help in figuring out what I did to kill my wired connection. With the ethernet cable connected to port enp11s0 I get:
1) nmcli d ==> "device enp11s0, state connected, connection: wired connection".
2) nmcli connection up uuid xxx ==> "connection successfully activated"

No matter what I try, I get no internet through.
I have no wifi in this desktop, and at the moment I am using a portable USB-Ethernet adapter that works.
I also have a working laptop with wifi that works if needed.
Thanks
A
 
Last edited:


What is output of..

ip add

and

netstat -nr
 
What is output of..

ip add

and

netstat -nr
Thanks for the reply! I am copying this and pasting from the "crippled" machine using the USB adapter to get internet. If you want me to disconnect that and connect the non-working ports, let me know.
_______________________________________
ip add
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether bc:5f:f4:08:d5:cc brd ff:ff:ff:ff:ff:ff
inet 192.168.0.34/24 brd 192.168.0.255 scope global noprefixroute enp11s0
valid_lft forever preferred_lft forever
inet6 fe80::abd7:e0ad:77c6:bb8e/64 scope link tentative noprefixroute
valid_lft forever preferred_lft forever
3: enp13s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether bc:5f:f4:08:d5:cb brd ff:ff:ff:ff:ff:ff
5: enp0s29u1u7u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:e0:4c:03:44:11 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.39/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s29u1u7u4
valid_lft 77711sec preferred_lft 77711sec
inet6 fe80::4655:292e:24d2:c496/64 scope link noprefixroute
valid_lft forever preferred_lft forever
6: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500
link/none
inet 10.4.86.243/24 scope global tun0
valid_lft forever preferred_lft forever
inet6 fde6:7a:7d20:56::10f1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::4d44:387d:9d97:72b7/64 scope link stable-privacy
valid_lft forever preferred_lft forever
~>
 
~> netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0 tun0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp11s0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp0s29u1u7u4
10.4.86.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
128.0.0.0 0.0.0.0 128.0.0.0 U 0 0 0 tun0
173.44.55.155 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
173.44.55.157 192.168.1.1 255.255.255.255 UGH 0 0 0 enp0s29u1u7u4
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp11s0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 enp0s29u1u7u4
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 enp11s0
~>
 
Code:
5: enp0s29u1u7u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 00:e0:4c:03:44:11 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.39/24 brd 192.168.1.255 scope global dynamic noprefixroute enp0s29u1u7u4
valid_lft 77711sec preferred_lft 77711sec

This adapter appears to be the only one that is up.

Code:
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp11s0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp0s29u1u7u4

It appears to have a default gateway. (There are two default gateways here, could be a conflict. )

What is the output of ...

ping google.com

and

traceroute google.com
 
The first, enp11s0 is the one on the mobo giving me a problem. The enp0s29xxx is the temporary usb adapter. I will disconnect that so that this test is meaningful....stand by. (I will log out and log back in from the laptop.)
 
ping google.com is hanging...probably will time out...ah there "Temporary failure in name resolution"

traceroute google.com: "Temporary failure in name resolution" "Cannot handle "host" cmdline arg 'google.com' on position 1 (argc 1)
 
Here is the correct output with the cable attached to the non-working port
~> netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 enp11s0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 enp11s0
192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 enp11s0
~> ip add
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp11s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether bc:5f:f4:08:d5:cc brd ff:ff:ff:ff:ff:ff
inet 192.168.0.34/24 brd 192.168.0.255 scope global noprefixroute enp11s0
valid_lft forever preferred_lft forever
inet6 fe80::abd7:e0ad:77c6:bb8e/64 scope link tentative noprefixroute
valid_lft forever preferred_lft forever
3: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether bc:5f:f4:08:d5:cb brd ff:ff:ff:ff:ff:ff
~>
 
FYI, when I run 'sudo rfkill' there is no output. Since there are no wifi nor bluetooth devices installed in this desktop, I don't expect to see them. But as KGIII mentions, rfkill should address wlan devices also....
 
Last edited:
sudo rfkill unblock wireless

is that what you ran?
 
So it appears you have no DNS. It could be that is isn't set automatically.
(Are you using DHCP or a static IP ?)
DHCP "usually" sets your DNS servers IP's for you (but not always).
With static IPs, you have to type it in yourself.

What is output of ...

nmcli con show enp11s0 | grep DNS

You can add DNS like this...

nmcli con mod enp11s0 ipv4.dns '8.8.8.8,9.9.9.9'

( 8.8.8.8 is googles public DNS server, 9.9.9.9 is another public DNS server )
NOTE: There is a comma between them.

Then repeat the command above to see if you have DNS.
If you already have a DNS server setup. Check your firewall for DNS service.

firewall-cmd --list-services
 
Last edited:
Thanks for the suggestions. I hope these command results below help. I have included some comments in parentheses.

~> nmcli c
NAME UUID TYPE DEVICE
Wired Connection c1d56241-49f0-f23c-c5f8-551e13b8aeeb ethernet enp11s0
mylan 33893334-49f2-4771-9b44-850571468a52 ethernet --
~>
(The "mylan" is something I created when I was futtering about with commands that I did not fully comprehend.)

> nmcli con show enp11s0 | grep DNS
Error: enp11s0 - no such connection profile.
~>

~> nmcli con show uuid c1d56241-49f0-f23c-c5f8-551e13b8aeeb | grep DNS
IP4.DNS[1]: 8.8.8.8
IP4.DNS[2]: 8.8.4.4

~> nmcli con mod enp11s0 ipv4.dns '8.8.8.8,9.9.9.9'
Error: unknown connection 'enp11s0'.

(Is it a problem that the device name enp11s0 is not recognized, but the uuid is?)

~> nmcli con mod uuid c1d56241-49f0-f23c-c5f8-551e13b8aeeb ipv4.dns '8.8.8.8,9.9.9.9'

~> nmcli con show uuid c1d56241-49f0-f23c-c5f8-551e13b8aeeb | grep DNS
IP4.DNS[1]: 8.8.8.8
IP4.DNS[2]: 8.8.4.4
~>

(Hmm, why didn't the 9.9.9.9 DNS get assigned?)

~> firewall-cmd --list-services
dhcpv6-client mdns samba-client ssh
~>
 
Can you give output of...

nmcli conn show

The connection name doesn't always match the device name.
For example, device enp11s0 could have a connection name of 'System enp11s0' or
'Wired Connection 3'. So when you modify the connection, the name has to match.
For example instead of ...

nmcli con mod enp11s0 ipv4.dns '8.8.8.8,9.9.9.9'

you might have to use

nmcli con mod 'System enp11s0' ipv4.dns '8.8.8.8,9.9.9.9'

Note that if there is a space in the connection name, you will have to put it in quotes or double quotes.
 
Last edited:
~> nmcli con show
NAME UUID TYPE DEVICE
Wired Connection c1d56241-49f0-f23c-c5f8-551e13b8aeeb ethernet enp11s0
mylan 33893334-49f2-4771-9b44-850571468a52 ethernet --
~>
 
So in your case you will have to use

nmcli con mod 'Wired Connection' ipv4.dns '8.8.8.8,9.9.9.9'
 
a) Is that any different than what I did by using the uuid to attempt to mod the dns?
b) I modded using the 'Wired Connection' as you said, but when I di "show" | grep DNS, the result is the same as above 8.8.8.8, 8.8.4.4. The 9.9.9.9 does not appear.
 
Here is what I wrote above:
_______________________
~> nmcli con show
NAME UUID TYPE DEVICE
Wired Connection c1d56241-49f0-f23c-c5f8-551e13b8aeeb ethernet enp11s0
mylan 33893334-49f2-4771-9b44-850571468a52 ethernet --
~> nmcli con mod 'Wired Connection' ipv4.dns '8.8.8.8,9.9.9.9'
~> nmcli con show 'Wired Connection' | grep DNS
IP4.DNS[1]: 8.8.8.8
IP4.DNS[2]: 8.8.4.4
~>
 
ANd again, thanks very very much for your patience and perseverence, Dos2Unix !
 
(The "mylan" is something I created when I was futtering about with commands that I did not fully comprehend.)

You can delete this if you want to,

nmcli con del mylan

Is that any different than what I did by using the uuid to attempt to mod the dns?

NetworkManager has been around since 2004. However a lot of distro's didn't start using it until
the last 7 or 8 years or so. When it first came out, there were some notes about not using the uuid.
It was buggy 13 or 14 years ago. I got into the habit of using the connection name instead of the uuid.
It is a lot more stable now, and I'm sure the uuid works fine now, but old habits die hard.
 

Members online


Latest posts

Top