Using SSLVPN and IpSec as a Single Connection with automatic fallback to simply enduser handling?

It will be nice to combine SSLVPN and IpSec to one visible connection. If you're in China and SSLVPN doesn't work stable fallback to IpSec should take place, if you're in an hotel and IpSec is not possible SSLVPN should be tried. There should be a possibility to define one as primary and another connection as secondary.

As already in another post is written down, a single provision file should be possible with the ability of an automated rollout.

Good Job, i like it!

Ralf

0 AlanT over 4 years ago

Thanks Ralf, that is the plan, though it's just not part of this release.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 NESCOM over 4 years ago in reply to AlanT

This could be struggling as SSLVPN is independent of the xg-wan interface, means xg is accepting on any WANport ssl-vpn connections.

IPsec is dedicate to one single interface without any option to add additional interfaces (just only one profile can be configured).
That makes WAN connection backup impossible for IPsec.

Without fundamental changes on xg there won't be no way to do this if you run multiple wan interfaces.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RaLu over 4 years ago in reply to NESCOM

The setup of both Connections is possible with the 2.0 Client using different architecture. You're right, there are differences. But having two working connections with SSLVPN and IpSec there should be no problem having an automated failover.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Fred12 over 4 years ago in reply to RaLu

...as long as you are using just a singe WAN interface you are right, but in real live you always will have at least 2 WAN interfaces for backup. If so, it won't work as explained.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel