I have a docker image running on localhost and what I want is to let the docker container communicate with my host's application on a specific port.

I cannot change the network=bridge docker configuration to anything else.

What I'm using right now:

screen ssh docker-container -R 16000:localhost:16000
[Ctrl] + A -> D

This means that there is an encryption layer, which is not needed at all and it adds latency to the communication, which is what I want to get rid of.

Can I establish a reverse port forwarding tunnel between two hosts without encryption?

I have a feeling like socat could be the solution.

  • Are you sure the latency from the encryption is measurable in any way? – ilkkachu Feb 22 '18 at 9:41
  • without encryption is just rsh – guiverc Feb 22 '18 at 9:47
  • 1
    @guiverc I think rsh doesn't support port forwarding at all, or am I wrong? – jirislav Feb 22 '18 at 9:49
  • @ilkkachu It would be measurable/comparable in a case when there would be a solution to my question :D – jirislav Feb 22 '18 at 9:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.