# Gtunnel | A Robust Tunelling Solution Written In Golang **URL:** \ **Category:** Tools & Scripts\ **Tags:** tools, programming\ **Created:** [August 10, 2020, 2:37pm UTC](https://onehack.st/t/gtunnel-a-robust-tunelling-solution-written-in-golang/100235 "2020-08-10T14:37:17Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Prometheus](https://onehack.st/user_avatar/onehack.st/prometheus/32/34950_2.png) [@Prometheus](https://onehack.st/u/Prometheus)\ **Post date:** [August 10, 2020, 2:37pm UTC](https://onehack.st/t/gtunnel-a-robust-tunelling-solution-written-in-golang/100235/1 "2020-08-10T14:37:17Z")
![image](https://onehack.st/uploads/default/original/3X/a/1/a1597241a233b6dd5f8eeeb75df2e66486de61b5.jpeg) A TCP tunneling suite built with golang and gRPC. gTunnel can manage multiple forward and reverse tunnels that are all carried over a single TCP/HTTP2 connection. I wanted to learn a new language, so I picked go and gRPC. Client executables have been tested on windows and linux. **Dependencies** gTunnel has been tested with Docker version 19.03.6, but any version of docker should do. **How to use.** The start\_server.sh script will build a docker image and start it with no exposed ports. If you plan on using forward tunnels, make sure to map those ports or to change the docker network. ./start\_server.sh This will eventually provide you with the following prompt: ```auto _______________ __________ __________________. _______ _____ /| | \ _ _____/| | /___ | | | | // | / | | __)_ | | / /_/ >| | | | // | / | | | |___ ___/ |____ | | ______/____ | __/____ | __//_______ /| _______/_____ / / / / />>> ``` The first thing to do is generate a client to run on the remote system. For a windows client named “win-client” ```auto >>> configclient win 172.17.0.1 443 win-client ``` For a linux client named lclient ```auto >>> configclient linux 172.17.0.1 443 lclient ``` This will output a configured executable in the “configured” directory, relative to ./start\_server.sh Once you run the executable on the remote system, you will be notified of the client connecting ```auto _______________ __________ __________________. _______ _____ /| | \ _ _____/| | /___ | | | | // | / | | __)_ | | / /_/ >| | | | // | / | | | |___ ___/ |____ | | ______/____ | __/____ | __//_______ /| _______/_____ / / / / />>> configclient linux 127.0.0.1 443 test>>> 2020/03/20 22:01:47 Endpoint connected: id: test>>> ``` To use the newly connected client, type use and the name of the client. Tab completion is supported. ```auto >>> use test(test) >>> ``` The prompt will change to indicate with which endpoint you’re currently working. From here, you can add or remove tunnels. The format is ```auto addtunnel (local | remote) listenPort destinationIP destinationPort ``` For example, to open a local tunnel on port 4444 to the ip 10.10.1.5 in the remote network on port 445 and name it “smbtun”, the command would be as follows: ```auto addtunnel local 4444 10.10.1.5 445 smbtun ``` Similarly, to open a port on the remote system on port 666 and forward all traffic to 192.168.1.10 on port 443 in the local network, the command would be as follows: ```auto addtunnel remote 666 192.168.1.10 443 ``` Note that the name is optional, and if not provide, will be given random characters as a name. To list out all active tunnels, use the “listtunnels” command. ```auto (test) >>> listtunnelsTunnel ID: smbtunTunnel ID: dVck5Zba ``` To delete a tunnel, use the “deltunnel” command: ```auto (test) >>> deltunnel smbtunDeleting tunnel : smbtun ``` To start a socks proxy server on target, use the socks command. The following command will start a socks server on port 1080 on the host running gClient. Usually, you will need to create a tunnel from the gTunnel prompt to use the socks server. ```auto socks 1080addtunnel local 1080 127.0.0.1 1080 ``` To go back and work with another remote system, use the back command: ```auto (test) >>> back>>> ``` Notice how the prompt has changed to indicate it is no longer working with a particular client. To disconnect a client from the server, you can either issue the “disconnect” command while using the client, or provide the endpoint id in the main menu. ```auto (test) >>> disconnect2020/03/20 22:14:52 Disconnecting test(test) >>> 2020/03/20 22:14:52 Endpoint disconnected: test>>> ``` Or ```auto >>> disconnect test2020/03/20 22:16:00 Disconnecting test>>> 2020/03/20 22:16:00 Endpoint disconnected: test>>> ``` To exit out of the server, run the exit command: ```auto >>> exit ``` Note that this will remove the docker container, but any tls generated certificates and configured executables will be in the tls/ and configured/ directories. **TODO** Reverse tunnel support Multiple tunnel support Better print out support for tunnels. It should show how many connections are established and ports, etc. Add REST API and implement web UI Dynamic socks proxy support. Authentication between client and server Server configuration file on input with pre-configured tunnels **Known Issues** - Intenet Explorer is causing the client to lock up on reverse tunnels - The startup server script should reuse the built image, not create a new one every time. ## GitHub: > **[GitHub - hotnops/gtunnel: A robust tunelling solution written in golang](https://github.com/hotnops/gtunnel)** > > A robust tunelling solution written in golang