UTM2UTM RED redundancy

Implement the logic layout among the physical, i.e. if you have one client sonnection IP and two server connection IPs create two RED Tunnels. If you have two or more client connections there will be four RED Tunnels and Multipathing Rules, if you like to have every case implemented. The Multipathing rule is needed on the client side, since this one sends traffic to the server and has to decide over which connection the packets flow.

Since client connections starts, when you activate them (without having traffic on the Interface), there's no need to implement a RED Server in a client Site.

Hi Alex,

more updates. I enabled uplink balancing and two multi path rules, as you suggested. One RED client connection to the other side is configured. Both ISP links are up and I have configured both as active in the balancing configuration, making ISP 1 the first in the list and ISP 2 the second. Now when I create the RED, it uses ISP 2, as this has the better BGP routing info at the moment.

But I cannot get the RED tunnel to bind to a certain interface. So when I create a second tunnel, it will use the same source IP and therefore the same ISP uplink as the other one. If the ISP fails, it falls over both to the other ISP. Something is still missing there. I tried the idea of Bob to use a different target host definition for both tunnels, each bound to an interface, but that doesn't work.

What am I missing?

Connecting to two different IP addresses on the target firewall work fine, by using OSPF.

Hi Ronny,

to get it: You have two links at your client side and two links at your server side, which are all active? You are able to connect to all of your IPs? You mentioned BGB -> You get a subnet via BGP distributed over two different providers/lines? To which IPs do you connect?

How's your configuration of the multipath rules? In my screenshot were two black fields in every of the rules. The first field defines the target IP (External Interface IP) to which the RED Tunnel should connect. The second one is the Interface, to which the connection should be bound.

Hi Alex,

sorry for all the confusion. Current setup is as follows:

FW A: one ISP uplink, RED server (plan to upgrade to second ISP link later this month)

FW B: two ISP uplinks, BGP full table, RED client

internal routing is all done via OSPF, BGP is only used externally (we advertise our own PI networks behind the FWs)

RED client is connecting to the external IP of FW A (which is provided in a transfer network from the ISP)

FW B also has two transfer networks, one for each ISP

This is the FW B setup:

Ah, now i got it...

Do you have another external IP on your Server UTM, since you cannot diffentiate the RED Traffic? In my example i have two Server IPs via two lines.

which UTM, the client UTM or the server UTM?

Edit: ahh wait, you asked for server UTM. I could use one of the additional address from the transfer network, didn't think about that. Nice one :) Thanks, I will try it tomorrow and give an update.

You're welcome, looking forward to hear good news. ;)

Hi Alex

I would like to give them to you, but the stickiness to the interface cannot be established. I added a secondary external address to FW A and created a second RED tunnel to this new IP, also changed the first multi patch rule to have the destination pointing to that new IP. Still the connection comes into FW A from the IP of the other ISP, so both REDs are established from the same source IP and therefore going across the same interface.

Maybe the multi path rules are not honored or my RED group is wrong. I specified 3400/TCP, 3400/UDP, 3401/UDP and 3410/UDP in that group, according to the documentation of Sophos.

Hm...

Why have the Destinations in your Multipath Rules Question Marks?

Its a SUM host definition, maybe that's why it doesn't have an icon?