From 788de4f7ba5e2fedc6a7e3a3e07e825faf5c54c2 Mon Sep 17 00:00:00 2001 From: Yang Tse Date: Mon, 26 Nov 2007 14:07:09 +0000 Subject: 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. --- tests/runtests.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- cgit v1.2.3