Open pekeler opened 8 years ago
For report mode I would hazard a guess that the support for multiple address per hop was implemented, and then "report mode" was not upgraded to support it.
For split mode, the idea is that mtr would eventually be split into several separate processes. One doing the network stuff and the display parts running one at a time as a separate process.
I would expect split mode to simply output the information that it has gathered: "got a response from hop 5 from IP xxxx after YYY ms."
Just noticed that this issue is in the TODO since 2008 https://github.com/traviscross/mtr/blob/faa1bd87e4325b604223aaa8ad5517872ccb7336/TODO#L44-L47
Well... Sounds about right.... :-) When I started being mtr-maintainer, I had the occasional "day" that I could spend on mtr and would implement things myself. Nowadays I'm too busy with other stuff that I can manage merging stuff from others, but I'm not available for "Could you make this extension for me?" kind of work.
Feel free to clone the repository and submit a pull request or a patch. This -r stuff and the other IP addresses isn't that difficult. Could be 1 hour of "getting to know your way around" and 20 minutes of coding, but it depends enormously on your experience level.
I was experimenting with the code and tried to fix this. Patch here : https://github.com/traviscross/mtr/compare/master...atib92:mtr-109
Before :
After :
When running interactively, I may get multiple addresses per hop such as here
Why don't we get this information when running
--report
or in split mode?