Ubuntu Server network issues | Linux For All | Page 1

outer holly Jun 1, 2023, 7:42 PM

#

Routing issues

low sequoia Jun 1, 2023, 7:46 PM

#

How can I go about fixing that?

#

This is what iproute shows

10.66.66.0/24 dev wg0 proto kernel scope link src 10.66.66.1 
169.254.0.0/16 dev wg0 scope link metric 1000 
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 
172.18.0.0/16 dev br-43d764c9920a proto kernel scope link src 172.18.0.1 linkdown 
172.19.0.0/16 dev br-769bfa934de5 proto kernel scope link src 172.19.0.1 linkdown 
172.20.0.0/16 dev br-c1aca5126529 proto kernel scope link src 172.20.0.1 linkdown 
172.21.0.0/16 dev br-5db812533961 proto kernel scope link src 172.21.0.1 linkdown 
172.22.0.0/16 dev br-2ec9a9a72f10 proto kernel scope link src 172.22.0.1 linkdown 
172.23.0.0/16 dev br-93bedc057e79 proto kernel scope link src 172.23.0.1 linkdown 
172.24.0.0/16 dev br-5cb5c5026843 proto kernel scope link src 172.24.0.1 linkdown 
192.168.1.0/24 dev enp6s0f1 proto kernel scope link src 192.168.1.58 metric 100 
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ```

#

Would it be best to just flush my iptable

outer holly Jun 1, 2023, 8:14 PM

#

https://www.redhat.com/sysadmin/beginners-guide-network-troubleshooting-linux

Enable Sysadmin

A beginner's guide to network troubleshooting in Linux

Every system administrator needs to have at least a basic understanding of network troubleshooting. And the first rule of network troubleshooting to remember is, "Packets don't lie."

low sequoia Jun 1, 2023, 8:26 PM

#

Well I’m going to assume it is definitely a routing issue based off of nslookup google.com becuase it returns Server: 127.0.0.53 Address: 127.0.0.53#53

#

But I'm still not sure on how I can go about fixing it

outer holly Jun 1, 2023, 8:30 PM

#

Nothing wrong with that output, that's systemd-resolved. Search the IP address up from a machine with proper internet access, and see. The link I shared otherwise is a good starting resource, which should be read thoroughly, instead of pointing fingers at the wrong things.

low sequoia Jun 1, 2023, 8:34 PM

#

I didn't just gloss over the article linked

#

I'm not really understanding how I'm supposed to fix or identify my issue if everything is returning normal according to that article

outer holly Jun 1, 2023, 8:41 PM

#

Apply your targets to the ones that you're having issues with

low sequoia Jun 1, 2023, 8:42 PM

#

I have

#

Everything seems to be fine

#

I've also noticed when logging in via ssh I see this message Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings

#

Everything seems fine through the command line so it must some other underlying problem

stuck summit Jun 2, 2023, 2:41 PM

#

What's the resulting output from resolvectl?

low sequoia Jun 2, 2023, 6:58 PM

#

stuck summit What's the resulting output from `resolvectl`?

Do you want all 264 lines or just the ethernet stuff

#

This is the two physical ethernet parts

      Current Scopes: DNS                   
DefaultRoute setting: yes                   
       LLMNR setting: yes                   
MulticastDNS setting: no                    
  DNSOverTLS setting: no                    
      DNSSEC setting: no                    
    DNSSEC supported: no                    
  Current DNS Server: 192.168.1.1           
         DNS Servers: 192.168.1.1           
                      2603:6010:8e00:236a::1
          DNS Domain: ~.                    
                      lan                   

Link 2 (enp6s0f0)
      Current Scopes: none
DefaultRoute setting: no  
       LLMNR setting: yes 
MulticastDNS setting: no  
  DNSOverTLS setting: no  
      DNSSEC setting: no  
    DNSSEC supported: no  ```

stuck summit Jun 2, 2023, 7:05 PM

#

You missed the Global section too.

low sequoia Jun 2, 2023, 7:47 PM

#

The global section is huge

#

nvm i just misread it

#

       LLMNR setting: no                  
MulticastDNS setting: no                  
  DNSOverTLS setting: no                  
      DNSSEC setting: no                  
    DNSSEC supported: no                  
          DNS Domain: lan                 
          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 ```

stuck summit Jun 3, 2023, 1:51 AM

#

When you use getent hosts google.com or similar website fqdn, do you get no results? And what do you use that returns ERR_ADDRESS_UNREACHABLE?

low sequoia Jun 3, 2023, 1:41 PM

#

Sites like twitter and askubuntu return it

#

Not all sites return it which I find weird, but it's also affecting my Docker containers

#

I can't even access my webserver outside of my network

#

I have no idea how this came to be after I left the server off for a few months and the only thing stopping me from reinstalling is I don't really know how to reinstall the OS without losing all of my stuff on the drive. Like configurations and docker containers

#Ubuntu Server network issues