Date: Sat, 05 Jun 1999 23:47:59 +0200 From: Roelof Osinga <roelof@eboa.com> To: Aubrey Kilian <aubrey@eng.uct.ac.za> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Getting FreeBSD to access a socks5 (wingate) machine Message-ID: <37599B0F.9D24D059@eboa.com> References: <004a01beaf8f$84d6b400$0201a8c0@scully>
next in thread | previous in thread | raw e-mail | index | archive | help
> Aubrey Kilian wrote: > > Hi All, > > I've scanned the archives, and can't seem to find anything... > > This probably also belongs in freebsd-newbies, as this is possibly a trivial > thing to do... > > I have 2 machines, on win98 machine running wingate (192.168.1.1), and a > freebsd machine running 3.2-RELEASE (192.168.1.2). > > Wingate is running succesfully as an http and ftp proxy, yet I can't seem to > get any IRC client to use the wingate machine as a socks5 server... On the > freebsd machine i have win98 dualbootable installed, and i have MIRC > installed, and it works through the wingate machine, specifying 192.168.1.1 > as a socks5 server, so wingate (seems to be) setup correctly... > > I installed the socks5 port, but that just seems to be a socks5 SERVER > component, and doesn't enable my IRC clients to use the wingate machine as a > socks5 server... > > Am I missing something? Does BSD have socks5 support by default? Is this > an IRC client shortcoming? Or should I rather stick to DOS? :) The client programs need to be socks enabled. E.g. you can tell netscape to go through the wingate server. It would probably be more efficient to use the FreeBSD server and NAT or Socks5 instead of the wingate machine. Roelof -- Home is where the (@) http://eboa.com/ is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37599B0F.9D24D059>