Re: [clamav-users] update report

2018-07-05 Thread Micah Snyder
Sorry for the delayed response, all: The issue facing those without IPv6 compatible hardware or networks came to light earlier in the CloudFlare mirror-transition. A ticket that both alerted us to the issue and provided a fix was prvoided in a bug courtesy of Guilherme Benkenstein:

Re: [clamav-users] update report

2018-07-03 Thread Reindl Harald
Am 02.07.2018 um 19:38 schrieb Benny Pedersen: > Gene Heskett skrev den 2018-07-02 19:20: >> On Monday 02 July 2018 13:12:12 Gene Heskett wrote: >> However, a network restart did not get rid of the ipv6 stuff in the >> ifconfig lo report. ?  /etc/network/interfaces is also clean of any >>

Re: [clamav-users] update report

2018-07-03 Thread Reindl Harald
Am 02.07.2018 um 19:20 schrieb Gene Heskett: >> And since that stuff did exist in my /etc/hosts file, I just stuck a # >> in front of all those, just for S of course. Watching log too. But >> its seems like an every other update run, and since I am not a >> paying/supporting customer, I only

Re: [clamav-users] update report

2018-07-02 Thread Joel Esler (jesler)
On Jul 2, 2018, at 1:56 PM, Gene Heskett mailto:ghesk...@shentel.net>> wrote: but even on my setups which have this for years freshclam repetaly produces ipv6 crap-messages which is simpyl wrong If thats the case, and I'll find out by this time tomorrow, then I can't help but agree, its a

Re: [clamav-users] update report

2018-07-02 Thread Gene Heskett
On Monday 02 July 2018 13:23:24 Reindl Harald wrote: > Am 02.07.2018 um 19:20 schrieb Gene Heskett: > >> And since that stuff did exist in my /etc/hosts file, I just stuck > >> a # in front of all those, just for S of course. Watching log > >> too. But its seems like an every other update run,

Re: [clamav-users] update report

2018-07-02 Thread Benny Pedersen
Gene Heskett skrev den 2018-07-02 19:20: On Monday 02 July 2018 13:12:12 Gene Heskett wrote: However, a network restart did not get rid of the ipv6 stuff in the ifconfig lo report. ? /etc/network/interfaces is also clean of any ipv6 stuffs. ? if all else fails check /etc/gai.conf

Re: [clamav-users] update report

2018-07-02 Thread Gene Heskett
On Monday 02 July 2018 13:12:12 Gene Heskett wrote: > On Sunday 01 July 2018 07:05:52 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

Re: [clamav-users] update report

2018-07-02 Thread Gene Heskett
On Sunday 01 July 2018 07:05:52 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:

Re: [clamav-users] update report

2018-07-02 Thread Reindl Harald
Am 01.07.2018 um 14:22 schrieb Gary R. Schmidt: > 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 ->

Re: [clamav-users] update report

2018-07-02 Thread Reindl Harald
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

Re: [clamav-users] update report

2018-07-01 Thread Gene Heskett
On Sunday 01 July 2018 10:20:59 Gary R. Schmidt wrote: > On 01/07/2018 23:00, Gene Heskett wrote: > > On Sunday 01 July 2018 08:22:03 Gary R. Schmidt wrote: > > [SNIP] > > >> Now, testing for IPv6 connectivity might turn a temporary failure > >> into a permanent one, which is not good, > > > >

Re: [clamav-users] update report

2018-07-01 Thread Joel Esler (jesler)
Gentlemen, we’ve descended into a “who is better” contest. I suggest we stop. Sent from my iPhone > On Jul 1, 2018, at 10:43, Gary R. Schmidt wrote: > >> On 02/07/2018 00:35, Reindl Harald wrote: >> >>> Am 01.07.2018 um 16:33 schrieb Gary R. Schmidt: >>> On 01/07/2018 22:37, Reindl

Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt
On 02/07/2018 00:35, Reindl Harald wrote: Am 01.07.2018 um 16:33 schrieb Gary R. Schmidt: On 01/07/2018 22:37, Reindl Harald wrote: [SNIP] do you see any ipv6 address here? the stack is disabled and even in that cases freshclam comes with ipv6 error messages Do you know the difference

Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt
On 01/07/2018 22:37, Reindl Harald wrote: [SNIP] > do you see any ipv6 address here? the stack is disabled and even in that > cases freshclam comes with ipv6 error messages > Do you know the difference between running an IPv6 stack and doing a name lookup for an record?     Cheers,       

Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt
On 01/07/2018 23:00, Gene Heskett wrote: On Sunday 01 July 2018 08:22:03 Gary R. Schmidt wrote: [SNIP] Now, testing for IPv6 connectivity might turn a temporary failure into a permanent one, which is not good, Needs an explanation. Udev is the only thing that will turn a temp failure

Re: [clamav-users] update report

2018-07-01 Thread Gene Heskett
On Sunday 01 July 2018 08:22:03 Gary R. Schmidt wrote: > 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

Re: [clamav-users] update report

2018-07-01 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am So den 1. Jul 2018 um 13:22 schrieb Gary R. Schmidt: > Do any machines *not* have IPv6 stacks installed these days? Yes. If you don't have and/or need IPv6 connectivity, it is probably the safest measurement to switch it off completely (by

Re: [clamav-users] update report

2018-07-01 Thread Gary R. Schmidt
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

Re: [clamav-users] update report

2018-07-01 Thread Gene Heskett
On Sunday 01 July 2018 02:17:41 Gary R. Schmidt wrote: > 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 ->

Re: [clamav-users] update report

2018-07-01 Thread 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:

Re: [clamav-users] update report

2018-06-30 Thread Gene Heskett
On Saturday 30 June 2018 20:30:57 Joel Esler (jesler) wrote: > Interesting. Can you give us a -debug? > Is this something I can put in the crontab, Joel? How? > Sent from my iPhone > > > On Jun 30, 2018, at 20:22, Gene Heskett > > wrote: > > > > I'm still logging this about every other

Re: [clamav-users] update report

2018-06-30 Thread Joel Esler (jesler)
Interesting. Can you give us a -debug? Sent from my iPhone > On Jun 30, 2018, at 20: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

[clamav-users] update report

2018-06-30 Thread Gene Heskett
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