Wired networking down. Fedora 37. [SOLVED]

[Atheist]

You can delete this if you want to,

nmcli con del mylan

It is a lot more stable now, and I'm sure the uuid works fine now, but old habits die hard.

Trying other things....
~> resolvectl status
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp11s0)
Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 8.8.8.8
DNS Servers: 8.8.8.8 9.9.9.9

Link 3 (enp13s0)
Current Scopes: none
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
~>

 

[dos2unix]

If they aren't already installed, you can try installing dig or nslookup.

dig linux.org

nslookup getfedora.org

The output of these, can help troubleshoot your DNS.
You can see what nameservers you are using, if they are actually resolving and if they
are forwarding the correct IPs.

 

[Atheist]

If they aren't already installed, you can try installing dig or nslookup.

dig linux.org

nslookup getfedora.org

The output of these, can help troubleshoot your DNS.
You can see what nameservers you are using, if they are actually resolving and if they
are forwarding the correct IPs.

I would if I had internet on that machine!
otoh, i could reattach the temp USB adapter....ok...

 

[Atheist]

If they aren't already installed, you can try installing dig or nslookup.

dig linux.org

nslookup getfedora.org

The output of these, can help troubleshoot your DNS.
You can see what nameservers you are using, if they are actually resolving and if they
are forwarding the correct IPs.

~> dig linux.org

; <<>> DiG 9.18.11 <<>> linux.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 40268
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;linux.org. IN A

;; ANSWER SECTION:
linux.org. 60 IN A 172.67.148.63
linux.org. 60 IN A 104.21.33.190

;; Query time: 1 msec
;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
;; WHEN: Thu Feb 02 13:05:22 CST 2023
;; MSG SIZE rcvd: 70

~> _____________________________________________

~>
~> nslookup getfedora.org
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: getfedora.org
Address: 38.145.60.21
Name: getfedora.org
Address: 8.43.85.67
Name: getfedora.org
Address: 152.19.134.142
Name: getfedora.org
Address: 209.132.190.2
Name: getfedora.org
Address: 34.221.3.152
Name: getfedora.org
Address: 38.145.60.20
Name: getfedora.org
Address: 8.43.85.73
Name: getfedora.org
Address: 152.19.134.198
Name: getfedora.org
Address: 140.211.169.196
Name: getfedora.org
Address: 67.219.144.68
Name: getfedora.org
Address: 2620:52:3:1:dead:beef:cafe:fed7
Name: getfedora.org
Address: 2600:2701:4000:5211:dead:beef:fe:fed3
Name: getfedora.org
Address: 2600:1f14:fad:5c02:7c8a:72d0:1c58:c189
Name: getfedora.org
Address: 2605:bc80:3010:600:dead:beef:cafe:fed9
Name: getfedora.org
Address: 2604:1580:fe00:0:dead:beef:cafe:fed1
Name: getfedora.org
Address: 2620:52:3:1:dead:beef:cafe:fed6

~>

 

[Atheist]

Looking at "ip addr" I see that the ip for enp11s0 is 192.168.0.34. When I first started trying to figure out what was wrong, I assigned that along with a gateway of 192.168.1.1 for the Asus router. The ...0.34 was a wild guess. Maybe that is causing problems? Just my 2 cents worth.

 

[Atheist]

(Please excuse my rambling on if it is a distraction)
I note that I do not have any configuration files in /etc/NetworkManager/conf.d. I do have a file that I am told not to edit that is
/etc/NetworkManager/NetworkManager.conf
Could there be a missing file in the conf.d subdir? thanks

 

[Atheist]

Here is a question: Why does this show a transmit and receive of 332k and 222k bytes, respectively?
~> ip -s -h l show dev enp11s0
2: enp11s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether bc:5f:f4:08:d5:cc brd ff:ff:ff:ff:ff:ff
RX: bytes packets errors dropped missed mcast
222k 932 0 3 0 508
TX: bytes packets errors dropped carrier collsns
332k 5.47k 0 0 0 0

 

[Atheist]

sudo rfkill unblock wireless

is that what you ran?

sorry if I did not answer this....no, since there is only a wired ethernet ports. Thanks.

 

[dos2unix]

Sorry, I'm at my real job today, so I've been back and forth a lot today.

Lets back up a little.

I see that the ip for enp11s0 is 192.168.0.34. When I first started trying to figure out what was wrong, I assigned that along with a gateway of 192.168.1.1 for the Asus router. The ...0.34 was a wild guess. Maybe that is causing problems? Just my 2 cents worth.

The computer and the gateway have to be on the same subnet. The IP addresses don't matter as much as the
subnet mask does.

The 192. and the 168. are the same on both subnets, so we can ignore them for now.
Your NIC has a 0 in the 3rd octet, your router has 1 in the 3rd octet. So that's a difference.

Do you really want these to be different? It's OK if for some reason you need them to be.
"Usually" (but not always) "most" (but not all) home networks are on a single 24 bit subnet.
You can check this by looking at your subnet mask. It'll "usually" be 255.255.255.0
In this case, that won't work for your network because of the 3rd octet.

 

[Atheist]

The 192. and the 168. are the same on both subnets, so we can ignore them for now.
Your NIC has a 0 in the 3rd octet, your router has 1 in the 3rd octet. So that's a difference.

Thanks. No that was a screwup on my part. How do I change it to 192.168.1.x?

 

[dos2unix]

Having a full blown network class here might not work
For now it would be easier if your NIC and your router were both in the same subnet.
For example. Your router could be 192.168.1.1
Your NIC could be 192.168.1.34. The first 3 numbers are the same.
Normally routers are set to .1 but they don't have to be. It's just a convention more than anything.
The other IPs on that subnet can be anything except 0 or 255. It can't be 1 because your router is
already using it. But it could be any other number between 2 and 254. At least as long as nothing else
is using that address. Your cell phone and any printers could have an IP on that subnet as well.

 

[dos2unix]

Thanks. No that was a screwup on my part. How do I change it to 192.168.1.x?

nmcli con mod 'Wired Connection' ip4 192.168.1.34/24 gw4 192.168.1.1 autoconnect yes ipv4.method manual

 

[Atheist]

That was it!! I was just about to give up and erase the disk and start over. You saved me, Dos2Unix.
It looks like it is workign now (after a reboot)
I hope I can repay the favor one day.
And once again, thanks for your patience.
A

 

[wizardfromoz]

Nice work, the pair of you

@Atheist if that fix persists, you could go to your first Post #1 and edit the title to include

[SOLVED] at the beginning or end.

Cheers

Wizard

BTW good time for a Timeshift snapshot if EXT4 or Snapper if BTRFS?

 

[Atheist]

BTW good time for a Timeshift snapshot if EXT4 or Snapper if BTRFS?

Thanks for the suggestion. I will do it.
A