ping6 -v fe80::1
I thought I would touch base with my fans.
I am still frustrated at the time and effort it takes to do things here. It is reassuring to at least hear people make noises that they want things to change. However, those same people turn right around and continue to be part of the problem — myself included. To quote Pogo, “We have met the enemy… and he is us.”
I also run into “helpful” people who tell me not to “throw out the baby with the bath water.” I hate cliches, and this one just has to go. In fact, at this point, I believe that everything we do might be better served by throwing out the baby and the bath water and starting over from scratch. I think we would find we have been spending a lot of time with a lot of tubs that turn out to not have a baby in them at all.
8 Comments:
Nice title. Derek Morr would be proud of you!
I hear you brother. If the same effort were to be spent on just getting the work done as is spent on figuring out who and how the work should or shouldn't get done, customers would be better served. Better customer service leads to better relationships with people which in turn leads to better services and more interesting work.
Yes, I would be :)
Btw, what is fe80::1 ? The all-nodes link-local multicast group is ff02::1 :)
localhost
Isn't localhost ::1 ?
$ ifconfig
lo0: flags=8049 UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
Technically I think it's the "link local" loopback address. Near as I can tell, it's one of those things where the plethora of available addresses makes for many ways of addressing the same thing simultaneously.
OK... If the loopback address is ::1, then to determine the link local version of that, we prepend fe80, resulting in fe80::1 as the "link local loopback address."
"A link-local address is formed by combining the well-known link-local prefix FE80::0 [RFC4291] (of appropriate length) with an interface identifier..." — rfc4862
Correct me if I'm wrong.
Yea, that does seem accurate. I'd just never seen it, and I'm not sure I understand the concept of a scoped loopback address.
Interestingly, not all OSes appear to configure fe80::1. OS X does, but Solaris 10 and RHEL 5 don't. Perhaps this should be documented in the wiki.
Post a Comment
<< Home