Just how much data is transfered during login between Nessus client and server?

[Jason Haar]

Chris Buechler wrote:

>>Am I right that this is a bandwidth issue?  Is it because all the
>>dependancy checks are done on the client instead of the server?
>>
>>    
>>
>
>I run the Nessus client to nessusd across VPN all the time, the
>slowest link being a 1 Mb uplink on the server's side.  The only
>significant data transfer I've noticed is after you first connect to
>the server, it pulls all the plugin info, which is a bit over 2 MB. 
>Even at 256 Kb that's only about a minute.  Other than that initial
>plugin load, everything else operates the same as it does over LAN.
>
>  
>

I just ran it here - nessus client logon generated 5.3Mbytes of traffic 
over a WAN at an average of 0.24Mbs. I also have iperf installed on the 
Nessus server - it rated 1.2Mbs to the same workstation with Nessus 
client... That's 5 times faster...

It seems nessusd is the bottleneck there - not the network? I don't have 
majorly fast processes (P-III), so I'm sure a bigger CPU would help, but 
I wonder why it takes nessusd so long to push that data out to the client?

Nessus 2.2.0 under RH Linux.

-- 
Cheers

Jason Haar
Information Security Manager, Trimble Navigation Ltd.
Phone: +64 3 9635 377 Fax: +64 3 9635 417
PGP Fingerprint: 7A2E 0407 C9A6 CAF6 2B9F 8422 C063 5EBB FE1D 66D1