I've sent you a template of some lp-gw rules. Hopefully that will do the
trick for you.
Let me know how things go.
Gauntlet Firewall Technical Support
NOTE: If I had any opinions they wouldn't be that of my employer.
On Sat, 26 Jul 1997, Mark A. Crother wrote:
> I am running Gauntlet 3.2 on BSD/OS 2.0.1. I cannot get the ! @
> to work. My netperm-table for lp-gw looks like..
> # lp-gw rules:
> # -----------
> #lp-gw: permit-destination <inside-printer-host>
> lp-gw: permit-hosts 126.96.36.199 -policy untrusted
> lp-gw: permit-destination 188.8.131.52
> lp-gw: deny-destination *
> #lp-gw: client <outside> -printer <outside-queue-name>
> lp-gw: client 184.108.40.206 -printer lp
> #lp-gw: printer <outside-queue-name> -host <inside-host> -printer <inside-queue>
> lp-gw: printer sp1 -host 220.127.116.11 -printer lp
> policy-untrusted: permit-proxy lp-gw
> where 18.104.22.168 is the client host on a untrusted perimeter. Its
> print queue is sp1 defined as
> The error messages are...
> Jul 26 16:44:25 stop lp-gw: deny host=mentor.ssd.bna.boeing.com/22.214.171.124 use of proxy by policy ''
> Jul 26 16:44:25 stop lp-gw: error or denial connecting client host=mentor.ssd.bna.boeing.com/126.96.36.199, reset client lp daemon
> Any help at all would be GREATLY appreciated....
> Mark Crother crotherm @
> Boeing North American (BNA)
> Space Systems Division (SSD) All opinions are mine.