On Tue, Oct 12, 2021 at 12:52:45PM +1100, Darren Tucker wrote: > On Mon, 11 Oct 2021 at 19:41, Chris Green <cl@xxxxxxxx> wrote: > > On Mon, Oct 11, 2021 at 07:13:37PM +1100, Darren Tucker wrote: > > > On Mon, 11 Oct 2021 at 18:54, Chris Green <cl@xxxxxxxx> wrote: > > > > I used to use the following ssh command to set up a socks5 proxy to > > > > use with Firefox:- > > > > > > > > ssh -fC2qTnN -D 8080 chris@xxxxxxxxxxxxxxxxxxxx > > > > > > 8080 is more often used for http proxies whereas 1080 is the > > > registered port for SOCKS. Which are you using? > > > > > Well the command above is exactly what I have in my script for doing > > this, so I was using 8080. Firefox allows you to specify what port to > > use so I just set 8080 there too. I can certainly try 1080 instead. > > I meant which *proxy protocol* are you using? Firefox supports two: > HTTP (commonly port 3128 or 8080, with GET and CONNECT variants for > HTTP and HTTPS respectively) and SOCKS (commonly port 1080). ssh -D > offers only SOCKS. > > Firefox has multiple places to configure proxies: several for HTTP > proxies (http, https, and ftp) plus one for SOCKS. If you point a > HTTP-style proxy setting at a SOCKS proxy server like ssh -D then it's > not going to work. You should only have the SOCKS proxy setting > populated. > Which is *exactly* what my problem was, I had all three (HTTP, HTTPS and SOCKS) configured. I'm sure I had it set up this way previously and it worked but maybe I'm remembering wrong. Anyway it now works exactly as it should! :-) -- Chris Green _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
