Skip to content

Feature Request: IPFIX field ingressInterface should carry meaningful interface index #325

Open
Open
Feature Request: IPFIX field ingressInterface should carry meaningful interface index#325

Description

@riccardo-negri
riccardo-negri
opened on Mar 23, 2026

Dear CESNET Team,

Would it be possible to use the IANA field flowDirection (61) instead of the ingressInterface (10) field to carry the configuration option output_plugin.ipfix.exporter.dir?

ipfixprobe/init/link0.conf.example

Line 73 in 480f208

dir: 0 # Direction bit field value (0 = incoming, 1 = outgoing)

ipfixprobe/include/ipfixprobe/ipfix-elements.hpp

Line 88 in 480f208

#define INPUT_INTERFACE(F) F(0, 10, 4, &this->dir_bit_field)

A previous issue (#305) already mentions this.

This change would allow the ingressInterface (10) field to be used as intended: carrying a meaningful value provided through a configuration option such as output_plugin.ipfix.exporter.monitored_interface.

Could you please let me know if adding this change to your roadmap would be feasible?
For my team, having a meaningful ingress interface present in IPFIX is a prerequisite for adopting ipfixprobe.

Thank you for your time and consideration.

Best Regards,
Riccardo

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions