Your message dated Sat, 11 Aug 2018 16:38:49 -0300
with message-id
<CA+QPbz0VGqzy04k6+M6Rwtv12uRpkShLhZ=cz5sbzhdokkg...@mail.gmail.com>
and subject line PEBCAK - Firewall issue
has caused the Debian Bug report #905926,
regarding squid-deb-proxy-client: ENETUNRECH on system with IPV6 and IPv4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
905926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid-deb-proxy-client
Version: 0.8.14
Severity: normal
Hi! While running apt update I see:
Traceback (most recent call last):
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 126, in
<module>
address = get_proxy_host_port_from_avahi()
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 109, in
get_proxy_host_port_from_avahi
hosts.append(AptAvahiClient(addr))
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 44, in
__init__
self.connect( (addr[0], addr[1], 0, 0) )
File "/usr/lib/python2.7/asyncore.py", line 356, in connect
raise socket.error(err, errorcode[err])
socket.error: [Errno 101] ENETUNREACH
Lots of times. I can't see the issue when the same machine is connected to a
pure IPv4 network.
This is the same as running
/usr/share/squid-deb-proxy-client/apt-avahi-discover by hand.
More info:
$ ip -c addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group
default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.7.8/24 brd 192.168.7.255 scope global dynamic noprefixroute
enp9s0
valid_lft 40810sec preferred_lft 40810sec
inet6 fe80::abc6:fe30:8407:8032/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp12s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 00:22:69:21:7c:21 brd ff:ff:ff:ff:ff:ff
7: enp9s0.900@enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.3.7/24 brd 192.168.3.255 scope global noprefixroute enp9s0.900
valid_lft forever preferred_lft forever
inet6 fe80::1669:b8f6:57fc:2e9f/64 scope link noprefixroute
valid_lft forever preferred_lft forever
8: enp9s0.901@enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.4.7/24 brd 192.168.4.255 scope global noprefixroute enp9s0.901
valid_lft forever preferred_lft forever
9: enp9s0.1@enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
state UP group default qlen 1000
link/ether 00:22:19:fe:4d:5d brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 brd 192.168.2.255 scope global noprefixroute enp9s0.1
valid_lft forever preferred_lft forever
I do not think the VLANs are to be blamed. I hope.
Of course I'll be happy to help debugging this.
Kinds regards, Lisandro.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.17.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8),
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages squid-deb-proxy-client depends on:
ii apt 1.6.3
ii avahi-utils 0.7-4
ii python 2.7.15-3
squid-deb-proxy-client recommends no packages.
squid-deb-proxy-client suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I have just thought on this and clearly is the issue behind my problems, so
not a bug in the package.
My most sincere apologies for the noise.
--
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
--- End Message ---
