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!

  • infinitejones@sh.itjust.worksEnglish
    11·
    9 months ago

    I’ve had similar problems in the past - apparently no internet connection, and both times I narrowed it down to the machine being unable to resolve domain names.

    Turns out Tailscale had changed the IP address for the machines’ DNS resolution in resolv.conf to 100.100.100.100

    That’s fine when the machine is connected to Tailscale but not when it isn’t!

    Reverting the DNS IP back to whatever it was previously, or to something like 1.1.1.1 solved the problem for me, at least to the extent that it could resolve URLs again.

    Worth a look, if only to rule it out…?

    • ludicolo@lemmy.mlOPEnglish
      1·
      9 months ago

      I try to nano into my resolv.conf but it appears to only be a symbolic link file. I apologize for my ignorance but is there any other way to revert my dns back?

      EDIT: the symbolic link leads to a directory that does not exist:

      /run/systemd/resolve/stub-resolv.conf

  • scrion@lemmy.worldEnglish
    10·
    9 months ago

    I don’t know what your previous setup was, but given that running resolved fixes your DNS issues, run:

    ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf

    This will point programs that use /etc/resolved.conf during DNS resolution to the local DNS server provided by systemd-resolved.

    Then, enable resolved so that it is started when you reboot:

    systemctl enable systemd-resolved.service

    Finally, start the service so that it is available immediately:

    systemctl start systemd-resolved.service

    You will want it run those with the required permissions, e. g. via sudo.

  • robador51@lemmy.mlEnglish
    2·
    9 months ago

    I had a similar issue with using tail scale, but here the issue was definitely not on the client. My actual DSL connection would reset, multiple times per day. Had the provider come 4 times to investigate the issue, got 3 new routers, they reinstalled the entry point to the house, and fixed an issue in the neighbourhood central point. All to no avail. I ended up purging everything tail scale and hand rolled wireguard. No more issues :/

    • FunkFactory@lemmy.worldEnglish
      1·
      9 months ago

      I love hearing about all of these stories the day after I decided to set up a tailnet. No issues so far but who knows. At least now I know to check my DNS config 🙉

  • TORFdot0@lemmy.worldEnglish
    1·
    9 months ago

    It looks like you fixed your issue but I had the same thing happen on windows 10 so I am gonna post how I fixed it in case someone runs across this thread later.

    In my case everything had been working previously but after an arbitrary reboot, my windows 10 PC could ping the local network and nothing else suddenly. No access to the tailnet, Internet; DNS or otherwise. On the wired interface that is. I could connect to WiFi and it would work just fine. I had a DHCP reservation set, deleted the reservation, let it get a new IP and then it worked. No idea why? Recreated the reservation and it still worked back on the old IP again

  • SuperUserDO@sh.itjust.worksEnglish
    1·
    9 months ago

    Let us know the following

    If ping works for: localhost, your gateway, 1.1.1.1, google.com.

    The contents of your /etc/resolve.conf

    If you have a tun0 interface (ifconfig or ip a)

    You said you uninstalled tailscale. Are there any running process or active systemd units laying around?

    • ludicolo@lemmy.mlOPEnglish
      1·
      9 months ago

      So I was able to get it working again by doing this solution that badlotus suggested. I did not delete the file because it was already gone after the first timw I attempted this. If I reboot my device however the issue comes back. If I run the command again my internet is back.

      Badlotus’ solution:

      “Have you tried deleting /etc/systemd/resolved.conf and restarting the service with systemctl restart systemd-resolved?”

      • SuperUserDO@sh.itjust.worksEnglish
        1·
        9 months ago

        Good that it’s working (kinda).

        So it sounds like your DNS resolver is botched. Id dig into the doc on how systemd-resolverd should look and see if you can’t rectify what went wrong (the arch wiki should have examples of what a default config looks like).

        I don’t remember if arch uses cloud init configs but it being reset at boot feels like a cloud init config problem.

  • litchralee@sh.itjust.worksEnglish
    0·
    9 months 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·
      9 months 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 months 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 months 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·
                  9 months 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.