Stumbled upon this post from @Simone_Filippini that describes the issue I ran into and an open source project to address it. Sharing here in case the Tailscale curious want to experiment further.
I have multiple reports from people that are using it successfully with Wireguard⌠but I have my doubts thatâs going to work with tailscale since you cannot define manually the AllowedIPs list (afaik)
@Simone_Filippini does this get at what you describe?
{
"action": "accept",
"src": [<list-of-sources>],
"proto": "tcp", // optional
"dst": [<list-of-destinations>],
}
Copy/pasted from Syntax reference for the tailnet policy file ¡ Tailscale Docs for those who want to dig into this topic.
It still wonât allow multicast packet through the tunnel. And even it tailscale client would allow multicast traffic routing through the tunnel it wonât still work because with wireguard the traffic goes to the endpoint defined in the config, with tailscale the endpoints are dynamically and automatically managed. I suggest to use wireguard for such a setup
Appreciate the feedback Simone. Thanks for chiming in!
This has worked well for me for some years. ARC is way better in terms of data usage though