Brainstorming for multi-site LAN (local), WAN (w/IPsec VPN), LAN (Metro Ethernet) setup

It will be much easier with EAP3 Refresh1, because the VTI (Route based VPN) is coming.

In this concept, you can actually build an IPsec with a Interface and route the traffic with SD-WAN / Static routing.

In that case, you do not have to figure out, which Precedence comes first. Instead both exists and uses the same "page". 

Another approach would be: Use RED Site to Site.

Same setup like VTI. You have an Interface for the VPN, so you can actually SD-WAN Route everything. 

It will be much easier with EAP3 Refresh1, because the VTI (Route based VPN) is coming.

In this concept, you can actually build an IPsec with a Interface and route the traffic with SD-WAN / Static routing.

In that case, you do not have to figure out, which Precedence comes first. Instead both exists and uses the same "page". 

Another approach would be: Use RED Site to Site.

Same setup like VTI. You have an Interface for the VPN, so you can actually SD-WAN Route everything. 

Thanks LuCar. The VTI sounds very interesting, while also circling back for a Red second look.

I actually had a XG Red connection setup between sites to start some testing, when someone suggested it may not be the best for optimization of resources, so I tore it down. Sorry, I should have paid more attention to their reasoning.

Well, I am back on this topic, if anyone is interested. I set up RED P2Ps, and I am trying to get  OSPF sorted out, if possible.

I brought a RED circuit up, and configured 2 LAN gateways:

1. Port 1 LAN - 192.168.10.1
2. Port 4 LAN - 172.30.255.10 (gateway 172.30.255.20)
3. red1 LAN - 172.40.255.10 (gateway 172.40.255.20)

OSPF Network

1. 172.30.255.0/24 - Area 0.0.0.0
2. 172.40.255.0/24 - Area 0.0.0.0 (showing off my naïveté)
3. 192.16.10.0/24 - Area 10.10.1.1

OSPF Area

1. 0.0.0.0
2. 10.10.1.1

Everything failed over to RED as needed when I added an 172.40.255.0/24 to area 0 to the below layout (don't know if that is even kosher), but SIP became unreachable a short while later.

Did you check the route precedence?

https://community.sophos.com/kb/en-us/123610

Apurv Patel / Rana Sharma Maybe somebody could take a look at this one?

Another approach: Does your Configuration work with static routes instead of OSPF?

There are two KBAs for this:

https://community.sophos.com/kb/en-us/132264

https://community.sophos.com/kb/en-us/125003

In the second one:

Note: 

The default OSPF route is shown in its routing table so it is restricted to be added to the kernel routing table. If admin wants to add the default OSPF route to the kernel, he has to manually enable it from the CLI using the following custom commands.

Thanks LuCar,

Didn't see this, until I tried something, that I would like to file under "Do not try this".

I hooked up another RED connection to a different remote site for testing, and found the second RED client was displaying the first RED client's external IP in the connection display. Yes, I had set up SD-WAN policy routing on the first site. The SD-WAN seems to be working even better than what I needed. I'm back to my topology drawing board. :)

Paul

Hi Paul Warriner 

Thanks for the feedback. Let us know in which scenario you are facing issue currently ?

Thanks,

Rana Sharma