-
-
Notifications
You must be signed in to change notification settings - Fork 195
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
Collection with sFlow #35
Comments
Hello, You can try enabling extensions. See: https://sourceforge.net/p/nfsen/mailman/message/32171818/ Nick |
Your answer is for nfcapd (netflow) but for me it's sfcapd (sflow). Thanks. |
According to https://sourceforge.net/p/nfdump/mailman/message/32916245/ you should be able to capture such data using "-T all". If not, it seems the above never underwent troubleshooting, and you should provide "a few minutes of packet dump" to the author, who might find an opportunity to fix things. |
Other question, How to contact the development team for nfdump/nfsen ? |
I guess the developer/author, Dr Peter Haag, is watching these comments. Furthermore, you may want to subscribe to the (low-volume) nfdump-discuss mailing list. |
Right - just post your requests here. I am a bit busy right now, so it could take some time. |
Ok thanks for your answer. |
I am afraid, but right now, sfcapd does not support mpls. The reason for that is, that I have no trails to test. If sflow supports certain fields, which are not implemented, pls collect some traffic in a pcap, sent to the collector, and send me this pcap. So I can update the collector to these features. |
Any possibility to share a pcap containing sflow records mpls? Otherwise I close the ticket. |
sflow code has been updated to commit 7322984 of https://github.com/sflow/sflowtool |
In the latest master commit, sfcapd now unwarps correctly the mpls stack and add the labels into nfdump records. |
Hello,
I Would like to know If It was as possible to recover the tag mpls In sFlow flow with sfcapd daemon of nfdump ??
Thank you for your answer.
The text was updated successfully, but these errors were encountered: