Persistent VPN IP Allocation With Static Routing Across Server Instances
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SSL VPN tunnel systems do not allow a VPN client to maintain the same IP address across multiple connections, as different server instances manage non-overlapping address pools, leading to inconsistent IP allocation.
Innovation Solution
Assign a static IP address to a VPN client and add it to a routing table, specifying the interface for routing traffic, ensuring the same IP address is used across disconnections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If multiple server instances each manage a subset of IP addresses from a fixed pool, then the number of tunnels that can be managed is increased, but a client cannot receive the same IP address over different connections involving different server instances
Solution Approach 1:
The system segments IP address management by creating separate IP address pools for each server instance rather than using a single shared pool. Each server instance is assigned a unique IP address pool, ensuring that when a client reconnects to a different server instance, they receive the same IP address from that instance's pool. This segmentation resolves the contradiction by allowing multiple servers to manage tunnels independently while maintaining IP consistency for each client across server transitions.
2Ease of operation
If each server instance manages its own non-overlapping IP address pool, then server independence is improved, but IP address portability between server instances deteriorates
Solution Approach 1:
The system introduces a front end component as an intermediary between clients and server instances. The front end maintains client connection information and uses a load balancer algorithm to direct requests to appropriate server instances. When a client reconnects, the front end ensures they are directed to a server instance that can provide their assigned IP address, thus maintaining IP portability while preserving server instance independence through the intermediary layer.
Data Source
AI summary
Systems and methods for assigning a persistent internet protocol (IP) address to a virtual private network (VPN) client. The method includes receiving, at a first server, a request for access from a first VPN client, the request including access credentials and the first server having a routing table; sending, from the first server, the access credentials to an access server; receiving, from the access server at the first server, a first static IP address to be assigned to the first VPN client, wherein the first static IP address is selected from a plurality of available static IP addresses; assigning the first static IP address to the first VPN client; and adding the first static IP address to a static routing path in the routing table, the static routing path specifying an interface to which traffic associated with the first VPN client is to be routed. The static routing path is configured to be referenced to enable traffic associated with the first VPN client to be directed through the interface.