You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
192.168.0.0/24 (sun) === 0.0.0.0/0 (moon) tunnel works no matter cloudflare warp (via wireguard) is up or down.
192.168.1.0/24 (sun) > udp2raw (client) === fake tcp === udp2raw (server) < 0.0.0.0/0 (moon) only works if cloudflare warp (vai wireguard) is up.
ip route get 192.168.1.35when warp is downand
ip route get 192.168.1.35when warp is upand
Finally, the tricky is this, which solved the problem.
ip rule add pref 100 lookup main suppress_prefixlength 0Actually, the
wg-quick upsyntax has a line:I think this case is interesting and I want to understand the logic behind. However, it's a little complex for me. Thanks.
Beta Was this translation helpful? Give feedback.
All reactions