Thanks for the help that is what I need  :)

I think you can put them in the Integrations section.

@Snailkhan:

am i doing something wrong ?  :-\

please help .. also why is the uname command showing dirty ?

Currently no easy way.. Best is probably to create a backup of the whole pfSense configuration from diagnostics\backup-restore to start with.

Before reverting to a old config uninstall the haproxy-devel package so the new binaries are also uninstalled..

Then if you upgrade the package, and dont make much changes. You should be able to revert to a previous config from before upgrading under diagnostics\backup-restore\history.  But that is only possible 30 changes back depending on how much you change after upgrading that might not be enough..

Otherwise if you do make other changes in firewall-rules or other things, and you want to keep those you might want to take another backup and manually 'merge' the old <haproxy>part into the new backup file, and restore that.. p.s. Restoring a full config will reboot pfSense..(a full restore will also re-install all packages automatically iirc..)

After a config is restored make sure to re-install the 1_5 package to get the 1.5 binaries installed again.

Other option is to just re-install the 1_5 package with the upgraded config, it will mostly still work though backend selections acl-names need to be checked.. And when upgrading again in the future it probably wont upgrade as nicely as it would on a first time.. (it automatically changes combined acl's names and creates matching use_backend actions..)

Now i just hope you will find 1.6 working fine :) , and there wont be any need to go back.</haproxy>

Squid's access.log shows the full URL minus any user data.  If you want to see the user data, add the directive strip_query_terms off to your Squid custom settings.  You can find access.log in /var/squid/logs.

This forum is specifically for issues involving DHCP or DNS.  You are asking about Squid.  The better forum to use for such questions is the Cache/Proxy forum.

Which part of fix your FTP server is unclear?

i have installed dansguardian

Try E2guardian when it comes out https://forum.pfsense.org/index.php?topic=87526.0

yeah looks like that fixed it… will make sure to add to my box of tricks. I have 4 of these machines running and they always worked out of the box. but i do have custom whitelists on all of them.

Thank you :)

Lets call it weird then.

@knothstine:

I'm having the same problem, but with squid 4.3.9 and squidGuard 1.9.15.

kivimart, I'd like to try your solution, but I don't know where to put it.

Squid 4.3.9 it's squid2, try updating to squid3.

Squid Cache (Version 3.3.10)? WTH is this? How did you install this on 2.2.x?

May I suggest you flatten and rebuild that box from scratch? Seriously, upgrading this package from any previous versions (2.7.x, 3.1.x, 3.3.x) and across major pfSense releases is a complete no go. And - ditto for downgrading.

Turn on 'Resolve DNS IPv4 First' this is necessary.

Thanks for the info

I already told you that noone will be patching Squid binaries on pfSense to fix typos.

Finally getting to turning on squid3 antivirus and smacked right into this same problem.

Running on pfSense 2.2.5-DEVELOPMENT (amd64) built on Sun Nov 01, with squid3 0.4.1.1,

The filename to edit is different, it's now /usr/local/pkg/squid_antivirus.inc

But editing to change [::1] to 127.0.0.1 now works, and even though the C-ICAP access log still shows ::1, it still passes the EICAR test.

Much thanks for the workaround.