US 12,407,641 B2
Updating meshnet internet protocol maps in a mesh network
Rytis Karpuška, Vilniaus r. (LT)
Assigned to UAB 360 IT, Vilnius (LT)
Filed by UAB 360 IT, Vilnius (LT)
Filed on May 25, 2022, as Appl. No. 17/824,383.
Application 17/824,383 is a continuation of application No. 17/752,788, filed on May 24, 2022, granted, now 11,646,992.
Prior Publication US 2023/0388191 A1, Nov. 30, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 61/25 (2022.01); H04L 41/0816 (2022.01); H04L 41/0823 (2022.01); H04L 41/12 (2022.01); H04L 45/74 (2022.01); H04L 61/2503 (2022.01); H04L 61/2514 (2022.01); H04L 67/12 (2022.01); H04L 61/4511 (2022.01)
CPC H04L 61/2503 (2013.01) [H04L 41/0816 (2013.01); H04L 41/0836 (2013.01); H04L 41/12 (2013.01); H04L 45/74 (2013.01); H04L 61/2514 (2013.01); H04L 67/12 (2013.01); H04L 61/4511 (2022.05)] 17 Claims
OG exemplary drawing
 
1. A method, comprising:
determining, by an infrastructure device associated with a mesh network that includes a first client device, that a second client device has joined the mesh network; and
transmitting, by the infrastructure device to the first client device at a time associated with determining that the second client device has joined the mesh network, communication information indicating a meshnet internet protocol (IP) address associated with the second client device to enable the first client device to update a meshnet address map to indicate an association of the second client device with the meshnet IP address, and to enable the first client device and the second client device to communicate with each other via a meshnet connection that is established between only the first client device and the second client device based at least in part on the first client device and the second client device privately negotiating one or more parameters for determining a cryptographic key for encrypted communication of meshnet data via the meshnet connection, wherein
the one or more parameters include a combination of (i) a first public key associated with the first client device, (ii) a second public key associated with the second client device, and (iii) one or more randomly generated numbers.