<p dir="ltr">Man sshd_config<br></p>
<p dir="ltr"> GatewayPorts<br>
Specifies whether remote hosts are allowed to connect to ports<br>
forwarded for the client. By default, sshd(8) binds remote port<br>
forwardings to the loopback address. This prevents other remote<br>
hosts from connecting to forwarded ports. GatewayPorts can be<br>
used to specify that sshd should allow remote port forwardings to<br>
bind to non-loopback addresses, thus allowing other hosts to con-<br>
nect. The argument may be ``no'' to force remote port forward-<br>
ings to be available to the local host only, ``yes'' to force<br>
remote port forwardings to bind to the wildcard address, or<br>
``clientspecified'' to allow the client to select the address to<br>
which the forwarding is bound. The default is ``no''.<br>
</p>
<div class="gmail_quote">On Oct 25, 2013 3:11 PM, "L. V. Lammert" <<a href="mailto:lvl@omnitec.net">lvl@omnitec.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Ran into an interesting problem today, .. on BSD and CentOS 5.4, when a<br>
reverse SSH tunnel is setup it binds to all IPs on the host:<br>
<br>
tcp 0 0 *.2210 *.* LISTEN<br>
tcp6 0 0 *.2210 *.* LISTEN<br>
<br>
With a more modern Linux, the *SAME* command binds to 127.0.0.1 ONLY:<br>
<br>
tcp 0 0 <a href="http://127.0.0.1:2205" target="_blank">127.0.0.1:2205</a> 0.0.0.0:* LISTEN<br>
tcp 0 0 ::1:2205 :::* LISTEN<br>
<br>
What must be done on a modern Linux kernel so that incoming connections<br>
can also use the port?<br>
<br>
Thanks!<br>
<br>
Lee<br>
_______________________________________________<br>
grlug mailing list<br>
<a href="mailto:grlug@grlug.org">grlug@grlug.org</a><br>
<a href="http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug" target="_blank">http://shinobu.grlug.org/cgi-bin/mailman/listinfo/grlug</a><br>
</blockquote></div>