Accessing local network devices via mesh network devices

1 . A meshnet infrastructure device associated with a first device that is in communication with a second device in a mesh network, the meshnet infrastructure device comprising:

a memory; and

a processor communicatively coupled to the memory, the memory and the processor being configured to:

configure the first device to receive, from the second device via a meshnet connection in the mesh network, connection information indicating a domain name services (DNS) server associated with a local area network (LAN) to which the second device is connected;

configure the first device to transmit, to the DNS server based at least in part on utilizing the connection information, a query to receive a subnet internet protocol (IP) address assigned to a LAN device;

configure the first device to receive, from the DNS server based at least in part on transmitting the query, the subnet IP address assigned to the LAN device;

configure the first device to determine, based at least in part on receiving the subnet IP address assigned to the LAN device from the DNS server, that the LAN device is connected to the LAN; and

configure the first device to transmit, to the second device via the meshnet connection in the mesh network, a meshnet packet including data to be transmitted by the second device to the LAN device based at least in part on utilizing the subnet IP address assigned to the LAN device.

2 . The meshnet infrastructure device of claim 1 , wherein, to configure the first device to transmit the initiation meshnet packet, the memory and the processor are configured to configure the first device to encrypt the initiation meshnet packet based at least in part on utilizing a cryptographic key associated with the meshnet connection.

3 . The meshnet infrastructure device of claim 1 , wherein, to configure the first device to transmit the initiation meshnet packet including data, the memory and the processor are configured to configure the first device to transmit the initiation packet with a payload that includes an initiation network packet to be transmitted by the second device to the LAN device.

4 . The meshnet infrastructure device of claim 1 , wherein, to configure the first device to transmit the initiation meshnet packet including data, the memory and the processor are configured to configure the first device to transmit the initiation meshnet packet with information indicating that the data is to be transmitted by the second device to the LAN device.

5 . The meshnet infrastructure device of claim 1 , wherein, to configure the first device to transmit the query, the memory and the processor are configured to configure the first device to transmit identification information to identify the LAN device.

6 . The meshnet infrastructure device of claim 1 , wherein the memory and the processor are configured to:

configure the first device to receive, from the second device based at least in part on transmitting the initiation meshnet packet, a response meshnet packet with a payload that includes a response network packet transmitted by the LAN device.

7 . The meshnet infrastructure device of claim 1 , wherein, to configure the first device to receive the connection information, the memory and the processor are configured to configure the first device to receive encrypted connection information that is encrypted based at least in part on utilizing a cryptographic key associated with the meshnet connection.

8 . A method in a meshnet infrastructure device associated with a first device that is in communication with a second device in a mesh network, the method comprising:

configuring the first device to receive, from the second device via a meshnet connection in the mesh network, connection information indicating a domain name services (DNS) server associated with a local area network (LAN) to which the second device is connected;

configuring the first device to transmit, to the DNS server based at least in part on utilizing the connection information, a query to receive a subnet internet protocol (IP) address assigned to a LAN device;

configuring the first device to receive, from the DNS server based at least in part on transmitting the query, the subnet IP address assigned to the LAN device;

configuring the first device to determine, based at least in part on receiving the subnet IP address assigned to the LAN device from the DNS server, that the LAN device is connected to the LAN; and

configuring the first device to transmit, to the second device via the meshnet connection in the mesh network, a meshnet packet including data to be transmitted by the second device to the LAN device based at least in part on utilizing the subnet IP address assigned to the LAN device.

9 . The method of claim 8 , wherein configuring the first device to transmit the initiation meshnet packet includes configuring the first device to encrypt the initiation meshnet packet based at least in part on utilizing a cryptographic key associated with the meshnet connection.

10 . The method of claim 8 , wherein configuring the first device to transmit the initiation meshnet packet including data includes configuring the first device to transmit the initiation packet with a payload that includes an initiation network packet to be transmitted by the second device to the LAN device.

11 . The method of claim 8 , wherein configuring the first device transmit the initiation meshnet packet including data includes configuring the first device to transmit the initiation meshnet packet with information indicating that the data is to be transmitted by the second device to the LAN device.

12 . The method of claim 8 , wherein configuring the first device to transmit the query includes configuring the first device to transmit identification information to identify the LAN device.

13 . The method of claim 8 , further comprising:

configuring the first device to receive, from the second device based at least in part on transmitting the initiation meshnet packet, a response meshnet packet with a payload that includes a response network packet transmitted by the LAN device.

14 . The method of claim 8 , wherein configuring the first device to receive the connection information includes configuring the first device to receive encrypted connection information that is encrypted based at least in part on utilizing a cryptographic key associated with the meshnet connection.

15 . A non-transitory computer-readable medium configured to store instructions, which when executed by a processor related to a meshnet infrastructure device associated with a first device that is in communication with a second device in a mesh network, configure the processor to:

configure the first device to receive, from the second device via a meshnet connection in the mesh network, connection information indicating a domain name services (DNS) server associated with a local area network (LAN) to which the second device is connected;

configure the first device to transmit, to the DNS server based at least in part on utilizing the connection information, a query to receive a subnet internet protocol (IP) address assigned to a LAN device;

configure the first device to receive, from the DNS server based at least in part on transmitting the query, the subnet IP address assigned to the LAN device;

configure the first device to determine, based at least in part on receiving the subnet IP address assigned to the LAN device from the DNS server, that the LAN device is connected to the LAN; and

configure the first device to transmit, to the second device via the meshnet connection in the mesh network, a meshnet packet including data to be transmitted by the second device to the LAN device based at least in part on utilizing the subnet IP address assigned to the LAN device.

16 . The non-transitory computer-readable medium of claim 15 , wherein, to configure the first device to transmit the initiation meshnet packet, the processor is configured to configure the first device to encrypt the initiation meshnet packet based at least in part on utilizing a cryptographic key associated with the meshnet connection.

17 . The non-transitory computer-readable medium of claim 15 , wherein, to configure the first device to transmit the initiation meshnet packet including data, the processor is configured to configure the first device to transmit the initiation packet with a payload that includes an initiation network packet to be transmitted by the second device to the LAN device.

18 . The non-transitory computer-readable medium of claim 15 , wherein, to configure the first device to transmit the initiation meshnet packet including data, the processor is configured to configure the first device to transmit the initiation meshnet packet with information indicating that the data is to be transmitted by the second device to the LAN device.

19 . The non-transitory computer-readable medium of claim 15 , wherein, to configure the first device to transmit the query, the processor is configured to configure the first device to transmit identification information to identify the LAN device.

20 . The non-transitory computer-readable medium of claim 15 , wherein the processor is configured to:

configure the first device to receive, from the second device based at least in part on transmitting the initiation meshnet packet, a response meshnet packet with a payload that includes a response network packet transmitted by the LAN device.