Tripton

Thanks for the info, that's actually what I'm doing to route the Cloudflare IP Range with Tailscale through a VPN Container because Deutsche Telekom AG peering Issues (#1 #2 #3) and the approach works really nicely!

Thank you so much

Hi there, I wanted to report a potential issue with the Tailscale plugin’s integration for Docker containers. Under Advanced Tailscale Show Advanced Settings -> Tailscale Advertise Routes, the input field for specifying subnet routes uses a regex pattern [0-9:., ]* in the HTML input tag. This pattern currently excludes the / character, which is required for CIDR notation (e.g., /24). As a result, users cannot input valid subnet routes like 8.8.8.0/24 directly into the field (which is cool for subnet routers). For a quick test, I manually edited the regex to also allow / which seems to work fine inside the container then. Could somebody verify that this is actually and issue and not just me being dumb? If it's actually an issue, maybe the validation pattern can be extended to allow slashes? This would ensure compatibility with Tailscale’s subnet router syntax. Thanks for your hard work!