A TCP/UDP self-hostable network tunneling solution that supports IPv4 and IPv6
Report Bug
·
Request Feature
Table of Contents
Netmask is a robust tool designed to facilitate secure and seamless network tunneling, similar to Ngrok, but with the added advantage of supporting TCP/UDP protocols and being entirely self-hostable. This makes it an excellent choice for users who need more control over their tunneling solutions, especially in environments where they require flexibility and security.
This is an example of how you may give instructions on setting up your project locally. To get a local copy up and running follow these simple example steps.
Netmask is built with simplicity in mind, it only requires a base installation of python 3.6 or above.
Method 1 (PIP):
- Install netmask from PIP
pip install netmask
Method 2 (GIT):
- Clone the repo
git clone https://github.com/josephdove/netmask
- Build and install
python3 setup.py install
Netmask is subdivided into two main components: the client (netmaskc) and the server (netmasks). The client and the server communicate on an encrypted stream with the key being based on the communication key, meaning that the client will only be able to communicate to the server while having the same key as the server. The default communication key is 0.
Netmask Server (netmasks): The server component, netmasks, is responsible for listening to incoming connections from clients and managing the tunnels.
Key Arguments for netmasks:
--port <port>: Specifies the port on which the server will listen for incoming connections. (DEFAULT: 1024)
--key <key>: Sets the communication key that the server and client will use. (DEFAULT: 0)
--verbose: Prints debug information.
listener4: This is the IPv4 address to bind to, if none, specify "-". (EXAMPLE: 0.0.0.0)
listener6: This is the IPv6 address to bind to, if none, specify "-". (EXAMPLE: ::)
Netmask Client (netmaskc): The client component, netmaskc, is used to establish a connection to the netmasks server and create tunnels. It forwards traffic from the local machine to the server, which then handles the routing to the intended destination.
Key Arguments for netmaskc:
--key <key>: Sets the communication key that the server and client will use. (DEFAULT: 0)
--verbose: Prints debug information (REQUIRES --nogui).
--nogui: Removes the GUI interface.
protocol: Can either be "tcp" or "udp", this specifies the protocol used while binding.
port: This is the port on the current host that we want to forward. (EXAMPLE: 443)
ipVersion: This is the IP version we want to use, must be either 4 or 6.
server: This is the server we want to connect to. MAKE SURE TO SPECIFY THE PORT (EXAMPLE: 127.0.0.1:1024)
- UDP Support
- Automatic TLS
- Kill connections from client (From GUI)
- Control panel for server (HTTP)
See the open issues for a full list of proposed features (and known issues).
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature) - Commit your Changes (
git commit -m 'Add some AmazingFeature') - Push to the Branch (
git push origin feature/AmazingFeature) - Open a Pull Request
Distributed under the MIT License. See LICENSE.txt for more information.
Your Name - josephdove@proton.me
Project Link: https://github.com/josephdove/netmask