-
Notifications
You must be signed in to change notification settings - Fork 48
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
TTL field and DF flag addition #54
Comments
Hi @fdauti, Thanks for using icmplib! Adding the DF flag should be possible. However, not having enough time to devote to icmplib at the moment, you will have to wait a bit. For the TTL, there have been several requests in the past on this subject but I do not understand the point of retrieving this information (the remote equipment responds with an initial TTL which may vary). Moreover, not having access to the IP header in IPv6, I can only retrieve this information in IPv4. |
Hi, Cheers, |
Good afternoon |
I Opened an almost Duplicate of this for a DF flag - i think an additional option in the ICMPScoket or ICMPRequest would be the right place - would you object if I did a clone/fork and attempted to build a Pull request to add this feature, or would you prefer to keep development entirely in house ? |
Closing in favor of #71. |
Hello and thank you for your development of icmplib.
I'm using it as part of a tool for diagnostic purposes. I wanted to ask if it is possible to include these two parameters as part of future development. First one is a "df" parameter as a feature, so that if set to True, will enable the Don't Fragment flag in the IP header. Second one is a ttl return value, corresponding to the ttl field value in received packet. Or maybe there is something related to the above but I'm missing them.
Thanks again and regards.
The text was updated successfully, but these errors were encountered: