Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tailscale Incompatibility #1658

Closed
alexk101 opened this issue Aug 18, 2024 · 5 comments
Closed

Tailscale Incompatibility #1658

alexk101 opened this issue Aug 18, 2024 · 5 comments
Labels
in/compatibility TYPE: a report about in/compatibility stale ATTRIBUTE: this issue has not had recent activity

Comments

@alexk101
Copy link

System Info
Distro: EndeavourOS
CPU: 8-core AMD Ryzen 7 6800H with Radeon Graphics (-MT MCP-)
speed/min/max: 503/400/4785 MHz
Kernel: 6.10.5-arch1-1 x86_64

What worked?
Still able to ping 1.1.1.1 and access the internet through IP's directly

What did not work?
When using Tailscale with portmaster, I am unable to resolve any DNS queries.

Debug Information:

NJ{"Created":1723998797,"Modified":1723998797,"Expires":1726590797,"Deleted":0}S
executing core/portmaster-core version 1.6.10 on linux amd64
240818 12:33:17.254 ▶ BOF
240818 12:33:17.386 entication:291 ▶ WARN 001 api: denying api access from 127.0.0.1:45742
240818 12:33:18.387 entication:291 ▶ WARN 003 api: denying api access from 127.0.0.1:58746
240818 12:33:19.388 entication:291 ▶ WARN 005 api: denying api access from 127.0.0.1:58762
240818 12:33:20.390 entication:291 ▶ WARN 007 api: denying api access from 127.0.0.1:58768
240818 12:33:21.391 entication:291 ▶ WARN 009 api: denying api access from 127.0.0.1:58776
240818 12:33:22.392 entication:291 ▶ WARN 011 api: denying api access from 127.0.0.1:58790
240818 12:33:23.146 les/worker:109 ▶ ERRO 013 resolver: service-worker ip info delayed cache writer failed (1): could not start database cache (type bbolt): timeout - restarting in 2s
240818 12:33:48.321 pat/module:112 ▶ ERRO 015 compat: self-check #3: dns integration check failed: failed to receive test response: lookup a81429592840200e3b8934c09b3931629b.self-check.portmaster.home.arpa. on 100.100.100.100:53: read udp 100.96.67.87:50287->100.100.100.100:53: i/o timeout
240818 12:33:57.736 e/core/api:118 ▶ WARN 017 core: user requested shutdown via action
240818 12:33:57.837 dules/stop:057 ▶ WARN 019 modules: starting shutdown...
240818 12:34:00.326 ◀ EOF

@alexk101 alexk101 added the in/compatibility TYPE: a report about in/compatibility label Aug 18, 2024
Copy link

Hey @alexk101, thank you for reporting on a compatibility.

We keep a list of compatible software and user provided guides for improving compatibility in the wiki - please have a look there.
If you can't find your software in the list, then a good starting point is our guide on How do I make software compatible with Portmaster.

If you have managed to establish compatibility with an application, please share your findings here. This will greatly help other users encountering the same issues.

Copy link

Greetings and welcome to our community! As this is the first issue you opened here, we wanted to share some useful infos with you:

  • 🗣️ Our community on Discord is super helpful and active. We also have an AI-enabled support bot that knows Portmaster well and can give you immediate help.
  • 📖 The Wiki answers all common questions and has many important details. If you can't find an answer there, let us know, so we can add anything that's missing.

@alexk101
Copy link
Author

I have discovered a work around. Tailscale manually overwrite /etc/resolv.conf to do dns resolution when it is unable to correctly interface with systemd-resolved. This is the default behavior on most distros bundled with NetworkManager & systemd-resolved. To allow Tailscale to properly communicate, follow the instructions here

Copy link

This issue has been automatically marked as inactive because it has not had activity in the past two months.

If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics.

@github-actions github-actions bot added the stale ATTRIBUTE: this issue has not had recent activity label Oct 21, 2024
Copy link

This issue has been automatically closed because it has not had recent activity. Thank you for your contributions.

If the issue has not been resolved, you can find more information in our Wiki or continue the conversation on our Discord.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in/compatibility TYPE: a report about in/compatibility stale ATTRIBUTE: this issue has not had recent activity
Projects
None yet
Development

No branches or pull requests

1 participant