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.

diff --git a/tests/runtests.pl b/tests/runtests.pl
index 165fd090420f70cdbb2f1a4f0acb48394cb7889f..1ae0f065551efcd12cf9d7abc3530ab9d695d32a 100755 (executable)
--- 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