-
The IPFIX parser currently only supports the standard scalar fields but not the ones described in [RFC 6313](https://tools.ietf.org/html/rfc6313).
The structured fields should be flattened into mes…
-
**Describe the bug**
The messages, as they arrive at pskreporter have sequence numbers which are 45 apart. This causes problems as the system thinks that there are a lot of missing packets.
**To R…
-
After spending some time digging through the code, I fear resolving this may be a bit of an architectural change, but, better to get it on the board for future I figure.
RFC7011 (and RFC5101) requi…
-
**Description**
custom_primitives.conf
```
name=interfaceName field_type=82 len=vlen semantics=str
name=egressVRFID field_type=235 len=4 semantics=u_int
name=ingre…
-
We found that netflow can report wrong flow if spanning tree protocol is enabled. It looks that
1 - Spanning Tree packets are treated as IPv6 packets(HOPOPT/0) in emitted flows
2 - Sometimes flows f…
-
Ticket request to support IPFIX for ESXi 5.1 and above. Any NetFlow exports sent from ESXi devices on ESXi 5.1+ now only support IPFIX.
I have this implemented myself using this plugin including the …
-
The boolean values in IPFIX do not use 0 as false. See http://tools.ietf.org/html/rfc5101#section-6.1.5
1 means true, 2 means false
-
Hello!
After Wireshark investigation I found you use 32 bit (4 bytes) packets and bytes counter for IPFIX. But in reference standard http://www.iana.org/assignments/ipfix/ipfix.xhtml this counters de…