[opensuse] socks5 and ssh in firefox
Though I've been using ssh in a basic way I've never until now looked into how to run something like Firefox on a remote machine residing in another country so as to get around country-specific annoyances. So I found this page: https://calomel.org/firefox_ssh_proxy.html and followed the instructions, went into the Firefox network settings on my local machine and chose SOCKS Host, put in 127.0.0.1 and port 8080, and checked the box for Proxy DNS when using SOCKS v5, but I see that by default, in the box 'No Proxy for' it already has localhost, 127.0.0.1 Wouldn't keeping that there defeat the object? Do I need to remove that? I tried removing it, then opened a terminal and did as suggested: ssh -C2qTnN -D 8080 {remote_machine} I see that by going to http://whatsmyip.org/ the remote IP address is shown and from testing a couple of sites, all seems to work as I need it to, but since I'll be wanting to do this occasionally and switch back and forth in the Firefox network settings, I don't understand if I should always remove that line in 'No Proxy for'? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/04/2018 à 22:17, gumb a écrit :
Though I've been using ssh in a basic way I've never until now looked into how to run something like Firefox on a remote machine residing in another country so as to get around country-specific annoyances.
if the remote machine is yours, the simpler way is to launch firefox on the remote jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 18/04/18 23:32, jdd@dodin.org wrote:
if the remote machine is yours, the simpler way is to launch firefox on the remote
I tried this but as Neil mentions in the other reply, it ran way too slow due to the bandwidth being gobbled by passing all the graphical interface data across the connection. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 19/04/2018 à 12:17, gumb a écrit :
On 18/04/18 23:32, jdd@dodin.org wrote:
if the remote machine is yours, the simpler way is to launch firefox on the remote
I tried this but as Neil mentions in the other reply, it ran way too slow due to the bandwidth being gobbled by passing all the graphical interface data across the connection.
no real problem here, but with fiber connection on local jdd -- http://dodin.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/18/2018 03:17 PM, gumb wrote:
Though I've been using ssh in a basic way I've never until now looked into how to run something like Firefox on a remote machine residing in another country so as to get around country-specific annoyances. So I found this page: https://calomel.org/firefox_ssh_proxy.html and followed the instructions, went into the Firefox network settings on my local machine and chose SOCKS Host, put in 127.0.0.1 and port 8080, and checked the box for Proxy DNS when using SOCKS v5, but I see that by default, in the box 'No Proxy for' it already has localhost, 127.0.0.1
Wouldn't keeping that there defeat the object? Do I need to remove that?
I used to use that kind of proxy. It worked very well. The "No Proxy for" isn't doing what you think it is doing. You don't need to touch that line. Suppose that you are running a web server on your local system. And you want to go to site http://127.0.0.1/some.file Then firefox will do that locally, without using the proxy. That's probably what you want. I added "192.168.0.0/16" to that "no proxy" list, because I wanted to be able to access the LAN router settings without going through the proxy. (I hope that example illustrates what it is for). And to answer jdd: Running firefox on the remote server, X-forwarding (so you can see locally) is very slow compared to using the socks5 proxy. There lots of X-traffic for painting graphics on the local screen. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/04/18 02:53, Neil Rickert wrote:
I used to use that kind of proxy. It worked very well.
The "No Proxy for" isn't doing what you think it is doing. You don't need to touch that line.
Suppose that you are running a web server on your local system. And you want to go to site
Then firefox will do that locally, without using the proxy. That's probably what you want. I added "192.168.0.0/16" to that "no proxy" list, because I wanted to be able to access the LAN router settings without going through the proxy. (I hope that example illustrates what it is for).
And to answer jdd: Running firefox on the remote server, X-forwarding (so you can see locally) is very slow compared to using the socks5 proxy. There lots of X-traffic for painting graphics on the local screen.
Okay thanks. I'll only be wanting to do this occasionally so I don't anticipate much in the way of knock-on effects. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
gumb -
jdd＠dodin.org -
Neil Rickert