Am 01.02.2018 um 18:23 schrieb Chris:
nc -zv 127.0.0.1 3300-3400 nc: connect to 127.0.0.1 port 3300 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3301 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3302 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3303 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3304 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3305 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3306 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3307 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3308 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3309 (tcp) failed: Connection refused nc: connect to 127.0.0.1 port 3310 (tcp) failed: Connection refused Odd that in all the years I've run ClamAV with the same settings I've not had this problem. Using nc -l 3310 in one terminal and nc 127.0.0.1 3310 I get: nc -l 3310 test this is a test
smells like SELinux preventing the client to connect to a non-default port while it still don't explain teh different results of "nc"
_______________________________________________ clamav-users mailing list [email protected] http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
