2.2 i386 (upgrade) - appears squid 2.7.9 package is broken

marcelloc

Squid3 pbi on i386 will be updated to fix missing transparent proxy compile option(you can confirm executing squid -v on console / ssh.

On amd64 it's transparent proxy is working fine.

vbentley

Thanks. I appreciate your effort to fix this.

In the old days, I used conditional branching proxy.pac files and I still think that it's a better way than transparent TCP interception. I'm going to have a go setting up wpad with dhcp delivery and see how I get on with that for now.

http://wiki.squid-cache.org/SquidFaq/ConfiguringBrowsers#Fully_Automatic_Configuration

KOM

WPAD Autoconfigure for Squid

cwf_netman

@jesus_seba:

Hello,

I had the same issue this morning. From an existing installation of pfSense 2.1 + Squid, I copied the following files onto my upgraded pfSense 2.2 system:

/lib/libz.so.5
/lib/libcrypto.so.6
/usr/lib/libssl.so.6

Squid works fine now.

Hope this helps.

Any chance of the pfSense dev team getting a 2.2.1 update out soon with these missing files included? A lot of us are still using Squid 2.x with pfSense because it works well and stable on older hardware.

jimp

Those files aren't missing. Those are old versions. pfSense 2.2 uses (for example) libz.so.6, libcrypto.so.7 and libssl.so.7.

If something is looking for the old versions, it must not have been compiled properly.

Maybe the PBI that was installed was still the old 2.1 PBI?

Uninstall all of the squid related packages, check "pbi_info" from the shell and "pbi_delete" any squid packages that still show up, then install it again.

vbentley

I have regressed my main firewall back to 2.1.5 today and edited the config.xml by hand and with diff/patch from known good backups. It's working fine again now.

I am planning to get 'new' hardware next week so that I can build the config from scratch on a 64bit version of 2.2 .

One thing I have learned from this experience is that I need to build my own test scripts for what's important for my installation. I completely forgot to test something that was important to my site during the entire 2.2RC period despite testing a load of other stuff on a 2.2RC machine before release day.

NetVicious

squid 3 on i386 seems not to being recompiled for transparent proxy at the moment isn't it?

And squid2 pbi seems to be wrong too.

Any other solution?

I downgraded until we got a solution for this problem.

Cino

@NetVicious:

squid 3 on i386 seems not to being recompiled for transparent proxy at the moment isn't it?

based on a few other threads, looks like the pbi for i386 came out yesterday.

marcelloc

@Cino:

looks like the pbi for i386 came out yesterday.

Yes, it fixed most compile issues for i386.

Steve Evans

I've just installed 3.4.10_2 pkg 0.2.6 and I'm seeing the following config using "squid -v".

'--disable-ipf-transparent' '--disable-ipfw-transparent' '--enable-pf-transparent'

This is the same as before. :(

Steve

Steve Evans

Is the phi that came out yesterday for squid 2 or 3?

Steve

marcelloc

@Steve:

This is the same as before. :(

The transparent pf is what we need '–enable-pf-transparent' to get transparent proxy working.

Are you still with issues?

@Steve:

Is the phi that came out yesterday for squid 2 or 3?

squid3

Steve Evans

Yes, still not working. My previous investigation of this showed the redirection wasn't working, but then you spotted the compile options.

Confused.

Steve

bellera

https://redmine.pfsense.org/issues/4293

mansi

Perfecto, gracias!!!