OSPF loses connection if "redistribute route" is enabled

Okay it seems that the RED connection goes down - but not the OSPF routing?!

Strange..

Is the OSPF connected via a static route? So does XG1 know the neighbor via static route? Maybe the RED tunnel cannot keep up. 

PS: RED connects via 3400 and the data flows to XG2 via 3410. So if the initial packet (3400) is correct, because there is no OSPF, it can break, after the RED t unnel is established and the packets (3410) are routed differently? Check packet capture. 

OSPF is not connected via static "route" - I have a dedicated subnet for the RED tunnel with a /30 subnet mask.

I can also see that XG 1 & 2 are exchanging routing information.

The RED tunnel does not drop instantly as soon as there is an OSPF traffic over it - but after a couple of seconds.

And what is also weird:

If OSPF networks are being setup manually and not via the "Redistribute connected" it works without any problem.

Can you verify it via tcpdump/packet capture? I guess, the routes changing and therefore the tunnel will drop.

Hmm that might be true - theoretically:

If I redistribute my local connected interfaces I would also push my external WAN IP into OSPF and XG2 would than try to route the RED tunnel through itself rather than via WAN.

Might the be true?

The issue could be related to the fact, that RED is "always online" (the interface at least). So the OSPF cannot differance between a hardware interface and red interfaces. And the route will be pushed to the interfaces as well. 

So try to setup a route (static) to the other end of RED. It should overwrite and work. 

So static route

Target IP/netmask would be my external WAN IP on XG1

Gateway WAN

Interface RED

What that be right?

Do you use Default Originate flag in OSPF? 

No

Okay your solution with a static route solved my issue!

For anyone reading this having same issues:

If the external WAN IP of primary Sophos is being distriubted via OSPF the 2nd Sophos will use it and triest to connect a RED tunnel within itself which makes it fail.

The solution is to add a static routing for the initial outgoing route:

Targe/netmaks = external WAN IP of Sophos 1.

Gateway = the WAN gateway of Sophos 2

Interface = WAN interface of Sophos 2

Okay your solution with a static route solved my issue!

For anyone reading this having same issues:

If the external WAN IP of primary Sophos is being distriubted via OSPF the 2nd Sophos will use it and triest to connect a RED tunnel within itself which makes it fail.

The solution is to add a static routing for the initial outgoing route:

Targe/netmaks = external WAN IP of Sophos 1.

Gateway = the WAN gateway of Sophos 2

Interface = WAN interface of Sophos 2