Gemino

After disable the wgcf WireGuard tunnel. still can't have traffic in "Exit mode" it's weird ``` [INFO] Status check in progress... ---------------------------- WARP Client : Stopped SOCKS5 Port : Off...

Tailscale IPv6 traffic will enter the wgcf network interface because the default route for IPv6 traffic is via wgcf. This default route takes precedence over any more specific routes unless...

After trying follow Alex's tutorial Install tailsacle in Docker. It only could access using IPv4 but failed to establish Direct connection as It behind the docker0 TUN interface (172.17.0.1/16... into...

~~update with the fix methods:just stop the WireGuard tunnnel and modify "nano /etc/wireguard/wgcf.conf" set to only Allow IPv6 traffic~~ update 2.0: still not fixed. as the tailscale still traffic IPv6...

Update with the help of Gemini Experimental 1114 💯 the problem fixed: wgcf Interface: This is your wireguard interface, as indicated by the wg-quick logs. It has been assigned an...

and for @fernandoenzo 's TailGate: The tailgate-allow ens5.service unit configured within the tailscaled.service.d/override.conf is not directly related to how IPv6 routing is handled for tailscale0 traffic. This configuration affects Tailscale's...

One more thing. if wgcf restart. it will over writer the priority 100 rule table. so thanks to wireguard PostUp and PostDown ["commands are issued when the interface is setup...

And from Claude 3.5 Sonnet V2 explain: why still have IPv6 in tailscale Ping command. *Tailscale's ping command behaves differently from a regular ping because it actively tries all possible...

Facing the same issue here, Set Remote VPS/VDS as Exit Node. but the device using the exit node have no Internet. Waiting for this "specify custom DNS (or DoH!" especially...

in Tailscale v1.78. remote VPC in Debian 12; have tailscale set --accept-dns=false, and config the systemd-resolved via "/etc/systemd/resolved.conf". doubled checked there is no NetworkManager installed or running. Read carefully this...