Hello folks, first post to the list. I'm fairly new to nfsen but I'm diving in head first, and here is my first issue:
Keep in mind, I haven't been able to test this against older versions of nfdump yet - here is what I'm seeing when running nfsen 1.3.2 with nfdump 1.6.1 (integrated into OSSIM 2.2, but I don't think that should make a difference) When processing stats (topN) using any of the various options, the data columns in the web interface stats table (parsed from the nfdump output) are becoming misaligned. I believe this is due to whitespace in the percentages included with flows, packets, and bytes (when using the nfdump -s option). The percentages always take up 4 characters inside the enclosed parentheses, directly after the associated data. When the parser runs into whitespace (which it will when the percentages are less than 3 decimal places, e.g.( 2.5) vs. (17.0) ... see below for example) it pushes the data to the next column. Date first seen Duration Proto Src IP Addr Flows(%) Packets(%) Bytes(%) pps bps bpp 2010-03-02 12:24:13.748 4367514.552 any xxx.xxx.xxx.xxx 196072(17.0) 211416( 2.5) 12.4 M( 0.5) 0 22 58 In this output example, the alighment is fine until we hit the Packets column where there is whitespace after the opening parenthesis "( 2.5)". This whitespace causes it to be parsed incorrectly and carry the rest of the percentage over to the next column as if it were Bytes... this continues to happen down the row, and all remaining data gets shoved into the last column. Is anybody else seeing this? I'm thinking it should be an easy fix, but I don't know enough about nfsen to track it down and fix it. I wanted to make sure this was strictly an nfsen/nfdump issue and not related to it being integrated into the OSSIM stuff before I bothered posting a bug on sourceforge. Thanks in advance for your assistance. Christopher ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
