On Fri, Apr 15, 2016 at 8:45 AM, Odhiambo Washington
wrote:
> Hello Amos,
>
> All noted.
>
> Lemme consult with some FreeBSD guys on these .
>
As a FreeBSD user, here's my two cents.
You should be using the www/squid port.
If the port doesn't compile with the options you wish, open a problem
r
On Mon, Jun 29, 2015 at 9:35 PM, Amos Jeffries wrote:
> On 30/06/2015 8:54 a.m., Nick Rogers wrote:
> > Hello,
> >
> > I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
> > tcp_outgoing_address correctly rewrites the source address of outgoing
> &g
Hello,
I am experiencing an issue with squid 3.5.5 and FreeBSD 10.1 where
tcp_outgoing_address correctly rewrites the source address of outgoing
packets, but fails to bind the socket to the correct interface. I've been
using this kind of setup/configuration for quite some time (since the squid
2.7
On Wed, Apr 22, 2015 at 10:35 PM, Amos Jeffries
wrote:
> On 23/04/2015 9:14 a.m., Nick Rogers wrote:
> > After upgrading from 3.4.x to 3.5.x, I've noticed a new error message
> with
> > my squid configuration. Apparently squid 3.5 no longer allows setting the
> > t
After upgrading from 3.4.x to 3.5.x, I've noticed a new error message with
my squid configuration. Apparently squid 3.5 no longer allows setting the
two lower-most ECN bits of the ToS byte. I realize that this is to
encourage people to use the modernized definition of ToS being a 6 bit DSCP
field a
Hello,
I thought I would make everyone on this list aware of an issue between
squid 3.4.x (and perhaps 3.5?) and FreeBSD 10.1-RELEASE. There was a
regression in the FreeBSD 10.1-RELEASE kernel's signal handling behavior
that causes squid to coredump and restart itself when receiving the
shutdown s
