What will occur if SecureConnect is used on Linux with a conflicting IPSec process?

When SecureConnect is utilized on Linux in an environment where there is a conflicting IPSec process, it disrupts the normal operation of SecureConnect. IPSec is a suite of protocols that secures Internet Protocol communications by authenticating and encrypting each IP packet in a communication session. If there is an existing IPSec process that conflicts with the operations required by SecureConnect, it can lead to failures in establishing the necessary secure tunnels that SecureConnect relies on.

The underlying reason for this is that both SecureConnect and the conflicting IPSec process might attempt to modify routing tables or manipulate network interfaces in ways that are incompatible with each other. As a result, SecureConnect won't be able to establish its connections or operate effectively, leading to a failure in its intended functionality. Therefore, when a conflicting IPSec process is present, SecureConnect cannot proceed as designed, which is why it will fail rather than operate in a limited capacity or require a restart.