squid-deb-proxy announces wrong port if http_port includes an IP address

[Roland Sommer]

If you want to bind an instance of squid-deb-proxy to a specific IP, setting something like

http_port 10.1.1.50:8000

in the config file, the announced avahi port is set to "10.1.1.50:8000" in /etc/avahi/services/squid-deb-proxy.service instead of "8000" leading to an error during execution of apt-avahi-discover.

error: uncaptured python exception, closing channel <AptAvahiClient> ('10.1.1.50', 10): 9223372036854775807 (<class 'socket.error'>:[Errno 111] Connection refused [/usr/lib/python2.7/asyncore.py|read|83] [/usr/lib/python2.7/asyncore.py|handle_read_event|446] [/usr/lib/python2.7/asyncore.py|handle_connect_event|454])

The port announced via avahi is 10 where no service is listening.

As a workaround i changed the port extraction in /usr/share/squid-deb-proxy/init-common.sh to handle http_port settings including an IP address:

PORT=$(grep http_port /etc/squid-deb-proxy/squid-deb-proxy.conf|cut -d' ' -f2|cut -d':' -f1 --complement)

[Christian Ehrhardt  (paelzer)]

Hi Roland,
Thank you for taking the time to report this bug and helping to make Ubuntu better.
But first of all I must beg your pardon as I don't see why no one came by here yet.
I currently clean up older bugs without actvitity.

Your case is quite clear, yet for the solution I have to ask you a favor.

This bug is present in Debian too, and Ubuntu currently doesn't make any changes over the Debian package. So this bug would be best fixed directly in Debian, and then Ubuntu will pick up the fix automatically.

Would you mind filing a bug with Debian please and mention the created bug here then?