-
Notifications
You must be signed in to change notification settings - Fork 5
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: libpnet and net-parser-rs #16
Comments
That being said, if pnet supports what you need, you should probably use it, since it is a more mature library. This is a library we're using internally for the use cases we have, both in terms of receiving and interrogating packets, and have open sourced it to see if others find it useful. Also, if you're running into speed/efficiency with pnet, feel free to keep an eye on this project. Over the next few months there will be even more focus on that with this crate. |
Hi, thank you for your prompt reply. As to your bullet-points:
Having real-world users is something really valuable, I'm also coming at this problem with an eye on my own company's use-cases, we're doing lots of low-level packet stuff as well - and in truth I am looking for a crate to rally around. Libpnet is quite mature and has support for a lot of protocols, but those can easily be added to your crate. Will do. In closing, I spent a few days surveying the landscape and the worst-case scenario is more fragmentation in the space - as a part of the wg-net workgroup I am hoping to find some low-level networking crates that the community can rally around. |
Hi there, this project looks really cool and I'm currently looking for a similar crate, I'm leaning towards adding parsing to libpnet - is there a reason (that I'm missing) why a new crate like this was needed as apposed to using something like libpnet?
The text was updated successfully, but these errors were encountered: