I have recently bought a Slate Plus, my goal is to have all the wireless traffic to go through a Tailscale exit node.
I went into the Tailscale section in the WebUI and configured Tailscale. After that I am able to access the Admin Panel on its Tailscale IP address. So the connection seems to work. However, as soon as I enable the “Custom exit nodes” switch, all the clients connected to the GL-A1300 Wi-Fi network lose Internet access. I know that this exit node works, as I can use it from other Tailscale-connected devices.
If I SSH into the router, I can ping external websites and my public IP is the exit node IP. So the router has Internet connection, but not the clients connected to it. How can I fix this?
It looks like the exit node problem that fails to send back traffic via tailscale tunnel. Please try to restart tailscale of the server and check its route rules.
Thank you for your reply. The thing is, that this exit node works just fine if I use it from my laptop or from my phone. In also works well from the Slate Plus SSH console. It’s just the clients, that connect to Slate Plus that don’t get connected to the Internet. Which seems to point at some configuration issue on Slate Plus.
This exit node works as expected when communicating with other nodes themself, but fails to let node’s subnet through. Please check the exit node’s route table to verify if there’s any route conflict.
For windows:
I ran into this issue as well and got it working. My problem was that the exit node is a Linux device, so you have to add the --accept-routes flag when running tailscale. See Subnet routers and traffic relay nodes · Tailscale
I am also running into a similar problem, except I have a Beryl. Using tailscale to connect to exit nodes using my laptop works fine. However, as soon as I turn on custom exit node on the Beryl, internet immediately stops working. The devices I am using for exit nodes are Windows and Mac machines.
I am not sure what to do. I looked around the forum, and it seems a lot of people are encountering this issue. I am not a networking expert, so i dont know how to command line or use luci without some instruction.
I’ve been in touch with Gl.Inet support and they tried different options as well, but not this particular setup. I have experimented with multiple different exit nodes and to me it’s clear that this feature is just broken. It seems that Gl.iNet is only testing it with a configuration where the exit node is on the same local network as other devices.
I even see that my Slate can ping external resources and has external IP of the exit node, it is just that it won’t share the connection to the clients.
aligatorzebra thank you for the suggestion, did you add the option when running tailscale on the router or on the exit node? I am wondering because my exit node is also Linux, but it works with other devices, just when the Slate router connects to it, it fails to share the Internet connection to the clients.
@rickyrick do you think you can ssh into your Beryl, when it’s configured with a custom exit node and check that you can ping external websites like google? This way we can verify that your case is exactly like mine and try to convince @hansome that there is actually an issue.
@hansome I am not sure if that helps, but here is the result of running of running ip route on the exit node. How can the exit node configuration be the issue, when it works just fine with my other devices?:
I found the subnet allowed on gl-a1300 has 192.168.1.0/24, while you exit node device has also the network of 192.168.1.0/24. This will cause conflict.
Please change one of the network to a different subnet to locate the issue.
Done! But unfortunately the issue still remains. As soon as I toggle the “custom exit node” switch, all clients connected to Slate lose internet access.
