vakuum / tcptunnel Goto Github PK

nevermind

After a bit of time with these options

./tcptunnel --local-port=2525 --remote-port=25 --remote-host=localhost  --stay-alive --fork

I get:

wait_for_clients: accept(): Too many open files

Will this also support amqp ?

Hi, i haved this error "build_server: bind(): Address already in use",
tcptunnel.exe --local-port=3389 --remote-port=61500 --remote-host=xxxxxx.xx

I want to redirect my 3389 traffic to an external server but it tells me that post 3389 and is already in use (RDP), it seems to me that this program what it does is open a port ... what I need is to listen to that port and compose it. regards

In tcptunnel.h: socket fds are stored in unsigned int variables.

that makes conditions like if (rc.server_socket < 0) never be satisfied.

I am trying to use this for sql connection tunneling. Is this supported for sql server port 1433

Hi

I use iperf test for concurrent connections.

but the second connection was not get data.

iperf concurrent connection with only 2.

so,it can't be concurrent connection?

If I use Ctrl+c to quit first iperf,It will show error with "build_tunnel: connect(): Connection refused".

I start tcptunnel with:

./tcptunnel --local-port=8080 --remote-port=8888 --remote-host=127.0.0.1 --bind-address=127.0.0.1 --stay-alive

And start iperf with:

iperf -s -p 8888 -B 127.0.0.1

use a bash command to test:

iperf -c 127.0.0.1 -p 8080 -t 60 &
iperf -c 127.0.0.1 -p 8080 -t 60 &

If I use nc -l -p 8888, and start nc 127.0.0.1 8080 to use first connection, after that use iperf -s -p 8888 -B 127.0.0.1 to use second connection. nc will work perfectly, but iperf will not get data.

Thank you!

First of all, forgive my ignorance on TCP.

I use tcptunnel to proxy traffic from one PC to another on my LAN that is connected to a VPN to piggyback off that VPN connection. I route two tunnels: HTTP and git over ssh and it works remarkably well. Until it doesn't.

Seemingly spontaneously the connection will break and I will have to reset it. Sometimes it won't do this for hours and other times it happens every few minutes. This is the Mac version of tcptunnel installed via Homebrew on an Apple Silicon machine.

The output is always the following:

use_tunnel: recv(rc.client_socket): Connection reset by peer

I route the HTTP traffic by starting the tunnel like this:

// VPN connected machine LAN IP = 1.2.3.4
// IP of machine only accessible with VPN = 4.3.2.1
$ sudo tcptunnel --bind-address=1.2.3.4 --local-port=443 --remote-host=4.3.2.1 --remote-port=443 --stay-alive &

Same thing with different ports for git over ssh.

I thought the --stay-alive argument would prevent this from happening but evidently it does not.

Is it obvious to somebody what I am doing wrong?

Hi,

Using the option "--stay-alive" the connection with the server stays connected when the client disconnects from the "tcptunnel". So, in order to kill the connection this parameter can't be used.

However, without it the tunnel disappears when the first client disconnects. So, it's useful to use the parameter "--fork". But this parameter isn't supported in Windows.

Any idea or workaround?
Thank you!

$ ./configure
checking host system type... Linux
sed: -e expression #2, char 16: unknown option to `s'
configure: configure complete, now type 'make' and 'make install'.