perfectly worked i put the WAN IP /24 worked like a charm. I actually never saw that option  :o

Thank KOM

the last interface that i have, use pppoe to connect with adsl to internet.

my subnet mask that set on that interface is 255.255.255.255 but when i trace change route in squid inc, i found that ifaces variables are these:

Array (     [0] => Array         (             [0] => 192.168.110.5             [1] => 255.255.255.0         )     [1] => Array         (             [0] => 127.0.0.1             [1] => 255.0.0.0         )     [2] => Array         (             [0] => x.x.x.x             [1] => 0.133.150.130         ) )

and this is the result of localnet in squid.conf

acl localnet src 192.168.110.0/24 127.0.0.0/8 0.1.16.128/0.0029437763168723

Either post the errors or click below:

I'm your magic ball, click me! ↓↓↓

That's more matter of personal choice but I like to see, directly in this interface, ports handled by FW rules.

This said, "it's not working" is not very helpful.
Did you check, e.g. from your workstation, that you can reach target server. This means to be able to resolve name (I suppose pfSense is your DNS) then to access it, f.i. using telnet.

In case of error, you should be able to tack it directly using pfSense, looking at firewall log in status/system logs/firewall tab.

This will tell you if this is blocked at FW level.

Should work fine on Windows, Mac and Linux clients.  Only mobile seems to still be an issue.

clean install because im on 2.2.2 works fine. Also make sure you white list the proxy on squid see picture. Also make sure squid is running. When doing a clean  install first get squid3 configure it, then install squidGuard.

Clipboarder.2015.05.09.png
Clipboarder.2015.05.09.png_thumb

Here you go

renato.PNG
renato.PNG_thumb

I have manage to fix my problem by clearing Squid Cache and Firefox Cache.
After I have done that the Whitelist worked as expected.
So, it was a noob error.  ;)    ::)

Very simple. You don't. And the "beta" does not mean what you think it means.

https://forum.pfsense.org/index.php?topic=93188.0

The ESF guys only compile & maintain a build of squid for pfSense.  If you want new features, go to squid-cache.org and get involved with the people that actually create squid.

i dont think it matters your using ipsec..
When using transparent-client-ip feature ALL reply traffic from the webserver:port is redirected to the pfsense system ip-stack for haproxy to pick up..
This also happens when accessing a server on opt1 from the lan-network..

It is a limitation of the ipfw & pf firewall combination required to make transparent-client-ip work..

Workaround might be to portforward incoming requests over ipsec or other to haproxy.

Its a known issue, also in the warning/explanation near the transparent-client-ip setting, however to get it solved a patch to pf is needed.. https://redmine.pfsense.org/issues/3943 . Not sure if/when that will get applied..

Tried localhost isntead of 127.0.0.1  and it worked.  ::) ::) ::) ::)

Not yet.
When a new squidguard version is released the package version will be incremented and you will see that System > Packages.

Steve

thanks sir its work :D

Thanks jimp, implemented the fix successfully on two machines.

o gotcha gotcha didn't see that anyway i just reinstalled it unfortunately it need to edit the sgerror php to my liking but besides that its doing a great job

Thank again