additional thought I always tend toward showing all the functionality , and let the user filter what they need , instead of a limited set because many users wouldn't even know the extra functionality existed
On Thu, Dec 15, 2011 at 3:58 PM, Dan Lose <[email protected]> wrote: > fine by me .. it is just that the new functionality is > way ntop is moving ... see url > > > http://www.ntop.org/nprobe/unveiling-application-visibility-in-ntop-and-nprobe-both-in-netflow-v9-and-ipfix/ > > maybe better to wait until ntop 4.1.2 is stable and incorporated into > package tree > > thanks for looking > > > > > > On Thu, Dec 15, 2011 at 3:38 PM, Daniel Manrique < > [email protected]> wrote: > >> Hi, >> >> I was able to reproduce the behavior you describe. However, it seems to >> me that this is "by design", and that out of the box ntop is configured >> to show only the protocols listed in /etc/ntop/protocols.list. It's not >> meant to be an exhaustive list of protocols but rather, a "filter" to >> show only those specified there. >> >> Documentation for the -p option says: >> >> This parameter is used to specify the TCP/UDP protocols that ntop will >> monitor. The format is <label>=<protocol list> [, >> <label>=<protocol >> list>], where label is used to symbolically identify the >> <protocol >> list>. The format of <protocol list> is <protocol>[|<protocol>], >> where >> <protocol> is either a valid protocol specified inside the >> /etc/ser‐ >> vices file or a numeric port range (e.g. 80, or 6000-6500). >> >> A simple example is >> --protocols="HTTP=http|www|https|3128,FTP=ftp|ftp- >> data", which reduces the protocols displayed on the "IP" pages >> to >> three. >> >> If you need ntop to monitor *all* protocols, you need to do so >> explicitly by removing the -p parameter from the startup file, as you >> have described. However the packager may have considered that this was >> too much for most people and thus chose to add a limited list of >> protocols as a starting point. >> >> Since this seems to be "by design", I'd be inclined to mark this bug as >> Invalid. Do let me know if this seems incorrect. I won't touch anything >> until I hear your opinion on this matter. >> >> Thanks! >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/904786 >> >> Title: >> service startup script for ntop incorrect >> >> Status in “ntop” package in Ubuntu: >> Incomplete >> >> Bug description: >> for the 4.1 version of ntop in precise 12.04 >> >> if you comment out the -p /etc/ntop/protocol.list >> ntop will generate the columns dynamically for the menu option >> IP -> Summary -> Traffic as traffic is seen >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/ntop/+bug/904786/+subscriptions >> > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/904786 Title: service startup script for ntop incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntop/+bug/904786/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
