Granted Patent B2

US 12,506,639 · App. 17/734,039 · Granted Dec 23, 2025

Inventors: Veerabhushan K. Hatte (Fremont, CA); Narasimha Talapady Nayak (Cupertino, CA); Pavan Gururaj Katti (Santa Clara, CA)

Assignee: Versa Networks, Inc.

H04L12/4633H04L12/4641H04L63/0272H04L65/1066

Abstract

Claims (57)

1 . A method of maintaining communication between a remote server and a client through different secure tunnels, the method comprising:

at a virtual private network (VPN) gateway, facilitating a first VPN session between the client and the VPN gateway, the first VPN session having a tunnel Internet Protocol (IP) address that was assigned by the VPN gateway, the first VPN session using a first VPN protocol;

at the VPN gateway, sending the tunnel IP address to the client;

at the VPN gateway, changing the tunnel IP address to a routable gateway IP address and communicating packets from the client to the remote server using the routable gateway IP address as a source IP address to the remote server, wherein the packets are communicated from the client to the remote server through a remote connection of the VPN gateway with the remote server, and wherein the packets are received at the VPN gateway from the client through the first VPN session;

at the VPN gateway, closing the first VPN session between the client and the VPN gateway;

at the VPN gateway, facilitating a second VPN session between the client and the VPN gateway, the second VPN session using a second VPN protocol, which is different from the first VPN protocol;

at the VPN gateway, receiving a request from the client to resume the remote connection with the remote server, the request including the tunnel IP address that was previously assigned to the client by the VPN gateway; and

at the VPN gateway, resuming the remote connection by communicating packets from the client to the remote server using the routable gateway IP address as the source IP address to the remote server, wherein the packets are received at the VPN gateway from the client through the second VPN session.

2 . The method of claim 1 , further comprising assigning the received tunnel IP address to the second VPN session with the client in response to receiving the request.

3 . The method of claim 1 , further comprising:

receiving a request for a persistent tunnel IP address from the client through the first VPN session, and

wherein sending the tunnel IP address to the client is in response to receiving the request for a persistent tunnel IP address.

4 . The method of claim 1 , wherein sending the tunnel IP address to the client comprises sending the tunnel IP address in a Type Length Value (TLV) field of a virtual private network (VPN) protocol header through the first secure tunnel.

5 . The method of claim 1 , wherein the remote connection is a remote session between the client and the remote server, and wherein communicating packets comprises communicating packets in the first VPN session and in the second VPN session within the same remote session.

6 . The method of claim 1 , further comprising:

receiving a request for a persistent tunnel IP address with the client through the first VPN session;

facilitating the persistent tunnel IP address in response to the request for the persistent tunnel IP address; and

storing the tunnel IP address in association with a session identifier of a VPN session.

7 . The method of claim 6 , further comprising:

storing a parameter in association with the session identifier,

wherein receiving the request comprises receiving the session identifier from the client, and

validating the parameter before assigning the tunnel IP address through the second VPN session.

8 . The method of claim 7 , wherein the parameter includes an expiration and wherein validating the parameter comprises validating that the first VPN session has not expired.

9 . The method of claim 1 , wherein facilitating a first VPN session comprises connecting to a first secure session with the client wherein facilitating a second VPN session comprises connecting to a second secure session with the client, and wherein receiving a request from the client comprises receiving a session identifier for the first secure session.

10 . The method of claim 9 , further comprising applying the session identifier to verify the tunnel IP address.

11 . The method of claim 1 , further comprising comparing the tunnel IP address received from the client through the second VPN session to a stored tunnel IP address that is associated with the first VPN session.

12 . The method of claim 1 , wherein communicating packets through the first VPN session comprises de-capsulating packets received from the client with the tunnel IP address and forwarding the de-capsulated packets to the remote server using the routable gateway IP address as a source IP address to the remote server and an IP address of the remote server as a destination IP address.

13 . The method of claim 12 , further comprising storing the destination IP address in association with the tunnel IP address.

14 . A non-transitory computer-readable storage medium containing program instructions, which when executed by the computer cause the computer to perform operations comprising:

at a virtual private network (VPN) gateway, facilitating a first VPN session between the client and the VPN gateway, the first VPN session having a tunnel Internet Protocol (IP) address that was assigned by the VPN gateway, the first VPN session using a first VPN protocol;

at the VPN gateway, sending the tunnel IP address to the client;

at the VPN gateway, changing the tunnel IP address to a routable gateway IP address and communicating packets from the client to the remote server using the routable gateway IP address as a source IP address to the remote server, wherein the packets are communicated from the client to the remote server through a remote connection of the VPN gateway with the remote server, and wherein the packets are received at the VPN gateway from the client through the first VPN session;

at the VPN gateway, closing the first VPN session between the client and the VPN gateway;

at the VPN gateway, facilitating a second VPN session between the client and the VPN gateway, the second VPN session using a second VPN protocol, which is different from the first VPN protocol;

at the VPN gateway, receiving a request from the client to resume the remote connection with the remote server, the request including the tunnel IP address that was previously assigned to the client by the VPN gateway; and

at the VPN gateway, resuming the remote connection by communicating packets from the client to the remote server using the routable IP address as the source IP address to the remote server, wherein the packets are received at the VPN gateway from the client through the second VPN session.

15 . The medium of claim 14 , the operations further comprising:

storing the tunnel IP address in association with a remote session identifier for a remote session between the client and the remote server that includes the routable gateway IP address,

wherein resuming the remote connection comprises resuming the remote session using the remote session identifier.

16 . The medium of claim 14 , the operations further comprising

receiving a request for a persistent tunnel IP address through the first VPN session;

facilitating the persistent tunnel IP address with the client in response to the request for the persistent tunnel IP address;

storing the tunnel IP address in association with a session identifier of the persistent tunnel IP address;

storing an expiration parameter in association with the session identifier; and

validating the expiration parameter by validating that the first VPN session has not expired before assigning the tunnel IP address through the second secure tunnel.

17 . A method of maintaining communication with a remote server through different secure tunnels and a virtual private network (VPN) gateway, the method comprising:

at a client, establishing a first VPN session with the VPN gateway, the first VPN session having a tunnel Internet Protocol (IP) address that was assigned by the VPN gateway, the first VPN session using a first VPN protocol;

at the client, receiving the tunnel IP address from the VPN gateway;

at the client, communicating packets through a remote connection with the remote server, the packets communicated from the client to the VPN gateway through the first VPN session having the tunnel IP address changed to a routable gateway IP address and using the routable gateway IP address as a source IP address to the remote server;

at the client, closing the first VPN session with the VPN gateway;

at the client, establishing a second VPN session with the VPN gateway, the second VPN session using a second VPN protocol, which is different from the first VPN protocol;

at the client, sending a request to the VPN gateway to resume the remote connection, the request including the tunnel IP address that was previously assigned to the client by the VPN gateway; and

at the client, resuming the remote connection by communicating packets from the client to the remote server, wherein the packets are communicated from the client to the VPN gateway through the second VPN session using the tunnel IP address and the routable gateway IP address is used as the source IP address to the remote server.

18 . The method of claim 17 , further comprising:

sending a request for a persistent tunnel IP address from the client through the first VPN session in a Type Length Value (TLV) field of a virtual private network (VPN) protocol header.

19 . The method of claim 17 , wherein establishing a first VPN session comprises establishing the first a VPN session with the VPN gateway by a VPN client, the method further comprising establishing a remote session with the remote server by a web client, and wherein communicating packets to the remote server comprises sending packets from the web client in the remote session to the remote server through the VPN client in the first VPN session.

20 . The method of claim 1 , wherein receiving a request to resume the connection comprises receiving the request in a Type Length Value (TLV) field of a virtual private network (VPN) protocol header through the second secure tunnel.

Assignments (2)

Continuity (1)

References Cited (15)