aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorYang Tse <yangsita@gmail.com>2007-11-26 14:07:09 +0000
committerYang Tse <yangsita@gmail.com>2007-11-26 14:07:09 +0000
commit788de4f7ba5e2fedc6a7e3a3e07e825faf5c54c2 (patch)
treef7e1ccbc75d9ca7f952d89fe9ec71bb8a049206e
parentebce0a16f6b2587434ba5bcde5b40633bb17c54c (diff)
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.
-rwxr-xr-xtests/runtests.pl2
1 files changed, 1 insertions, 1 deletions
diff --git a/tests/runtests.pl b/tests/runtests.pl
index 165fd0904..1ae0f0655 100755
--- a/tests/runtests.pl
+++ b/tests/runtests.pl
@@ -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