Verify Meshnet services using this container

[MattsBos]

Container platforms mostly use overlay networks to enable the network abstraction layer. Since Meshnet is a service relying and depending on networking, and is not originally intended to be run in a container, it's possible not all Meshnet services function as expected.

Routing through this container using the Meshnet network is working fine, this is my original use-case, to use a Meshnet node/peer as an exit node like any traditional VPN.

Local network access works as expected. All local IP ranges (RFC 1918) seem to be available. Blocking this access will initiate firewall rules to block all non-internet routable IP ranges. The fact that NordVPN runs in a container does not change anything about this functionality.

To be tested:

• Does the filesharing function work? Is this even something that should be enabled/used within a container?
• Does the Remote Access service work? According to the docs this allows Pings and other direct connected service access.

[MattsBos]

Updated with new tests, local network access and blocking local access works as expected.