Michael C. Toren on Tue, 17 Jun 2003 18:25:58 -0400 |
> MCT recently mentioned that ssh can act as a socks proxy. Cool. So I > execute > > ssh -v -D 9000 hostname Sorry, I haven't checked my PLUG folder in a while :-) The above does indeed look correct. > and configure mozilla to think all protocols in its list are socks4 > proxies on localhost, port 9000. I make a request from mozilla > (verified on local and remote hosts as working) and get a stream of > these lines: > > debug1: Connection to port 9000 forwarding to socks4 port 0 requested. > debug1: fd 8 setting O_NONBLOCK > debug1: channel 2: new [dynamic-tcpip] > debug1: channel 2: zombie > debug1: channel 2: garbage collecting > debug1: channel_free: channel 2: dynamic-tcpip, nchannels 3 > > Mozilla reports that the document contains no data. > > Any suggestions what I might be doing wrong or what to look at? The only thing I can think of is that perhaps Mozilla wasn't properly configured. You mentioned that you told it to use the SOCKS4 proxy on localhost port 9000 for all protocols, but I'm not entirely sure what you mean? In the proxy configuration screen, the only hostname that should be listed is that of the SOCKS proxy; the HTTP, SSL, FTP, and Gopher proxies should all be left blank. Here's a screenshot of what my configuration looks like: <http://michael.toren.net/images/screenshots/mozilla-preferences-socks-proxy.jpg> HTH, -mct _________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce General Discussion -- http://lists.netisland.net/mailman/listinfo/plug
|
|