Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't Fragment IP Option #7

Open
alessandromaggio opened this issue Sep 8, 2018 · 3 comments
Open

Don't Fragment IP Option #7

alessandromaggio opened this issue Sep 8, 2018 · 3 comments
Labels
bug Something isn't working

Comments

@alessandromaggio
Copy link
Owner

It looks like the DF option is not being set (tested on Windows, verifies with Wireshark). Currently, the option set is option 10, and it is set to 1.
@alessandromaggio alessandromaggio added the bug Something isn't working label Sep 8, 2018
@alessandromaggio
Copy link
Owner Author

It seems like Socket.DONT_FRAGMENT is not valued correctly. The "don't fragment" option is assumed to be 10 without proper documentation. From a deeper analysis, it seems MS Windows doesn't have this capability on IPv4, just on IPv6.

@malbers15
Copy link
Contributor

malbers15 commented Aug 27, 2020 •
edited
Loading

Issue has been fixed for Linux users of pythonping:
85d751e

@fdauti
Copy link

fdauti commented Feb 25, 2022

when running, ping('192.168.255.11',size=1700, df=True) in linux system, I see with Wireshark that the packets get fragmented, and More fragments bit is set (1). Shouldn't "Don't fragment" flag be 1, when enabling df option?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@alessandromaggio @fdauti @malbers15