-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Hello,
Thought I should follow this:
Unless you are opening a pull request which will only make small corrections, for instance, to correct a typo, you are more likely to get traction for your changes if you open an issue first to discuss the proposed changes. Issues and Pull Requests older than 60 days will automatically be marked as stale and then closed 7 days later if there still hasn't been any further activity.
Anyway, I have a Pull Request open, here #3883 which basically just guides you on what to include in the Raspberry Pi Connect daemon system service so it works with Tailscale. You can check my forum post here, the TLDR is that Raspberry Pi Connect uses IP addresses by default, which is fine, but when somebody uses Tailscale, mDNS gets in the way and suddenly connect doesn't stream the desktop due to Web RTC not working. The solution from the paulmu engineer was to set the Raspberry Pi Connect daemon to mDNS mode, meaning that it will use blah-blah-blah.local in web RTC instead of good old IP addresses. This mode can be simply enabled by passing the -mdns flag to the connect daemon and then both Raspberry Pi Connect and Tailscale are happy and work perfectly without limiting any functionality, This is most likely going to be used by advanced users but I believe it should be in the documentation so people having the same issue don't have to do the same research as I did. Hope that covers you!