On Mon, 30 Jan 2017 06:03:08 +0530 deva seetharam <deva.seetharam@xxxxxxxxx> wrote: > sorry, it does not make sense because it is a reverse tunnel. that is, > the server that is running the firewall gets the connection requests > on that port (2222). i see that the port opens (can see it using nmap) > up as soon as the tunnel is up. however, IPTABLES does not have that > port open. that is what is confusing. That's because the 'reverse' tunnel flows across the encrypted SSH connection. The server's firewall never sees the traffic; it only sees packets flowing across the existing connection. When a program on the server connects to localhost:2222 (or to remotehost.com:2222), SSH itself listens on that socket and communicates with the SSH instance running on the laptop to connect to the host:port specified in the '-R' option. The traffic for that connection flows across (is tunneled through) the encrypted SSH connection. -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
