Skip to content
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion src/content/docs/magic-wan/zero-trust/warp.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,13 @@ head:
- tag: title
content: Use WARP as an on-ramp
---
:::note
By default direct Warp to Warp connections are not supported for machines behind MWAN with Warp connected due to double encapsulation and asymmetric routing.

It's recommended to not connect Warp when a device is in a location behind MWAN, and instead connect to their LAN IP from remote devices instead of using Warp to Warp.

If you do wish to use Warp inside a MWAN connected location, and directly connect to the devices Warp IP (in the 100.96.0.0/12 range) by using Warp to Warp you will need to exclude the 100.96.0.0/12 subnet from you on premises Warp profile and include it in your off premises profile.
:::

import { GlossaryTooltip, Render } from "~/components";

Expand Down Expand Up @@ -83,4 +90,4 @@ nslookup <SERVER_BEHIND_MAGIC_WAN>

This DNS lookup should return a valid IP address associated with the server or service you are testing for.

Next, test with a browser that you can connect to a service on the WAN by opening a webpage that is only accessible on the WAN. The server can be the same server used in the DNS lookup or another server in the WAN. Connecting using an IP address instead of a domain name should work.
Next, test with a browser that you can connect to a service on the WAN by opening a webpage that is only accessible on the WAN. The server can be the same server used in the DNS lookup or another server in the WAN. Connecting using an IP address instead of a domain name should work.