Hi Thomas,
why not only build one tunnel. As SSL. Side 2 is client, side one is server.
So, if on side 2 provider 1 fails, the tunnel will be build over provider 2 and vice versa.
Load balancing over 2 tunnels to the same ip ranges isn't really possible. Two tunnels with the same destination range. How schould a firewall decide witch way it schould take? And takes the answer the same route?
Viele Grüße / Best Regards,
Manu
- CISO -
- Sophos SCA & Partner-
Manu, the stimulus for this approach was the desire to prioritize VoIP traffic. Although you can do much of that with a single tunnel, it's easier to avoid disruption by up/downloads if one set of connections is used for VoIP and the others for everything else. Adding the fail-over to the other connections was just an extra I did for the client. We've had no further complaints about VoIP call quality. In these cases, the VoIP subnets are separate from the data subnets.
Cheers - Bob
Manu, the stimulus for this approach was the desire to prioritize VoIP traffic. Although you can do much of that with a single tunnel, it's easier to avoid disruption by up/downloads if one set of connections is used for VoIP and the others for everything else. Adding the fail-over to the other connections was just an extra I did for the client. We've had no further complaints about VoIP call quality. In these cases, the VoIP subnets are separate from the data subnets.
Cheers - Bob