Since we see it processing the -m specification w/o any subsequent error, it's not discarding the supernet of the interface parameter itself, which is what I was concerned about.
You can (and should) check this on the About | Show Configuration page (info.html) in the value of the -m parameter (what's shown is the effective value, meaning the parameter has been processed and the display list created from what that). Otherwise, nothing jumps out at me. If you can capture a short (10-20) packet trace - one that exhibits the problem - using tcpdump and send it plus the contents of /etc/ntop.conf to me off list, I'll try and look it over if I have time. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Barrett, Tony Sent: Monday, March 07, 2005 8:28 AM To: '[email protected]' Subject: [Ntop] RE: Local traffic not correct Burton, below is the output of running NTOP with trace level set to 4 (-t 4). Sorry for the long post, but the log file is pretty big. <snip /> Mar 4 16:07:11 netmon2 ntop[20325]: Processing -m | --local-subnets parameter '193.118.192.0/21' <snip /> -- Visit our website at www.roke.co.uk Roke Manor Research Ltd, Roke Manor, Romsey, Hampshire SO51 0ZN, UK. The information contained in this e-mail and any attachments is proprietary to Roke Manor Research Ltd and must not be passed to any third party without permission. This communication is for information only and shall not create or change any contractual relationship. _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
