Re: [squid-users] Access denied on transparent after upgrade 3.1.x to 3.3

Hey Ali,

Two major points for you.
Squid requires one port to be a regular forward proxy with no
transparent or other options.

What is your problem? regular proxy or just intercept?

To make things simpler advance one step at a time please.
- basic squid configuration without intercept.
ALL is not a dst or src but a ALL by all means so just use one line in
the http_access and only one to make it clear:
http_access allow all.

Be ware that this will make your proxy *open* to anyone and it is just a
debugging step which you should change after the test.

How do you intercept you traffic? iptables? routing?bridging?

Please attach the access.log to confirm it's squid problem and not other
problem you are having since it smells something else to me.

Regards,
Eliezer

On 12/19/2012 4:05 PM, Ali Jawad wrote:
> Hi
> I did upgrade from squid 3.1.x to 3.3 "and tried 3.2.5 in between"
> problem is now that i have upgraded transparent proxy always returns
> access denied even if I do set src all to allowed. Please see a sample
> config below
>
> http://pastebin.com/vEWgsPkz
>
> On 3.1.x the transparent proxy did work just fine for http_port, I did
> upgrade due to issue with https_port, but since the upgrade even the
> http_port for transparent always returns denied.
>
> Please advice.
>
> Regards
>

-- 
Eliezer Croitoru
https://www1.ngtech.co.il
sip:ngtech_at_sip2sip.info
IT consulting for Nonprofit organizations
eliezer <at> ngtech.co.il