Hallo, * Stefano Rivera [Thu, Jan 23 2020, 11:15:59AM]: > Package: apt-cacher-ng > Version: 3.3.1-2 > Severity: normal > > Since upgrading from 3.2-3 to 3.3.1-2, I couldn't do an "apt update" any > more. It would 502 on the InRelease file. > > My backend configuration is: > http://mirror.kardiogramm.net/debian/ > http://deb.debian.org/debian/ > > The first one is my mirror at home, that is only available over IPv6. > On IPv4-only networks, apt-cacher-ng used to just skip over this. Now it > gets stuck on it.
Ok. Mind to share a raw tcpdump running for at least 5 seconds? Maybe also: strace -f -o log.trace -p $(pidof apt-cacher-ng) I tried to simulate with sysctl -w net.ipv6.conf.all.disable_ipv6=1 and sorry, it's not reproducible. The changes in v3.3 were actually supposed to counteract in a similar case, IPv6 being resolvable but v6 connections becoming stuck. Best regards, Eduard.
