Look into NAT - from the perspective of your ISP and the rest of the world you will have a different public IP address than what you have as a private IP inside your home display when you run ip addr or ifconfig If you only create a tunnel between 2 devices on your LAN(local area network) the traffic will be encrypted and decrypted before hitting the internet. Please advise whether setting up tunneling in same network for purpose of proxy is even possible?Ĭreating the tunnel is possible, but it isn't going to help if those sites are being throttled by your ISP. This sort of thing is used to access Webservers that are firewalled off, or maybe your Tomcat app backend without going through your NGINX frontend or something like that. If you SSH'ed to the Pi, then that's where you'd look like you're coming from, if that's still subject to restrictions, you're still stuck. So if you went to in a browser, you'd see localhost on the server you SSH'ed to, not your client desktop/laptop machine. So, if you do your -D 8080 thing when ssh'ing, then set your browser or any app to use port 8080 on localhost (wrt your app, the proxy is started and listening on the same machine) then anything you type in the address bar will be accessed wrt the server side. If you're trying to get round "administrative restrictions", let's say a firewall on a box that locks down the Webserver to localhost connections, then your web connection (after it pops out the SSH tunnel on the server side) will look like it's coming from the server you SSH'ed to. I'm not sure I get what you mean with the local network and your intentions. If you're on Windows and using Putty as your client, this will be under Connection > SSH > Tunnels in the configuration. I should be more clear, that SOCKS proxy is opened up locally on your machine where you started your SSH connection from, your computer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |