On 30/09/17 10:56, Troy Telford wrote:
I’m fairly sure that the firewall is configured to pass the ICMPv6
messages from any interface to any interface - Clients inside the
network are definitely seeing “packet too big” messages.
So is there something in Squid which could be causing my path
Run multiple instances of squid, one per IP address? I'm not aware of
some magic config option to do what you want.
Seriously though, using a proxy to control your outgoing IP address is
weird.Use setsockopt(SO_BINDTODEVICE) in your code.
--
Aaron Turner
https://synfin.net/ Twitter:
The program is multithreaded so the process based routing won't work. There
is no simple way to make Squid use the connecting IP for the outgoing IP?
On Fri, Sep 29, 2017 at 6:37 PM, Aaron Turner wrote:
> If you don't need a proxy server for other reasons, there are better
One more update before I restart squid:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
3188 squid 20 0 4821844 4.337g 1.008g R 53.0 30.4 349:31.24 squid
3187 squid 20 0 3539696 3.153g 1.008g R 31.9 22.1 259:15.31 squid
3190 squid 20 0 3198228
If you don't need a proxy server for other reasons, there are better
ways. Example, per-process routing:
http://www.evolware.org/?p=369
Or if you have control over the source code of the software,
setsockopt() will do it for you as well.
--
Aaron Turner
https://synfin.net/ Twitter:
I've been slowly trying to get this fixed for a few years now... I had my
system setup to use Squid + TPROXY using IPv6, and it was working great.
However, a couple of years ago, it simply stopped working, and I’ve been trying
to figure out why ever since.
When I try to use IPv6+TPROXY+Squid,
I have multiple IPs on my Linux system and I need one of my programs to be
able to choose which IP to use. One way to achieve this is to use a proxy
server. But with Squid's default config file, the IP I connect to, is not
the IP used for the outgoing connection.
Is there anything I can do to
On 30/09/17 04:32, chiasa.men wrote:
I have to restart squid after each reboot to get it working. I think that is
because squid starts before systemd has started the network and so the dns
lookups fail:
journalctl says:
"squid.service: Unit cannot be reloaded because it is inactive."
So
On 30/09/17 04:11, Vieri wrote:
Hi,
I gather Squid does not yet support http/2.0?
https://wiki.squid-cache.org/Features/HTTP2
Correct.
Do you think it can make it into Squid 5?
I have been trying for that, but things are going very slowly.
Amos
Hi,
I gather Squid does not yet support http/2.0?
https://wiki.squid-cache.org/Features/HTTP2
Do you think it can make it into Squid 5?
Thanks,
Vieri
___
squid-users mailing list
squid-users@lists.squid-cache.org
Hi Alex,
ok, thanks for the clear answer.
best regards
--
Sent from:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
___
squid-users mailing list
squid-users@lists.squid-cache.org
11 matches
Mail list logo