Your previous post showed your clamd instance is bound to the loopback interface
and as such other systems cannot connect. But even if they could what would they
do? You surely don't want to ship whole file systems across your network for
scanning, do you? That would also be required if you wish to scan email
attachments. It can be done (think NFS) but the network traffic may surprise you.
dp
On 7/25/16 1:17 PM, Ravi Maddi wrote:
Hi Dennis,
I am trying to connect to a Clam AV running on a separate linux box...and
if there is some configuration I have to do to connect? Or, Clam AV even
allows that?
The fact that you take `hostname` parameter makes me think it's possible.
But, I am getting connection refused error.
Thank you so much!
Best,
Ravi
On Mon, Jul 25, 2016 at 1:20 PM, Ravi Maddi <ravindra.ma...@gmail.com>
wrote:
Thank you Dennis for your swift response. Yes, I got PONG as the response.
We are looking into firewall settings. Appreciate your swift response.
Best regards,
Ravi
On Mon, Jul 25, 2016 at 12:39 PM, Dennis Peterson <denni...@inetnw.com>
wrote:
Try a simple test of the clamd connection with:
echo "PING" | nc localhost 3310
It should return "PONG". If it does your problem is not related to clamd.
dp
On 7/25/16 7:44 AM, Ravi Maddi wrote:
Hi Al,
I am new to clamav. I am able to install it on RHEL AWS environment and
enabled it to run on port 3310.
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
_______________________________________________
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
