3 ms·

Is your result "nothing" because you 1) have IPv6 turned off, 2) are running a restrictive reverse firewall, 3) didn't pay attention to the fact that you likely

Is your result "nothing" because you 1) have IPv6 turned off, 2) are running a restrictive reverse firewall, 3) didn't pay attention to the fact that you likely have to specify your ethernet interface explicitly, 4) didn't notice that you need to use `ping6` instead of `ping`, 5) have device isolation on your wifi network, 6) any of a number of other things? You seem to be here to complain more than to actually learn, else you'd've said what results you got, and you'd communicate better by not using acronyms without context (TFA: trans fatty acids? Thanks for asking?) Regarding the comment about web browsers being made by stupid people, we're all allowed to have opinions. Most of the common web browsers have tons of stupid design choices, and generalizing that stupid design choices come from stupid people just sounds like a flippant remark, not a denigration of a whole group of people. The people I know who work on web browsers would wholeheartedly agree with the author's comment (I've heard many similar sentiments). The information in this article is useful, and everyone even remotely in IT would benefit by keeping this page bookmarked :)

observationist 2y ago
The context for TFA is this site; it's common knowledge.
Arnavion 2y ago
The Fine/Fucking Article. cf RTFM
bhaney 2y ago
> (TFA: trans fatty acids? Thanks for asking?) "The Fucking Article." Etymologically derived from "RTFM," but now mostly used as a casual abbreviation to refer to the article that a comment thread is about. People who have traumatic childhood memories of soap in their mouths sometimes pretend it stands for "The Fine Article" or "The Featured Article."
- aftbit 2y ago
  Thanks! I have been on HN since 2014 and I still hadn't figured out WTF people were talking about with TFA. I just assumed it was some kind of reference to the article but I didn't realize the F was for fucking.
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).

observationist 2y ago

The context for TFA is this site; it's common knowledge.

Arnavion 2y ago

The Fine/Fucking Article. cf RTFM

bhaney 2y ago

> (TFA: trans fatty acids? Thanks for asking?) "The Fucking Article." Etymologically derived from "RTFM," but now mostly used as a casual abbreviation to refer to the article that a comment thread is about. People who have traumatic childhood memories of soap in their mouths sometimes pretend it stands for "The Fine Article" or "The Featured Article."

aftbit 2y ago
Thanks! I have been on HN since 2014 and I still hadn't figured out WTF people were talking about with TFA. I just assumed it was some kind of reference to the article but I didn't realize the F was for fucking.

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).