The attached patch changes the label for the sflow.fs.seqno from "Sequence
number:" to "Sample sequence number:". This change helps differentiate this
particular item from the sflow.sequence_number which also uses the label of
"Sequence number:".
svn path=/trunk/; revision=26902
after we've checked whether the total length is less than the header
length, so that we don't believe an obviously bogus total length. (This
doesn't catch all cases of bogus total lengths, but it catches, for
example, a total length of 0.)
svn path=/trunk/; revision=26901
- Implement the beginnings of sflow5 support.
- Get rid if the inconsistencies regarding return values: Always return
the offset.
- Make more elements filterable
- Make the naming of elements more consistent (not finished)
- To see what's missing have a look at the TODO section at the beginning
of the file and search for XXX in the code.
The not so good:
- Only tested with a single sample trace. No extended/expanded data in
that trace.
- This patch hopefully doesn't break sflow4 support, but I didn't have
any traces to test with, so please test.
- The names of many filters have changed to make things more consistent.
svn path=/trunk/; revision=26891
It's not a good idea to refer people in the snmp section to
the name resultion section for mibs configuration and then
not provide any clue that they are there correctly if mib
support wasn't compiled in.
svn path=/trunk/; revision=26889
- Put QualificationDirectiveRes in the tree.
- Use correct tag value for messageWaitingNotificationType (145)
- analogRedirectRecord is OPTIONAL.
svn path=/trunk/; revision=26877
- Added support for the optional "flag" field in the SVR4 NFS file handle
(checked with OpenSolaris, NFSv3 and NFSv4).
When the server file system is UFS, the SVR4 decoding works fine. ZFS still
needs some work.
I'm one of the "5 people or less in the world" (see checkin comment r18530),
who care about the inner structure of NFS file handles. I may even re-enable
the heuristics to determine the file handle type automatically, but the old
NETAPP heuristics was definitely much too weak.
svn path=/trunk/; revision=26871
data; at best, that can be a bit confusing, and, at worst, if the field
isn't long enough, or the offset is wrong, it can cause an exception to
be thrown and the dissection to fail.
svn path=/trunk/; revision=26868
