On 2/10/2012 4:29 a.m., Gerald McNulty wrote:
Hello,

Is it possible to have Squid use a different client port than the one
that the client uses when using PROXY in 3.1.21? As an example:

Client: 20.20.20.20:20001   ->   Server: 30.30.30.30:80

Squid will also bind() to 20.20.20.20:20001. I'd like the option of
bind()ing to 20.20.20.20:17654, or some other ephemeral port.


The reason for wanting to do this is that I regularly get "commBind:
Cannot bind socket FD $fd to $client_ip:$client_port: (48) Address
already in use" errors for sites that have many items on a page, some
of which are large.

Thank you

Squid is meant to zero the port on outgoings so the OS assigns a new one. That TPROXY bug with retained ports was fixed around 3.1.14 I thought.

Amos

Reply via email to