Selfhosted

44024 readers

554 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Tailscale has messed up my internet connection (lemmy.ml)

submitted 19 hours ago* (last edited 14 hours ago) by ludicolo@lemmy.ml to c/selfhosted@lemmy.world

37 comments fedilink hide all child comments

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!

you are viewing a single comment's thread
view the rest of the comments

[–] ludicolo@lemmy.ml 1 points 15 hours ago* (last edited 15 hours ago) (1 children)

-- 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.world 1 points 15 hours ago* (last edited 15 hours ago) (1 children)

See if this helps at all:

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

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

[–] ludicolo@lemmy.ml 1 points 15 hours ago (1 children)

The issue fixes after the restart command but when I reboot it cimes back.

'ls -lh /etc/resolv*' spits out:

lrwxrwxrwx 1 root root 37 Mar 11 16:48 /etc/resolv.conf -> /run/systemd/resolve/stub-resolv.conf

[–] just_another_person@lemmy.world 1 points 15 hours ago

I really think you have conflicting resolvers running on startup, which would explain this. Double check your systemd units that are enabled on boot. If you don't see anything like networkmanager, reboot the machine, get the status of systemd-resolv to make sure it's actually running after a fresh boot, check the logs and see if you see anything interesting there, then restart it and check the logs again once DNS works. Something is different between those two actions.