-
Notifications
You must be signed in to change notification settings - Fork 53
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
[Feature Request] ICMP #10
Comments
+1 |
Hi, I am thinking about it. What are the types of ICMP packets that would be most important for you? Greets |
Currently EchoRequest and EchoReply would be sufficient for me. |
Destination Unreachable is the most interesting one for me. |
Came here looking for ICMP as well :) |
Hi, I would like to see ICMP support as well. I can also implement and open a PR if you are willing to accept. |
@JulianSchmid I'm looking for ICMP support as well... and am happy to try to implement it. If I submitted a patch/pull request, would you be willing to accept it (assuming the code wasn't too horrible)? I was thinking of adding ICMP as another type of TransportHeader so it could be easily matched against Tcp/Udp/etc.- thoughts? Please let me know and thanks. |
@robs-zeynet Sounds good, but I cannot guarantee that I will find time right away for a code review & merges. I have a bit of time the next few weeks and after that I will have to find time on the weekends. Which was difficult to find in 2020. But next year will (hopefully) be less stressful. In the following weeks I will try to finally finish up #13 after which I can finally rebase and merge #11 . |
Time Exceeded is useful as well (ICMP notification of reaching the TTL limit). |
Support for reading/writing ICMP would be helpful. There's an opportunity after that for helper methods to generate common ICMP packets, for example fragmentation needed and time exceeded.
The text was updated successfully, but these errors were encountered: