-
Notifications
You must be signed in to change notification settings - Fork 86
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
Current status of support for Cisco High-Speed Logging (HSL) #93
Comments
It appears this duplicate field business also happens for IPFIX from Cisco ASR1k with IE 12235 for PEN 9. |
I am also seeing a similar issue with Netflow from Forcepoint NGFW. Error log and PCAP below.
|
Oops just found this in RFC7011, chapter 8. It's one of the MUST requirements we currently don't implement, see also issue #83.
|
Here is another sample from another Forcepoint NGFW. |
Confirming the observations robcowart made about Forcepoint NGFW, seeing exactly same issue here. As a workaround, using CEF format log forwarding and Logstash CEF input codec with '\n' as delimiter. |
The duplicate from Forcepoint is fixed with this #171 |
I am seeing same errors for HSL on logstash 6.8.4 and elastiflow. |
Hello, do we believe this will be resolved? Cisco is using HSL in their SDWAN firewall logging and using this plugin would be very valuable. |
No as the logstash netflow codec is deprecated. |
@abraxxa the netflow CODEC is not deprecated. The netflow MODULE (which was essentially ElastiFlow 1.0.0 repackaged as a Logstash module) has been deprecated. |
I had a support ticket open for that and Elastic said it won't develop/support the Logstash netflow codec any more and we have to use the Filebeat one. |
Elastic has never really actively developed the Netflow codec. The community always has. BTW, a Logstash module is more than an input and codec. They also include a full pipeline to further process the data and the necessary index templates, and Kibana content. Whether modules offer a significant value or not is a different question, and is about more than just Logstash. I also find most of the Beats modules to be mediocre at best. While the stack itself allows for some compelling solutions to be built on top of it, Elastic isn't really great at doing so IMO. |
I've created a new "cisco-hsl" branch to add support for Cisco HSL.
However, I'm running into a structural issue:
Currently only these flowset_id's are properly decoded:
The text was updated successfully, but these errors were encountered: