Me and a friend each have a an account
I can use my exit node when i’m connected to 4G on my phone to browse both local internet
My friend which is on hols in greece cant use his exit node. He can ping it. But all internet traffic is killed. As soon he de-select exit node browsing works
What can he/we check? Everything is updated
dns server on the exit node was set to the router/modem
on my exit node it was not so guessing this is the issue here,
That was not the case… ie it was not the cause for the breaking
ping 100.126.215.89 (OMVNAP by Tailscale address)
ping OMVNAP (OMVNAP by hostname)
But cannot ping 4.2.2.1
It returns “Request timed out.” x 4
Exit Node = None:
PS C:\WINDOWS\system32> tracert 4.2.2.1
Tracing route to a dot resolvers dot level3 dot net [4.2.2.1]
over a maximum of 30 hops:
1 3 ms 3 ms 6 ms H1600V7.home [192.168.1.1]
2 24 ms 33 ms 21 ms 10.106.108.100 [10.106.108.100]
3 36 ms 25 ms 24 ms 79.128.250.10
4 25 ms 22 ms 22 ms 79.128.234.90
5 30 ms * 25 ms 79.128.35.181
6 32 ms 23 ms 25 ms 79.128.250.74
7 28 ms 23 ms 36 ms kolasr01-hu-0-0-0-0.ath.OTEGlobe.gr [62.75.3.9]
8 66 ms 60 ms 64 ms 62.75.4.154
9 69 ms 62 ms 61 ms 213.19.198.253
10 72 ms 62 ms 324 ms ae2.3204.edge7.Frankfurt1.level3.net [4.69.159.38]
11 123 ms 189 ms 65 ms a.resolvers.level3.net [4.2.2.1]
Trace complete.
Exit Node = OMVNAP:
PS C:\WINDOWS\system32> tracert 4.2.2.1
Tracing route to a.resolvers.level3.net [4.2.2.1]
over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Also check his DNS settings in the tailscale admin console.
Does he have “Override local DNS” setting active? (on top of the “Global nameservers” entries).
no changes done in the console, not him or me
but he got a second machine that we made an exit node and the subnet route was set wrong on the first machine 192.168.0.0/24 and not 192.168.0.1/24 so it matches his local network, prob we forgot to turn ip forwarding on
it works now but very slowly, prob his upload is shitty low
192.168.0.0/24 is correct if the IP range of his network is from 192.168.0.1 to 192.168.0.255, so it maybe was the IP forwarding as you said.
There are some instructions here regarding IP forwarding with subnets: Subnet routers and traffic relay nodes · Tailscale
that was the page i came up with when we setup his secon machine… and also what i used to compare with was in his admin console, and yes we had a big DOOOH moment when we saw the wrong ip range
and yes his upload in the uk is only 5.48 mbit/s
and the wifi at his hotel is 3.4 mbit/s
just curious, how much is lost running things through tailscale?
As long as you’re not going via a DERP relay it shouldn’t be too much overhead.
See this post that goes into some of the latest speed achievements: Surpassing 10Gb/s over Tailscale · Tailscale