Re: [squid-users] Re: /dev/pf permission for squid 3.2.0.6 on openbsd 4.8

2011-04-19 Thread Indunil Jayasooriya
> > 3.2 will not mark the traffic and do any of the special transparent traffic > handling unless one of the NAT lookups functions returns true. Just relying > on the default getsockname() is not sufficient to mark the traffic for > special handling. > > Fortunately the "ipfw" NAT lookup does what

Re: [squid-users] Re: /dev/pf permission for squid 3.2.0.6 on openbsd 4.8

2011-04-10 Thread Amos Jeffries
On 11/04/11 17:11, Amos Jeffries wrote: On 11/04/11 16:31, Indunil Jayasooriya wrote: Hi reyk, many thanks for the reply. - revert /dev/pf to the old 0600 permissions reverted. Now it is set to default. pls see below. # ls -al /dev/pf crw--- 1 root wheel 73, 0 Apr 1 19:30 /dev/pf

Re: [squid-users] Re: /dev/pf permission for squid 3.2.0.6 on openbsd 4.8

2011-04-10 Thread Amos Jeffries
On 11/04/11 16:31, Indunil Jayasooriya wrote: Hi reyk, many thanks for the reply. - revert /dev/pf to the old 0600 permissions reverted. Now it is set to default. pls see below. # ls -al /dev/pf crw--- 1 root wheel 73, 0 Apr 1 19:30 /dev/pf - recompile squid _without_ --ena

[squid-users] Re: /dev/pf permission for squid 3.2.0.6 on openbsd 4.8

2011-04-10 Thread Indunil Jayasooriya
> updated. Pls see below. > > pass in log on $int_if proto tcp from $lan_net to any port 80 \ >    divert-to 127.0.0.1 port 3129 > > > but, still now luck. any comments ? squid developer in squid mailing list said the below, Aha! so PF provides getsockname() now. That means it will require the

[squid-users] Re: /dev/pf permission for squid 3.2.0.6 on openbsd 4.8

2011-04-10 Thread Indunil Jayasooriya
Hi reyk, many thanks for the reply. > - revert /dev/pf to the old 0600 permissions reverted. Now it is set to default. pls see below. # ls -al /dev/pf crw--- 1 root wheel 73, 0 Apr 1 19:30 /dev/pf > - recompile squid _without_ --enable-pf-transparent (disable it) recompiled wit