[clamav-users] update report
Gary R. Schmidt
grschmidt at acm.org
Sun Jul 1 08:22:03 EDT 2018
On 01/07/2018 21:05, Reindl Harald wrote:
> Am 01.07.2018 um 08:17 schrieb Gary R. Schmidt:
>> On 01/07/2018 10:22, Gene Heskett wrote:
>>> I'm still logging this about every other freshclam run:
>>> Sat Jun 30 18:49:53 2018 -> nonblock_connect: connect(): fd=4 errno=101:
>>> Network is unreachable
>>> Sat Jun 30 18:49:53 2018 -> Can't connect to port 80 of host
>>> db.us.clamav.net (IP: 2400:cb00:2048:1::6810:ba8a)
>>> And I've rm'd mirrors.dat several times.
>> Do you have an IPv6 network connection to the outside world?
>> That's what "2400:cb00:2048:1::6810:ba8a" is trying to do.
>> I noticed the same thing was happening with my freshclam, had a look at
>> the configure options, reconfigured with "--disable-ipv6", rebuilt and
> build from source is not an option for most users and trying ipv6 on a
> obvious ipv4-only machine where even the loopback device don#t have a
> ipv6 address is a bug - it's that easy
Do any machines *not* have IPv6 stacks installed these days?
They may not have IPv6 connectivity to the outside world, but all my
Solaris, Linux, and Windows boxes have IPv6 stacks installed by default.
So testing for an IPv6 loopback would still say "go for it."
Now, testing for IPv6 connectivity might turn a temporary failure into a
permanent one, which is not good, it would probably be better for the
IPv6 failure message to say "IPv6 connection failed, trying IPv4."
More information about the clamav-users