-
Notifications
You must be signed in to change notification settings - Fork 3
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
panic #2
Comments
My first guess would be that the data it's being sent is somehow corrupted or doesn't match the IPFIX format. Do you happen to have a pcap of traffic that triggers this?
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
…On Thursday, February 4th, 2021 at 6:40 AM, Laco Skokan ***@***.***> wrote:
I see this in log when using the lib
thread 'ipfix' panicked at 'range end index 297 out of range for slice of length 88', /usr/local/cargo/git/checkouts/rs-ipfix-42c2f7fc459fd94f/0714f22/src/lib.rs:130:38
Is it anything obvious?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, [view it on GitHub](#2), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ABJPVJRU3KK6VNRC2RZXXDTS5KWV7ANCNFSM4XC6FYEA).
|
yes, it was. I was passing in Netflow v9 starting with "0009" or even some other data. It would be wise to check netflow/ipfix version in header and also not to panic if length is invalid in "lib.rs:130" |
I'll go ahead and make that change, it really shouldn't panic on any malformed or unexpected traffic |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see this in log when using the lib
thread 'ipfix' panicked at 'range end index 297 out of range for slice of length 88', /usr/local/cargo/git/checkouts/rs-ipfix-42c2f7fc459fd94f/0714f22/src/lib.rs:130:38
Is it anything obvious?
The text was updated successfully, but these errors were encountered: