I have no idea why this is happening on my arch linux machine. I was trying to set it up as a client device, and now i have no internet connection on my wired network. This is bare metal not docker. I just wanted to add the device to my tailnet.

Any help is appreciated

Thank you for your time.

EDIT: I have completely uninstalled tailscale yet I still do not have internet access. I am connected to the network fine. If i cinnect through wifi it is the same result.

EDIT 2: the error I am recieving is limited connectivity.

EDIT 3: It has been fixed! scrion@lemmy.world solution fixed it!

  • litchralee@sh.itjust.worksEnglish
    1·
    12 hours ago

    It would help if you could recall what steps you did, a link to the instructions you followed, and what you’re currently observing. Otherwise, we’re all just guessing at what might be amiss.

    • ludicolo@lemmy.mlOPEnglish
      1·
      12 hours ago

      This is the guide I followed:

      https://tailscale.com/kb/1036/install-arch

      I then restarted because I was getting several errors when trying to use the tailscale up command.

      After thay restart I was able to get tailscale up to work but that is when the issue with limited connectivity arose.

        • ludicolo@lemmy.mlOPEnglish
          1·
          9 hours ago

          I did and thay did not change anything.

          As of right now I have tailscale uninstalled so I will reinstall it and try the values again.

          EDIT: lol I forgot I do not have internet I cannot reinstall tailscale

          EDIT 2: Pinging 1.1.1.1 works

          • just_another_person@lemmy.worldEnglish
            1·
            9 hours ago

            Well only your DNS is broken, so that’s all that needs to get fixed. Are you POSITIVE you’re using systemd resolve and not networkmanager?

                • ludicolo@lemmy.mlOPEnglish
                  1·
                  8 hours ago

                  – Boot b3a9a949f8d1499fb0404672a02d2e34 – Mar 11 21:04:21 arch systemd[1]: Starting Network Name Resolution… Mar 11 21:04:21 arch systemd-resolved[1296]: Positive Trust Anchors: Mar 11 21:04:21 arch systemd-resolved[1296]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d Mar 11 21:04:21 arch systemd-resolved[1296]: . IN DS 38696 8 2 683d2d0acb8c9b712a1948b27f741219298d0a450d612c483af444a4c0fb2b16 Mar 11 21:04:21 arch systemd-resolved[1296]: Negative trust anchors: home.arpa 10.in-addr.arpa 16.172.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.a rpa 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 170.0.0.192.in-addr.arpa 171.0.0.192.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa ipv4only.arpa resolver.arpa corp home internal intranet lan local private test Mar 11 21:04:21 arch systemd-resolved[1296]: Using system hostname ‘arch’. Mar 11 21:04:21 arch systemd-resolved[1296]: mDNS-IPv4: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers. Mar 11 21:04:21 masonarch systemd-resolved[1296]: mDNS-IPv6: There appears to be another mDNS responder running, or previously systemd-resolved crashed with some outstanding transfers.

                  • just_another_person@lemmy.worldEnglish
                    1·
                    8 hours ago

                    See if this helps at all:

                    sudo systemctl revert systemd-resolved
sudo systemctl restart systemd-resolved

                    Also, what does ls -lh /etc/resolv* show?