On Mon, Jun 29, 2015 at 9:35 PM, Amos Jeffries <squ...@treenet.co.nz> 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 > > 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 days), so I believe something between squid 3.3 and squid 3.5 has > > broken this behavior, or it is a problem with FreeBSD 10.x that I do not > > understand. FWIW squid 3.3.3 on FreeBSD 9.x behaves correctly with the > same > > config. > > FYI: Squid has nothing to do with interface binding. That is 100% > internal to the kernel routing stack. > > All Squid is able to do is set the IP and port for the connection as a > hint to the routing. Whether the hint is taken and used is outside our > control. > Yeah, that is what I thought. I was hoping there was a necessary flag that needed to be set on the socket that is different for FreeBSD versus linux and what not, that perhaps may have changed or been removed sometime recently. I will take try and take it up with the FreeBSD lists. Thank you. > Amos > > _______________________________________________ > squid-users mailing list > squid-users@lists.squid-cache.org > http://lists.squid-cache.org/listinfo/squid-users >
_______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
