You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
output/ipfix: flowDirection value placed in wrong field #305
Hi, I'd like to work on this one if nobody else is. Looking at include/ipfixprobe/ipfix-elements.hpp, INPUT_INTERFACE is defined as F(0, 10, 4, &this->dir_bit_field), so the dir option of the IPFIX exporter ends up in ingressInterface (IE 10) instead of flowDirection (IE 61).
My plan would be to export dir as flowDirection (IE 61, unsigned8) and stop sending ingressInterface with the direction value, together with a test for the generated template/record. Since this overlaps with #325 (meaningful ingressInterface index), @SiskaPavel would you prefer both handled in one PR, or #305 first on its own? Also, should the old behaviour be kept behind an option for backward compatibility with existing collectors?
Activity
MichalJankura commentedon Oct 7, 2026
Hi, I'd like to work on this one if nobody else is. Looking at
include/ipfixprobe/ipfix-elements.hpp,INPUT_INTERFACEis defined asF(0, 10, 4, &this->dir_bit_field), so thediroption of the IPFIX exporter ends up in ingressInterface (IE 10) instead of flowDirection (IE 61).My plan would be to export
diras flowDirection (IE 61, unsigned8) and stop sending ingressInterface with the direction value, together with a test for the generated template/record. Since this overlaps with #325 (meaningful ingressInterface index), @SiskaPavel would you prefer both handled in one PR, or #305 first on its own? Also, should the old behaviour be kept behind an option for backward compatibility with existing collectors?