sneakers as in (casual) shoes...

With the resetting of the network configuration and the command "ip r" I have the following

default via 192.168.1.1 dev wx001f1fcd87e3 proto dhcp metric 600
169.254.0.0/16 dev wlx001f1fcd87e3 scope link metric 1000
192.168.1.0/24 dev wlx001f1fcd87e3 proto kernel scope link src 192.168.1.8 metric 600

Your thoughts?

Looks ok. Need the DNS info.

Can you ping an IP address.

ping 8.8.8.8

Which is one of Googles dns server.

Yes I can.

Paste of the desktop command "resolvectl"

ohn@john-Desktop-Linux:~$ resolvectl
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
lines 1-23...skipping...
Global
LLMNR setting: no
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

Link 4 (ipv6leakintrf0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: ::1
DNS Servers: ::1
DNS Domain: ~.

Link 3 (wlx001f1fcd87e3)
Current Scopes: none
DefaultRoute setting: no
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no

lines 1-55

Check status of systemd-resolved

systemctl status systemd-resolved

I have tried multiple times to put the output here from the "systemctl" command and it's too long and having a very difficult time cutting the script and pasting it. With that in mind since I have little data on this desktop perhaps I can upgrade to a later version Linux Mint. What is your opinion of that and the easiest way to go about it if you agree to my proposal,

Something isn't "working" with systemd-resolved because the DNS server is your computer and not the router. I'm not sure what is broken.

https://wiki.archlinux.org/title/Systemd-resolved

Installing a newer version will obviously fix the problem.

1 members found this post helpful.

michaelk
you have been so kind helping me to locate the issue and I am very grateful to you. Thank You!
I have learned some things here due to you. I have decided to upgrade to the latest version which presently running Linux Mint Ulyssa 20.1 so can you point me to where a simple installation can be upgraded?

An inplace upgrade would be from 18-19 then 19-20. You can find upgrade guides but I probably would backup files and install 20 from scratch.

1 members found this post helpful.

I second that advice. Doing an in-place upgrade just MIGHT preserve the cause of the problem.

1 members found this post helpful.

Sorry but I have been away for sometime. Lately life has been interrupting my activities. This morning I checked my documents and had nothing of importance, no photos, etc so I reformated the drive and reinstalled the OS iso. All is working well again.

Thank you to all who spent much time helping me diagnose and solve the issue. Much obliged.
Do take care.