Open mo8Zomo0 opened 2 years ago
It runs into "max outstanding probes" and that is set to 1024.
If I remember correctly, it now probes upto 10 further than the last host.
So you're sending about 15 probes 10 times per second, so 150 probes per second. So after 6-7 seconds, you're running into that 1000. Not sure when they expire, but that may be something like 10 seconds.
Try increasing packet/probe.h:#define MAX_PROBES 1024 to say 4096 and see if that solves it for you. That said... I think 1000 should be enough.
I don't know what changed in kernels, or MTR, but I used to be able to do the following: (potentially sudo) mtr 75.75.75.75 i 0.01 dd to show the nice, very fast updating graph of pings to Comcast's DNS server.
It used to run for hours if I let it. Now it dies after 10s or less.
So what changed?
referring to https://github.com/traviscross/mtr/issues/298
@rewolff it would be good to quote what would be reasonable values and also what else might cause this behaviour or what could improve it.
(on Debian 10)
From how I see it it seems to fail quite quick if there are hops which do not respond on the path. As you see here, 500 packages, 0.1 (which I find is not very aggressive at all and which I would expect to work)