Feat: Support TCP proxy

[nodauf]

Hi,

Like several others, I encountered a use case where I needed to connect via SSH to a remote Docker container and proxy raw TCP connections (see issues #252, #242, #221).

This PR introduces support for that feature. When a TCP protocol is specified in the Docker label (e.g. tsdproxy.port.1=22/tcp:22/tcp,no_autodetect), the proxy will use a TCP proxy instead of the default HTTP one.

[patrickwolf]

This PR introduces support for that feature. When a TCP protocol is specified in the Docker label the proxy will use a TCP proxy instead of the default HTTP one.

Thanks. How exciting is this? :) @almeidapaulopt can this be accepted and merged in please? :)

[mkawczynski07]

@nodauf great work! @almeidapaulopt It will be nice to have that merged. I want to use TSD Proxy in my new setup, but I must expose PostgreSQL DB connections. Now it is not possible. Please merge that :)

[patrickwolf]

And I need to access my machines via SSH to connect via VSCode with them and can't do that either yet so can't use TSDProxy for those yet... Please merge :)

[patrickwolf]

@almeidapaulopt have you had a chance to look at this pull request? i'm needing this functionality every day and just have to deploy a new container and am wondering if i need the old tailscale side car route when I would prefer to use tsdproxy but i just need the ssh support... and in this moment i'm wondering how to build tsdproxy from this PR but obviously would prefer if it was included.

so just sending a gentle nudge your way and thank you for the tool!! :)

[nodauf]

@patrickwolf would you be interesting to test the PR. If you validate the correct implementation and that it work for you, it would maybe help for the review.

[patrickwolf]

Yes I'd be happy to. Could you give me easy instructions on how to turn this PR into a docker container I can use for the test?

[nodauf]

I will try to publish a Docker image this week or the next one, and I'll let you know once it's done.

[almeidapaulopt]

I will try to publish a Docker image this week or the next one, and I'll let you know once it's done.

Thank you for you contribution, I've made some changes. Can you look at it, please?

[patrickwolf]

Nice I'm excited @almeidapaulopt and @nodauf ... it will make tsdproxy usable in so many more scenarios!!

[nodauf]

All good with the last commit

[nodauf]

@patrickwolf So you can test these changes while the PR is waiting to be merged, I've published a Docker image (https://hub.docker.com/r/nodauf/tsdproxy/tags)

This image includes the main feature from this PR and the changes from #260.
You can see the specific commits here:

• Commits: https://github.com/nodauf/tsdproxy/commits/main/

Let me know if this works for you!

[Zolfax]

I've tested your docker image, it works great.
Thank you.
I've specifically tried mounting a samba share from a different location.
This was not possible with the current TSDProxy image.

Usecase is a non-docker server that is part of lists.
Here's my nas.yaml file for reference:

nas:
  proxyProvider: default
  tailscale:
    ephemeral: true
  ports:
    445/tcp:
      targets:
        - tcp://<hostname>:445
    443/https:
      targets:
        - https://<hostname>:8443

[nodauf]

Thank you for your feedback

[jukoby]

Thank you for doing this.
Is this ready to be merged? @almeidapaulopt
I could test it too if it's needed.

[almarzn]

This project seems unmaintained for now. Maybe we should try and maintain a proper fork?

[subey]

It works for me too - thank you!.
Without it, when I tried to connect, I got: "http2: failed reading the frame payload: %!w(), note that the frame header looked like an HTTP/1.1 header"

[patrickwolf]

@patrickwolf So you can test these changes while the PR is waiting to be merged, I've published a Docker image (https://hub.docker.com/r/nodauf/tsdproxy/tags)

Sorry that I have not been able to test it yet. My work pulled me in different directions for now

[mattdale77]

I'm interested in this for git. Commenting so I see updates

[totza2010]

I still hope this code will be integrated and further developed.

[almeidapaulopt]

Closing this PR — TCP proxy support is already implemented on main. The codebase already has a tcpPort struct in internal/proxymanager/port.go with proper net.Conn-based bidirectional forwarding, context cancellation, and error handling. It's integrated into the port initialization via newPortTCP() in proxy.go:137. The existing implementation is cleaner as it uses standard net.Conn instead of gvisor/gonet.TCPConn, avoiding the heavy gvisor dependency and the type assertion risk. Thank you for the contribution, nodauf!

[mattdale77]

Is there an example somewhere of using docker compose labels to use this feature?

[almeidapaulopt]

look a https://almeidapaulopt.github.io/tsdproxy/docs/providers/docker-reference/#common-patterns