reverse-tunnel | Reverse tunnel TCP and UDP | Proxy library

by snsinfu Go Version: v1.3.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | reverse-tunnel Summary

reverse-tunnel is a Go library typically used in Networking, Proxy applications. reverse-tunnel has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

[Build Status][build-badge]][build-url] [Release][release-badge]][release-url] [MIT License][license-badge]] LICENSE.txt). [build-badge]: [build-url]: [release-badge]: [release-url]: [license-badge]: rtun is a tool for exposing TCP and UDP ports to the Internet via a public gateway server. You can expose ssh and mosh server on a machine behind firewall and NAT.

Support

Quality

Security

License

Reuse

Support

reverse-tunnel has a low active ecosystem.

It has 55 star(s) with 10 fork(s). There are 6 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 11 have been closed. On average issues are closed in 20 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of reverse-tunnel is v1.3.0

Quality

reverse-tunnel has 0 bugs and 0 code smells.

Security

reverse-tunnel has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

reverse-tunnel code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

reverse-tunnel is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

reverse-tunnel releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 1144 lines of code, 57 functions and 33 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed reverse-tunnel and discovered the below as its top functions. This is intended to give you an instant insight into reverse-tunnel implemented functionality, and help decide if they suit your requirements.

Start starts the agent
WebSocket upgrades websocket connection
Watch sends a ping message to the websocket connection
run runs the agent
extractAuthKey extracts the auth key from the request
NewService returns a new Service .
Add adds a session to the sessionStore
parsePort parses a string to a port number .
hookCancel executes the given function with the given context .
Load config file

Get all kandi verified functions for this library.

reverse-tunnel Key Features

No Key Features are available at this moment for reverse-tunnel.

reverse-tunnel Examples and Code Snippets

No Code Snippets are available at this moment for reverse-tunnel.

Community Discussions

Trending Discussions on reverse-tunnel

How to reverse SSH tunnel to remote docker container for Xdebug?

QUESTION

How to reverse SSH tunnel to remote docker container for Xdebug?

Asked 2020-Jun-26 at 03:56

There are many posts on SO and elsewhere on how to set this up. So far I've been unsuccessful in getting it working.

Setup
Local machine - Windows 10, with Cygwin, git bash, and WSL2 with Ubuntu installed; and MacBook Air (Mojave)
Host machine - AWS EC2 instance running Amazon Linux 2
Docker container - CentOS 7.8 running PHP with Xdebug

Goal
Remotely debug PHP code in container from local machine by utilizing a reverse tunnel from the local machine to the container.

I have gotten this working before when the PHP code was installed locally on the host machine, so the question is not around Xdebug. As soon as I moved the PHP code into the container, debugging no longer works.

What I've tried
Setting up a reverse tunnel from the local machine to the host EC2 instance works. For this I'm doing ssh -vvv -i "aws.pem" -R 9000:localhost:9000 user@ec2instance in terminal, cygwin, or git bash and testing with nc -z localhost 9000 || echo 'no tunnel open' on the host machine.

When I docker exec -it container bash into the container and run nc, the tunnel is not available.

I'm using docker-compose:

...

ANSWER

Answered 2020-Jun-26 at 03:56

I got this working. After reading up on the ssh man page and looking over things again, I realized I was binding to the docker container IP not the bridge (docker0) IP.

I updated my connect command to ssh -vvv -i "aws.pem" -R 9000:172.17.0.1:9000 user@ec2instance with the right IP and the tunnel started working. I do still have GatewayPorts enabled (per the man page) and removed the 9000:9000 mapping.

I then updated my xdebug.remote_host value to the same IP and debugging is now working. Not sure why host.docker.internal didn't work, but that's for another day.

Source https://stackoverflow.com/questions/62580411

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install reverse-tunnel

Compiled binaries are available in the [release page][release-url]. To build your own ones, clone the repository and make:.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: