William:
I am 100% in concurrence... a Linux firewall would be easier to use from the
perspective of workstation configuration... no client to install. You set
the Linux box as the gateway in your DHCP params, set up forwarding and
masquerading, and WHAMMO!! your boxes are out on the internet regardless of
their OS (since MS only makes the proxy client for Windows systems). It's a
screening, NAT'ing router essentially. You give up some security I will
admit just using ipfwadm/ipchains because you don't get the app proxies, but
you could then use TIS fwtk or SOCKS (but then you complicate it again, and
that wasn't my original point). It depends on what you want to accomplish,
and Khurram appears to either preferr to use NT, or does not have a choice.
He may have been told he was going to make proxy work, and then again, he
may have installed Linux at work, unbeknownst to management, and is just
looking for a way to get out to the net. ;)
Khurram:
Now, with NT you get the web proxy, Winsock proxy and a socks4 proxy. For
your Linux box to get out, you have to get "socksified" versions of ftp,
telnet, etc. and configure them to use your proxy server. Instead of
reproducing the documentation, I would encourage you to do some research on
your own. Here are a couple URL's:
http://www.socks.nec.com/
http://www.aventail.com/index.phtml/solutions/socks_links.phtml
I am no guru (obviously), but I'm happy to help when I can. :)
Carric Dooley
Good point. Although I've never taken the time to look them up,
my understanding is that there are a number of socks compatible
applications for Linux. Linux can act as the gateway too - but read on.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
