Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to expose TCP connections #123

Merged
merged 26 commits into from
Sep 8, 2020
Merged

Add ability to expose TCP connections #123

merged 26 commits into from
Sep 8, 2020

Conversation

mpociot
Copy link
Member

@mpociot mpociot commented Sep 7, 2020

This PR adds the ability to not only share HTTP connections, but also raw TCP connections.

The server will then assign a random port to the connection and forward all traffic from that port to the local destination port on the exposed computer.

Example:

expose share-port 2525

Todo:

  • Add a new column to the users table to only allow TCP tunnels for specific users
  • Make the port range configurable
  • Attach TCP control connections to the auth token and show them in the API responses

@mpociot mpociot merged commit 2f57fa1 into master Sep 8, 2020
@moisesh18
Copy link

moisesh18 commented Oct 11, 2020

Hi. With sharing TCP port feature activated, --subdomain option is allowed?.

UPDATE: I tried this new feature, but just realized that this PR is not in the master, since the last version (3.1.4) was released in Jul 28, and this post is from Sept 8. Thank u. I'l aware this feature!
image

@ldub
Copy link

ldub commented Nov 24, 2020

hey @mpociot, sorry to revive a merged PR, but do you think you could do a release of expose sometime soon to include this code? tunneling tcp connections is super useful and i'm looking forward to this feature :)

@MeestorX
Copy link

Is TCP tunnelling part of this or not? It seems to have been merged, but as above, the share-port command doesn't work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants