Tailscale with Cloudflare Warp
Conclusion!!!
Tldr
> Use WARP as proxy mode!!!!!
Use cf-warp
?
Use proxychains-ng
ssh で手元のコードをサーバ上で動かす(proxychains-ng) - 続 カッコの付け方
global nameserver に 1.1.1.1 はだめ???
-
dns: resolver: forward: no upstream resolvers set, returning SERVFAIL
- Override global namaservers
-
[RATELIMIT] format("netstack: could not bind local port %v: %v, trying again with random port")
- The
randomizeClientPort
field, if set totrue
, makes devices prefer a random port for WireGuard traffic over the default static port 41641. This option is intended as a workaround for some buggy firewall devices, and should only be enabled after consulting with Tailscale (contact support).
- The
Tailscale
- Make
Preferences -> Use Tailscale DNS Settings
disabled
Warning
It may kill Magic DNS of Tailscale.
If you can't access a device that connected to Tailscale with
Question
Maybe, Cannot it connect to DERP
?
Turn on
せずに tailscale 起動時
What firewall ports should I open to use Tailscale · Tailscale
Cloudflare Warp
Split Tunnels · Cloudflare Zero Trust docs
- Add some values (that shows below) into
Preferences -> Advanced -> Split Tunnel (Exclude IPs)
. Tailscale IP ranges -> Can I use Tailscale alongside other VPNs · Tailscaletailscale.io
*.tailscale.io
tailscale.com
(Possibly for the logging-in process)*.tailscale.com
(Possibly for the logging-in process)100.64.0.0/10
fd7a:115c:a1e0::/48