When no route to host, it is found that when the --report parameter is used, the one-hop source address will be reported, while the curses mode will report (no route to host)
I think there is a problem with --report mode.
I found that (aba24a7f129f846e17c6fe1279a40f1d118281c3) does not handle --report mode.
report mode:
[root@mtr ~]# mtr -r -a 99.99.23.6 dst.ip
Start: 2023-09-22T19:32:34+0800
HOST: mtr Loss% Snt Last Avg Best Wrst StDev
1.|-- 99.99.23.6 10.0% 10 1815. 1896. 646.6 3054. 857.2
curses mode:
[root@mtr ~]# mtr -a 99.99.23.6 dst.ip
My traceroute [v0.95]
mtr (99.99.23.6) -> dst.ip (dst.ip) 2023-09-22T19:32:34+0800
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Snt Last Avg Best Wrst StDev
When no route to host, it is found that when the --report parameter is used, the one-hop source address will be reported, while the curses mode will report (no route to host) I think there is a problem with --report mode. I found that (aba24a7f129f846e17c6fe1279a40f1d118281c3) does not handle --report mode.
report mode: [root@mtr ~]# mtr -r -a 99.99.23.6 dst.ip Start: 2023-09-22T19:32:34+0800 HOST: mtr Loss% Snt Last Avg Best Wrst StDev 1.|-- 99.99.23.6 10.0% 10 1815. 1896. 646.6 3054. 857.2
curses mode: [root@mtr ~]# mtr -a 99.99.23.6 dst.ip My traceroute [v0.95] mtr (99.99.23.6) -> dst.ip (dst.ip) 2023-09-22T19:32:34+0800 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Snt Last Avg Best Wrst StDev