What is the best way to setup a ClamAV database server?

I have a couple hundred machines which I'm beginning to install ClamWin onto. Obviously, I'd rather they didn't all go out to database.clamav.net everyday to get an update!

As such, I attempted to setup a local linux server for the machines to pull updates from. This is what I did:

* Setup a crontab on the server to download "daily.cvd" and "main.cvd" everyday.
* Edited my apache config such that any requests for "/daily.cvd" and "main.cvd" redirects to their location on the disk.
* Tested this by typing "https://servername/daily.cvd" into my webbrowser on the client, and it does try to download the proper file.
* Put my servername in the Preferences/Internet Updates/Download Site on the client-side configuration.

But when I try to do a database update, it fails, complaining about "cdiff" files. something like this:

WARNING: getpatch: Can't download daily-7565.cdiff from [servername]

However I can't download this from database.clamav.net. Or at least, I'm not sure where I'm supposed to do that. I've read that other people have used squid to do the same thing, but I don't think that that will work for my situation. I've never setup squid before, and my internet traffic doesn't go through this server (which I believe is supposed to be the case for squid?).

Thanks for any help/suggestions

Bill

If this is an obvious/dumb question please feel free to point that out (with a relevant faq/howto/man/etc?). I can't be the only person here who's trying to admin ClamWin on a medium sized network?

Any help/pointers are appreciated.

Bill

Looks like you may be out of luck. According to the PDF posted at https://www.clamav.net/doc/mirrors/ (have a look at page 3 of clamav-mirror-howto-1.pdf), they do not support private mirrors! Below is an excerpt from that doc:



It's a pity really as in Australia all moderately priced ISP packages that are in use by SOHO's include download limits and ClamAV virus updates begin to take a bite of that limit when you have several machines downloading updates!

You might want to try setting up a squid proxy server on a system and have the clients use that proxy server.
This way the first client to access the updates should put the files on the local proxy server, and thus other clients would download the file locally rather than having to go to the internet. You may need to increase the file size in the squid.conf since the definition files are larger than the default limits.

So, not your own server, but should reduce the traffic.