Providing an explicit bind address besides the port for dynamic application-level

port forwarding, our socks port, prevents ssh from running on some systems.

By default, ssh binds local port forwardings to the loopback address, since this
was the address being given as the explicit bind address, now it isn't given.
This commit is contained in:
Yang Tse 2007-11-26 14:07:09 +00:00
parent ebce0a16f6
commit 788de4f7ba
1 changed files with 1 additions and 1 deletions

View File

@ -1105,7 +1105,7 @@ sub runsocksserver {
}
my $flag=$debugprotocol?"-v ":"";
my $cmd="ssh -D ${HOSTIP}:$SOCKSPORT -N -F curl_ssh_config ${USER}\@${HOSTIP} -p ${SSHPORT} -vv >log/ssh.log 2>&1";
my $cmd="ssh -D $SOCKSPORT -N -F curl_ssh_config ${USER}\@${HOSTIP} -p ${SSHPORT} -vv >log/ssh.log 2>&1";
logmsg "TRACESSH:runsocksserver: calling startnew with cmd: $cmd\n";
my ($sshpid, $pid2) =
startnew($cmd, $pidfile, 15, 1); # start the server in a new process