Best tunneling practice

[DennisBlah]

Hi all,

I'm looking for a quick and easy solution for a OSX system.
I want internal clients (i.e. 10.0.0.10), to connect to a internal server (i.e. 10.0.0.11) on a specific port (i.e. 8181)
And have the server forward it to the internet (i.e. 48.123.222.88) on a different port (i.e. 3333)

How can I achieve this?
Would this be.. forwarding, tunneling, proxying ?

What software should I use and/or is there any best practices or quick and easy tutorials ?

I've downloaded tcptunnel but that's not working at all as far as I tried, the internal server does not open the port to listen on to tunnel it through. When I open a port with ie. netcat then it still won't be forwarded externally.

 

[belvdr]

You configure the router to forward that external port to the internal servers IP.

 

[DennisBlah]

You configure the router to forward that external port to the internal servers IP.

I wonder how you think this is even near a solution
Please read the first 2 lines again.

 

[belvdr]

I wonder how you think this is even near a solution
Please read the first 2 lines again.

Gee, sorry for misreading. Good luck with that attitude.

 

[LewisChapman]

I wonder how you think this is even near a solution
Please read the first 2 lines again.

Was going to assist until I read this rude post.

Good luck with your findings.

 

[Mikael H]

Hi all,

I'm looking for a quick and easy solution for a OSX system.
I want internal clients (i.e. 10.0.0.10), to connect to a internal server (i.e. 10.0.0.11) on a specific port (i.e. 8181)
And have the server forward it to the internet (i.e. 48.123.222.88) on a different port (i.e. 3333)

How can I achieve this?
Would this be.. forwarding, tunneling, proxying ?

What software should I use and/or is there any best practices or quick and easy tutorials ?

I've downloaded tcptunnel but that's not working at all as far as I tried, the internal server does not open the port to listen on to tunnel it through. When I open a port with ie. netcat then it still won't be forwarded externally.

If you want to reach singular services on the Internet this way, you’ll want to look into reverse proxying. Common products that approach the problem slightly differently from each other: HAProxy, Squid, nginx.
There’s a lot of tips out there, but when it comes to more advanced networking rules like this, I’d recommend actually learning the underlying concepts and the pros and cons of the different choices available, especially if you have any kind of security requirements for this solution. But with the product names I gave you, you have somewhere to start.