In a scenario where one machine has access to the internet, and a remote machine does not (due to firewall restrictions), but is accessible via a VPN or something. There is a way to provide internet access for this remote machine.<\/p>\n\n\n\n
One way this can be achieved with dynamic port forwarding in SSH, at least for HTTP requests.<\/p>\n\n\n\n
Suppose From If already connected, try the escape code This will open a socks proxy in Next step is to setup this proxy to be used by This way, the HTTP (and HTTPS) requests should be redirected via our new proxy. Using Git will use the environment variables (as it uses libcurl for HTTP requests) but you can configure so that only git uses the proxy, or maybe only some repositories:<\/p>\n\n\n\n <\/p>\n\n\n\n Of course circumventing firewall restrictions with this can be a security hazard and can be against company security rules.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" In a scenario where one machine has access to the internet, and a remote machine does not (due to firewall restrictions), but is accessible via a VPN or something. There is a way to provide internet access for this remote machine. One way this can be achieved with dynamic port forwarding in SSH, at least … <\/p>\nhostA <\/code>is the local machine, which can access the internet; and hostB <\/code>is the machine that is accessible from hostA <\/code>but its access do the internet is blocked by a firewall.<\/p>\n\n\n\nhostA<\/code>, connect to hostB<\/code>:<\/p>\n\n\n\nssh -R localhost:1080 user@hostB<\/code><\/code><\/pre>\n\n\n\n~C<\/code> (after an <ENTER><\/code>) and enter the command and <ENTER><\/code><\/p>\n\n\n\n-R localhost:1080<\/code><\/code><\/pre>\n\n\n\nhostB <\/code>in port 9000, that will forward connections through the SSH connection to be coming out of hostA<\/code>.<\/p>\n\n\n\nhostB<\/code>. For several terminal applications its possible to set this up by exporting a few environment variables.<\/p>\n\n\n\nexport http_proxy=\"socks5h:\/\/localhost:1080\"\nexport https_proxy=\"socks5h:\/\/localhost:1080\"<\/code><\/code><\/pre>\n\n\n\n\"socks5h\"<\/code> will also resolve the DNS for these requests via proxy, \"socks5\"<\/code> will try to resolve DNS locally and then make the request to the proxy. This should work for most applications that uses HTTP requests through cURL (older wget versions do no support socks proxies).<\/p>\n\n\n\n# configure for this repository only\ngit config http.proxy socks5h:\/\/localhost:1080<\/code>\n# configure for all repositories\ngit config --global http.proxy socks5h:\/\/localhost:1080<\/code><\/code><\/pre>\n\n\n\n