New answers tagged router
It's not possible to connect to a port-forwarded public IP address from inside the same LAN. To explain this, I'll need an example. Let's suppose your router's private IP is 192.168.1.1 with public IP 10.1.1.1. Your server is on 192.168.1.2 port 2222. You set up port forwarding from 10.1.1.1:1111 to 192.168.1.2:2222. If somebody on the Internet ...
Ports 23 and 80 open are because for connection to your router, port 23 to telnet to your router and port 80 to have your WebUI of your router. Since only these two are open port-forwarding is not in the picture. So a router restart and your SSH server restart will help.
You can do this through ssh's ProxyCommand facility. Add the following to your $HOME/.ssh/config file. Create it if it doesn't exist with just this content: Host remoteserverX User userint ProxyCommand ssh userext@externalserver nc remoteserverX %p Host remoteserverY User userint ProxyCommand ssh userext@externalserver nc remoteserverY %p ...
There will be various approaches depending on how you want to connect to the fileserver. One option is to port forward FTP traffic so that when you FTP to your "router" it passes it though to the fileserver. The shorewall documents might be of use here. http://articles.slicehost.com/2007/10/10/rsync-exclude-files-and-folders The only issue with that is ...
Top 50 recent answers are included