Steve Freeman wrote:
Hi,
Thanks to those who replied to my security question. The QUEUE rule was
the culprit, and it shouldnt have been there.
It came from the peerguardian daemon (a privacy filter, ironically!),
and should have only been applied to the OUTPUT,FORWARD tables only, NOT
the INPUT. I have modified the code to remove the INPUT and recompiled.
Solved.
It has really helped to voice this on here, although it was not samba
related. The samba log is now clean. Thanks again,
Mike
glad you found the cause. i was wondering what the queue was for
anyway. :)
--
My Website: http://messinet.com
My Online Gallery:
http://messinet.com/modules.php?name=Web_Links&l_op=visit&lid=3
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
