Persistent Tunnel IP Resumption Across VPN Tunnel Switching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing VPN technologies disrupt remote server connections when clients switch between different VPN tunnels due to changes in tunnel IP addresses, causing inconvenience and requiring re-establishment of sessions.
Innovation Solution
Maintaining a consistent tunnel IP address across different secure tunnels by assigning a persistent tunnel IP address and using signaling and tables to resume remote connections, allowing seamless transitions between VPN protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a new tunnel IP address is assigned when switching VPN tunnels, then the secure tunnel can be established with different VPN protocols, but the remote server connection is disrupted and requires re-establishment
Solution Approach 1:
The system performs preliminary actions by assigning and maintaining a persistent tunnel IP address before the VPN tunnel switch occurs. The gateway server stores the mapping between the client identifier and the persistent tunnel IP address in advance, so when the client reconnects through a different VPN tunnel, the same tunnel IP address can be immediately assigned without disrupting the remote server connection.
Solution Approach 2:
The gateway server acts as an intermediary between the client and the remote server. It decouples the client's actual IP address changes from the remote server's perspective by always presenting the same persistent tunnel IP address to the remote server, regardless of which VPN tunnel is currently active. This intermediary function allows protocol flexibility while maintaining connection stability.
2Adaptability or versatility
If the tunnel IP address changes when switching VPN tunnels, then different VPN protocols can be used, but the remote server sees different source IP addresses causing connection interruption
Solution Approach 1:
The persistent tunnel IP address serves multiple functions simultaneously: it acts as the client's identifier in the first VPN tunnel, remains valid during tunnel switching to a second VPN tunnel, and continues to function as the source IP address for remote server communications. This universal address enables seamless operation across different VPN protocols without requiring session re-establishment.
3Reliability
If a persistent tunnel IP address is maintained across VPN tunnels, then remote connections can be resumed seamlessly, but additional signaling and table management are required
Solution Approach 1:
The gateway server performs preliminary actions by establishing and storing the persistent tunnel IP address mapping before the VPN tunnel switch occurs. This advance preparation eliminates the need for complex real-time negotiations when the client reconnects, as the mapping is already in place and can be immediately applied to maintain the remote server connection.
Data Source
AI summary
Resumption of a remote connection is described with a previous secure tunnel IP address. In embodiments, a first secure tunnel is facilitated with a client. The first secure tunnel has a tunnel IP address. The tunnel IP address is sent to the client. Packets are communicated from the client received through the first secure tunnel to a remote server using the tunnel IP address in the first secure tunnel. The first secure tunnel is closed and a second secure tunnel is facilitated with the client. A request is received from the client to resume the remote connection, that includes the tunnel IP address. The remote connection is resumed by communicating packets from the client received through the second secure tunnel to the remote server using the tunnel IP address in the second secure tunnel.