Update:
We have been using a small code patch to add the IP_BIND_ADDRESS_NO_PORT sockopt prior to the bind system call on outbound connections from squid. This has allowed us to significantly scale concurrent sessions, with the entire ip_local_port_range available to each unique destination IP:PORT. Without the code patch, outbound connections to all destinations max out at the ephemeral port range size.
What is the process to have this code patch upstreamed for future squid versions?
On 20/05/22 19:44, Praveen Ponakanti wrote:
> Hi Alex,
>
> Thanks for going through several steps to help mitigate src port
> exhaustion. We are looking to achieve 400-500% more
> concurrent connections if we could :) as there is a significant buffer
> on the available CPU.
Then you require at least 4, maybe 5, IP addresses to handle that many
concurrent connections with Squid.
We would like to investigate going beyond the ephemeral port range for some specific destination IP:PORT addresses. For that it appears squid does not round-robin requests if we use multiple tcp_outgoing_addresses. We could use ACL’s to pick a different outbound IP based on the clients source IP, however that is not very ideal in our environment as our clients aren’t always equally split by subnet. However, if we could split by the client’s source port that might help achieve this. For example something like:
acl pool1 clientport 0-32768
acl pool2 clientport 32769-65536
tcp_outgoing_address 10.1.0.1 pool1
tcp_outgoing_address 10.1.0.2 pool2
Squid's ACLs currently do not allow filtering by the client's source port. We could look into a separate patch to add this functionality to squid’s ACL code if that makes sense. Or is there a better way to achieve this?
Thanks
Praveen
> The option to use multiple tcp_outoing_addresses appears to be promising
> along with some tweaks to the TCP timeouts. I guess we could use ACLs to
> pick a different outbound IP based on the requesting client's prefix. We
> had not considered that option as the ephemeral ports were no longer
> available to other applications when squid uses most of them with a
> single outbound IP configured. We are also looking to modify the code to
> use the IP_BIND_ADDRESS_NO_PORT sockopt as that could help delay port
> assignment with the bind() call on the outbound TCP sessions (to
> hopefully allow access to the 4-tuple on the socket).
Patches welcome.
However, please be aware that use of the 4-tuple is often no different
from the 3-tuple since the dst-port is typically identical for all
outgoing traffic to a given dst-IP.
Cheers
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
