[squid-users] Squid binding to unknown ports!

From: Maildrop <maildrop@dont-contact.us>
Date: Wed, 16 Oct 2002 16:30:57 -0500

For some reason Squid is binding to a lot of weird ports, I am trying to
lock it down a bit and was wondering if anyone knew what these where:

USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
nobody squid 81575 5 udp4 *:1667 *:*
nobody squid 81575 7 tcp4 127.0.0.1:4434 127.0.0.1:4433
nobody squid 81575 8 tcp4 127.0.0.1:4436 127.0.0.1:4435
nobody squid 81575 9 tcp4 127.0.0.1:4438 127.0.0.1:4437
nobody squid 81575 10 tcp4 127.0.0.1:4440 127.0.0.1:4439
nobody squid 81575 11 tcp4 127.0.0.1:4442 127.0.0.1:4441
nobody squid 81575 16 tcp4 192.168.17.1:3128 *:*

First what is it binding to all UDP port 1667 all ALL Interfaces, including
the External ones!? What does it need UDP for, this is a single server and
has no cache hosts? Anyone know how to disable all UDP traffic/bindings
from Squid?

The 127.0.0.1 44?? address don't bother me to much... I am assuming these
are used to auth with ncsa_auth program internally?

192.168.17.1:3128 is correct and right, it should be only binding the proxy
to the internal interface.

Any ideas on what/why squid is using udp port 1167 for? Ideas on how to
keep squid from doing any udp traffic at all (this is single server proxy
only, no cache, no cache servers, no ssl, no icp, nothing but proxy please!)
:)

Regards,
Jack
Received on Wed Oct 16 2002 - 15:17:52 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:10:43 MST