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!

  • scrion@lemmy.worldEnglish
    4·
    9 days 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
    1·
    8 days 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·
      7 days 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 🙉

  • infinitejones@sh.itjust.worksEnglish
    1·
    9 days 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…?