[clamav-users] ClamAV mirrors have gotten worse!

Paul Kosinski clamav-users at iment.com
Tue Nov 20 18:02:32 UTC 2018

I think you misunderstand. The 'LocalIPAddress' is the *outgoing* IP
address: i.e., the address assigned to the NIC. (This used to be
important when we had two Internet connections.)

The 'LocalIPAddress' has nothing to do with the IP address that
freshclam tries to get the cvds etc. *from*. (Otherwise, the OS would
be expected to have a default IP address as the source of ClamAV data?)

The *only* freshclam that is experiencing delays is the one pulling its
updates directly from the ClamAV (Cloudflare) servers. The other
machines on our LAN don't use the DNS TXT mechanism, but rather are
signaled by the "master" (Internet-connected) ClamAV that new cvd files
are now available locally. Then they run freshclam using a 10.x.x.x
mirror address.

To sum up, the "LocalIPAddress" is exactly what it should
be, the address assigned to a NIC. It is *not* where freshclam tries to
get updates from.

On Tue, 20 Nov 2018 03:39:12 +0100
Benny Pedersen <me at junc.eu> wrote:

> Paul Kosinski skrev den 2018-11-20 03:25:
> >   # Use aaa.bbb.ccc.ddd as client address for downloading databases.
> >   # Useful for multi-homed systems.
> >   # Default: Use OS'es default outgoing IP address.
> >   LocalIPAddress
> comment that line
> > No matter, are we so unlucky -- only 1 out of 3M -- in having the
> > sync errors reappear? Or are we simply one of far fewer users who
> > log (and actually examine) their entire freshclam output?
> you did not make localmirror correct, whole 10.x.x.x/8 is non routed
> in rfc1918, so not external problem to solve other then make
> freshclam get a localmirror that works, if unsure how, comment that
> localipaddress

More information about the clamav-users mailing list