Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question regarding interface name #183

Open
pwp333 opened this issue Oct 1, 2021 · 5 comments
Open

Question regarding interface name #183

pwp333 opened this issue Oct 1, 2021 · 5 comments

Comments

@pwp333
Copy link
Contributor

pwp333 commented Oct 1, 2021

Dear aabc,

Here you mentioned we can export interface names. But we don't see it in flows. Could you please advise how to export physical interfacename like eth0 and eth1?
https://sourceforge.net/p/ipt-netflow/bugs-requests-patches/58/?page=1&limit=25#63d9

Thanks in advance.

@aabc
Copy link
Owner

aabc commented Oct 4, 2021

Only system interface names are exported, in netflow v9 and ipfix protocol. You should be able to see them with wireshark.

@pwp333
Copy link
Contributor Author

pwp333 commented Oct 4, 2021

Could you please advise which filed in netflow data has the interface name? Did not see these have value for v9.
252 | ingressPhysicalInterface
253 | egressPhysicalInterface

@aabc
Copy link
Owner

aabc commented Oct 5, 2021

IF_NAME(82) and possible IF_DESC(83).

@vladum
Copy link

vladum commented Oct 15, 2021

Maybe the disconnect here is that if id-to-name mappings are in different records than flows?

I wonder what would it take to have IF_NAME in the flow records instead of just ids. Maybe performance concerns to convert ifindex to name in datapath. Or the fact that names and the interfaces themselves could change in the middle of a flow, so it doesn't really make sense to report on flows.

@vladum
Copy link

vladum commented Oct 15, 2021

Actually, what I proposed makes no sense from the protocol's point of view. Sorry for the noise. IF_NAME is a single Information Element, but the Flow Record needs egress, ingress interfaces, as well as their physical counterparts, and all those are defined as integers.

So I guess the collector needs to support joining the id-to-name mapping with the flows. (Or the Exporting Process uses Enterprise-Specific Information Elements, but that is not ipt_NETFLOW's problem.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants