Page MenuHomeVyOS Platform

Missing mtr6?
Open, LowPublicBUG

Description

HI All,

On the VyOS 1.4.4 there is no way to force mtr to check over IPv6 using mtr6 command/alias.

vyos@r0-sto.e-utp.net:~$ ping ipv6.google.com
ping: Unknown host: ipv6.google.com

vyos@r0-sto.e-utp.net:~$ ping6 ipv6.google.com
PING ipv6.google.com(nt-in-f101.1e100.net (2a00:1450:4025:807::65)) 56 data bytes
64 bytes from nt-in-f101.1e100.net (2a00:1450:4025:807::65): icmp_seq=1 ttl=109 time=33.0 ms
64 bytes from nt-in-f101.1e100.net (2a00:1450:4025:807::65): icmp_seq=2 ttl=109 time=33.0 ms
64 bytes from nt-in-f101.1e100.net (2a00:1450:4025:807::65): icmp_seq=3 ttl=109 time=33.0 ms
64 bytes from nt-in-f101.1e100.net (2a00:1450:4025:807::65): icmp_seq=4 ttl=109 time=33.0 ms
64 bytes from nt-in-f101.1e100.net (2a00:1450:4025:807::65): icmp_seq=5 ttl=109 time=33.0 ms
64 bytes from nt-in-f101.1e100.net (2a00:1450:4025:807::65): icmp_seq=6 ttl=109 time=33.0 ms
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 32.958/32.976/33.038/0.029 ms

vyos@r0-sto.e-utp.net:~$ traceroute ipv6.google.com
traceroute: Unknown host: ipv6.google.com

vyos@r0-sto.e-utp.net:~$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2a00:1450:4025:802::8a) from 2a0f:5707:ba0e:100:14ab:ba50:9291:6963, port 33434, from port 45919, 30 hops max, 60 bytes packets
 1  2620:107:4000:2210:8000:0:f405:77 (2620:107:4000:2210:8000:0:f405:77)  7.267 ms  1.705 ms  1.739 ms
 2  2620:107:4000:a290::f000:c0f (2620:107:4000:a290::f000:c0f)  0.268 ms  0.210 ms  0.299 ms
 3  2620:107:4000:cfff::f200:7425 (2620:107:4000:cfff::f200:7425)  3.085 ms  3.009 ms  2.525 ms
^C15% completed...

vyos@r0-sto.e-utp.net:~$ mtr ipv6.google.com
mtr: Unknown host: ipv6.google.com

vyos@r0-sto.e-utp.net:~$ mtr6 ipv6.google.com

  Invalid command: [mtr6]

vyos@r0-sto.e-utp.net:~$

But:

vyos@r0-sto.e-utp.net:~$ /usr/bin/mtr ipv6.google.com
vyos@r0-sto.e-utp.net:~$

Really do IPv6.

Thanks,

Details

Version
1.4.4
Is it a breaking change?
Behavior change
Issue type
Bug (incorrect behavior)

Event Timeline

drixter triaged this task as Low priority.