search for: nessusd

Hi, I have shorewall version 1.4.10g on Redhat 9 Local clients are on eth1 in subnet 192.168.3.0/24. eth0 is for the outside (over xdsl with includes a ppp0 interface). Nessus (nessusd) is installed *on the firewall* and managed trough nessus (the client or frontend) running on one of the internal machines. When I was running a scan against 194.152.181.36 I observed several entries like following in the log of the firewall (its IP is 81.223.219.255): Nov 8 11:24:45 fw kerne...

...ow I will not be checking, except that I also had to remove a bunch of samba-related checks which I really should probably keep. I should note that the server always starts up fine, but running the client results in messages such as: *** The daemon shut down the communication *** nessus: nessusd abruptly shut the communication \ down - the test may be incomplete and then the server is off spinning in some CPU loop, and the client is doing nothing much. This happens before the server has sent any packets to the target host. I could obviously provide more details abou...