2 ms·

1. Fully working IPv6 network. 2. No restrictive firewall (pings work just fine in unicast contexts) 3. Used "ping ff02::1%enp34s0" exactly as the article sugge

by chungy 2y ago

1. Fully working IPv6 network. 2. No restrictive firewall (pings work just fine in unicast contexts) 3. Used "ping ff02::1%enp34s0" exactly as the article suggests. 4. What year is it? "ping6" hasn't been a thing for well over a decade now that standard ping works with IPv6 just fine. 5. Not even using WiFi. 6. Too vague to respond. That's the context: "ping ff02::1%enp34s0" just doesn't get any responses at all. And yes, I have both global and link local IPv6 addresses on the interface.

bhaney 2y ago
> Fully working IPv6 network Apparently not?
johnklos 2y ago
So your network interface is enp34s0? And the results you get are... "PING ff02::1%enp34s0(ff02::1%enp34s0) 56 data bytes" ...and nothing else at all? > What year is it? "ping6" hasn't been a thing for well over a decade now that standard ping works with IPv6 just fine. Ummm... Perhaps that's true about your specific OS, but there are plenty of other OSes for which this isn't true, like macOS and the BSDs. > Too vague to respond. I was trying to make the point that you were the one being too vague. We can guess at things, but saying "nothing happened" is not the same as saying, "I did this thing, and this is the result I got", where the result isn't described as "nothing" ;)
- chungy 2y ago
  > And the results you get are... > "PING ff02::1%enp34s0(ff02::1%enp34s0) 56 data bytes" > ...and nothing else at all? Correct, at least until I send ^C and get a report of 100% packet loss. > Perhaps that's true about your specific OS, but there are plenty of other OSes for which this isn't true, like macOS and the BSDs. It's true on Linux and FreeBSD anyway, the two OSes I have installed in my home. Granted, FreeBSD does hardlink ping6 to the same binary for ancient script compatibility, but the standard ping works just fine. OpenBSD is the same. The days of IPv6 being a weird experimental protocol requiring separate commands are long over (I can't check Mac OS, don't own any Apple products).

by chungy 2y ago

bhaney 2y ago

> Fully working IPv6 network Apparently not?

johnklos 2y ago

So your network interface is enp34s0? And the results you get are... "PING ff02::1%enp34s0(ff02::1%enp34s0) 56 data bytes" ...and nothing else at all? > What year is it? "ping6" hasn't been a thing for well over a decade now that standard ping works with IPv6 just fine. Ummm... Perhaps that's true about your specific OS, but there are plenty of other OSes for which this isn't true, like macOS and the BSDs. > Too vague to respond. I was trying to make the point that you were the one being too vague. We can guess at things, but saying "nothing happened" is not the same as saying, "I did this thing, and this is the result I got", where the result isn't described as "nothing" ;)

chungy 2y ago
> And the results you get are... > "PING ff02::1%enp34s0(ff02::1%enp34s0) 56 data bytes" > ...and nothing else at all? Correct, at least until I send ^C and get a report of 100% packet loss. > Perhaps that's true about your specific OS, but there are plenty of other OSes for which this isn't true, like macOS and the BSDs. It's true on Linux and FreeBSD anyway, the two OSes I have installed in my home. Granted, FreeBSD does hardlink ping6 to the same binary for ancient script compatibility, but the standard ping works just fine. OpenBSD is the same. The days of IPv6 being a weird experimental protocol requiring separate commands are long over (I can't check Mac OS, don't own any Apple products).