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!
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 :/
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.
This seems to have fixed it!! Thank you so much!
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