Does Gauntlet 3.1 packet filter in the conventional sense (permit / deny
source / destination)? Or it is purely a application level proxy services
approach?
If I have IP traffic for which there is no proxy for, how can I control
this traffic without writing a custom proxy?
If it does packet-filter, how (well) are the proxy "rules" integrated with
the packet-filtering "rules"?
I checked out the TIS web sight and could not find any specific statments
toward "yes, it packet filters".
--
Steve Engle
DHT, Inc.
sengle @
hti .
net
|
|
