ntop shouldn't STOP, it should just ignore the down interface. Unless you're getting something odd reported back through libpcap?
ntop doesn't support dynamic interfaces - it sets them up at the beginning and that's it. So if it's not up when ntop starts, tough. I suppose that could be handled - another periodic thread that rechecks the interfaces... not 3.0... -----Burton > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Julien TOUCHE > Sent: Tuesday, December 23, 2003 7:23 AM > To: [EMAIL PROTECTED] > Subject: interface up/down [was Re: [Ntop] Unknown DLT types] > > > Burton M. Strauss III wrote: > > >> > >>note: it may be useful to have an option to ignore interface which are > >>not up (for example vpn tunnel down). > > > > > > Not sure how you tell this - if the OS reports that the > interface exists, > > ntop adds it. And libpcap would see packets on it. Maybe I don't > > understand what you mean - post the ifconfig output (start a > new thread) and > > I'll look at it. > > > if i set the ntop interface to eth0,tun1, but tun1 is down for the > moment (but only a moment), ntop stops (logical). > *maybe* an option so it only gaves a warning and try to sniff it lately > *could* be interesting (mainly for people monitoring vpn tunnel) > > Regards > > Julien > _______________________________________________ > Ntop mailing list > [EMAIL PROTECTED] > http://listgateway.unipi.it/mailman/listinfo/ntop > _______________________________________________ Ntop mailing list [EMAIL PROTECTED] http://listgateway.unipi.it/mailman/listinfo/ntop
