Technically, it's not FreeBSD w/ ntop, it's ntop (libpcap) w/ FreeBSD. :-( The patch reverts (for FreeBSD only) to using pcap_loop instead of pcap_dispatch. The man page explicitly says pcap_dispatch won't work w/ setnonblocking and it doesn't (for more than a little while, except on some systems, like mine, where pcap_dispatch + setnonblocking works fine).
Google for "pcap_dispatch site:tcpdump.org" - it makes for some interesting reading if you are into pain, esp. http://www.tcpdump.org/lists/workers/2003/05/msg00263.html. Software at this level starts to expose some surprising changes between releases of OSes, where based on the version # you wouldn't expect it (FreeBSD 4.4 v 4.5 v 4.6, as in this http://www.tcpdump.org/lists/workers/2002/09/msg00033.html. Read this stuff and you'll begin to understand why I get really peeved at libpcap. libpcap does a wonderful job of hiding the nitty gritty details of interfacing to the network across platforms except where it doesn't. It's like patting a Panda Bear - don't EVER forget it's really a wild animal w/ 4" long claws. -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of shane mullins Sent: Monday, February 21, 2005 7:48 AM To: [email protected] Subject: Re: [Ntop] ntop unstable on FreeBSD 4.x FreeBSD has issues with ntop. Burton has a patch out to help this. Shane ----- Original Message ----- From: "Matthias Teege" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, February 21, 2005 6:56 AM Subject: [Ntop] ntop unstable on FreeBSD 4.x > Moin, > > I've setup ntop 3.1 on a FreeBSD 4.10 box. I run it with > "-d -L --set-pcap-nonblocking --skip-version-check -i dc0,dc1,dc2" > > Ntop starts an collecting some data but after some minutes I've got > errors loke this. > > Feb 21 12:55:05 bullet ntop[74040]: **ERROR** Reading packets on device 0 (dc0): 'read: No child processes' > Feb 21 12:55:05 bullet ntop[74040]: THREADMGMT: pcapDispatch thread terminated... > Feb 21 12:57:36 bullet ntop[74040]: **ERROR** Reading packets on device 2 (dc2): 'read: No child processes' > Feb 21 12:57:36 bullet ntop[74040]: THREADMGMT: pcapDispatch thread terminated... > Feb 21 13:03:22 bullet ntop[74040]: **ERROR** Reading packets on device 1 (dc1): 'read: No child processes' > Feb 21 13:03:22 bullet ntop[74040]: THREADMGMT: pcapDispatch thread terminated... > > What maybe the problem? > Matthias > > -- > make world not war > > > _______________________________________________ > Ntop mailing list > [email protected] > http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop _______________________________________________ Ntop mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop
