> The Firewall-Howto for Linux has a section on socks; you might
> want to start there.
> http://metalab.unc.edu/linux/HOWTO/Firewall-HOWTO.html
> One thing it points out is that socks only works with TCP (not UDP
> or ICMP) applications, so ping won't work through a socks proxy (If I'm
> mistaken or this information is outdated, my apologies).
> The freefire project tools page also has pointers to socks
> information:
> http://sites.inka.de/sites/lina/freefire-l/index_en.html
> Cheers,
> - Bill
Socks5 works with TCP and UDP. Socks4 supports only TCP. The NEC socks5
server also supports "socks-ified" ping and traceroute. But the supplied
clients really do nothing more than request the proxy to run the local ping
and traceroute utilities ON the proxy host, and return the results to the
clients. Only the NEC socks5 proxy supports this, and the clients are for
UNIX.
There's a patch to the TIS FWTK 2.1 for transparency, so the proxies will
work in conjunction with ipfilter/ipchains to create transparent application
proxies on Linux and *BSD. See http://www.erols.com/avenger for the FWTK
FAQ and links to patches.
_______________________________________________________________
UNIX Team - The difference between theory and practice is often greater in
practice than in theory.
01/04/99 17:53:30
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
