-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fwmtu mis-measures some MTUs. #1490
Labels
Comments
I did some more research on this, and it looks like you have to use ICMP packets to find receive host issues. IP packets only tell you about router config issues. Here is some sample code that uses ICMP and seems to address the problem:
|
NB: The above code was generated with ChatGPT and will have to be clean-roomed to be license-compatible with perfSONAR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@bltierney Noticed that the I2 perfSONAR hosts are showing MTUs of 1500. I checked the interfaces; they were reconfigured incorrectly to 1500 during a recent re-provisioning.
Sometimes he's able to get it to show 9000, which we suspect may be that the
socket.error
exception being caught after the call tosock.send()
may be too simplistic and is returning a MTU value for something that doesn't make it all the way there.Investigate this and make corrections to make it work properly.
The text was updated successfully, but these errors were encountered: