Can I use Tailscale and WireGuard client together?
Yes, but not recommended to turn on “Custom Exit Nodes”, I don’t know what’s gonna happen.
That said, enabling both Tailscale and wireguard client make traffic complicated.
Before firmware 4.5, the underlying traffic of Tailscale(port 41641) goes via Non-VPN interface.
From 4.5, it will go via wireguard VPN interface, so you will find a public VPN IP at tailscale console - Machine Details page.
2 Likes
Basically this sounds like my problem right now. Tailscale on 4.5 is broken? GL.iNet GL-MT3000 (Beryl AX)
Can i change the behavior of Tailscale so that it acts like the previous version before 4.5?
Yep, see this one:
1 Like
It’s maybe only relevant if you have access to a VPS or other machine that is able to run docker containers, but there is the alternative option of spinning up a bridge that connects the WireGuard tunnel to the Tailscale tailnet by using GitHub - juhovh/tailguard: Easy Tailscale to WireGuard bridge using Docker .
This way you can just use Tailscale on your GL.iNet router, and connect to the WireGuard node / subnets through that. It may not be as efficient as using a direct WireGuard tunnel, but makes configuration much easier, and allows accessing the same tunnel from other computers as well.
1 Like