Very strange problem with networking not working when I tried Bodhi 6.0.0. in the live mode or after installing it to my hard drive. I tried both AppPack Release and the Standard Release. I am using a wireless dongle that worked with the previous version of Bodhi and with my dual boot mint OS. The WIFI shows connected and lists a proper IP from my fiber router but I cannot browse anywhere, chromium shows a DNS error. if I try a nslookup www.google.com it says cannot resolve. I can ping the IP of google. com etc. If I check the DNS cache it shows nothing in it. I checked the internet for DNS problems but I could not find a fix for it. I can boot into my Linux mint partition and the same WIFI dongle works fine. I was really looking forward to checking out 6.0.0. Stumped for now.
My linux installs have a separate partition for root and home, and I had installed with out formatting the home partition. As I had missing icons in the bodhi launcher, I installed again, and used a wired LAN connection and set to install updates and 3rd party drivers etc. Still same problem. Most likely a DNS issue as I can browse the settings webpage on my internet router as it uses a IP and I can ping internet IP addresses but not urls. As stated before everything looks good in the WIFI settings and it connects fine, just cannot go anywhere due to DNS not working. Works fine on wired LAN just not wireless.
lsusb | grep -i network. returned nothing
lsusb. returned: Bus 002 Device 005: ID 050d:845a Belkin Components F7D2101 802.11n Surf & Share Wireless Adapter v1000 [Realtek RTL8192SU]
sudo cat /var/run/dnsmasq/resolv.conf returned the following on wifi or wired LAN.
cat: /var/run/dnsmasq/resolv.conf: No such file or directory
sudo cat /var/run/systemd/resolve/stub-resolv.conf. Returned following on wireless or wired LAN:
# This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs must not access this file directly, but only through the # symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way, # replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf.
Thanks for all the help so far. After more digging it could be a driver issue. I had another USB dongle that does not work unless I run an install script provided by Bosstrends, which I ran and that WIFI dongle would work. Switching back to the Belkin N300 Wireless USB Adapter, Model: F9L1002v1, does not work.
I then did: inxi -Fxz | grep -iE "card|driver|if"
which returns: Device-2: Belkin F7D2101 802.11n Surf & Share Wireless Adapter v1000 [Realtek RTL8192SU] type: USB driver: r8712u
Which seems to show the wrong driver for this. This Belkin adapter usually would work with most Linix OS I have tried, and did work with the previous version of Bodhi linux. I am currently looking on how to update the driver for the Belkin N300 Wifi dongle.
As to the previous suggestion resolvectl status 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 5 (wlxc05627e8d51f) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no
Link 2 (enp3s0) Current Scopes: none DefaultRoute setting: no LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: 2001:568:ff09:10a::53 DNS Servers: 2001:568:ff09:10a::53 2001:568:ff09:10b::53 DNS Domain: ~.