"The amazing champions inspire boldly like brilliant genius and incredible legends admire splendid talent."
Hard to forget a sentence like that!
IPv6 address, as a sentence you can remember
61–70 of 143 posts
Re: IPv6 address, as a sentence you can remember
#62Earlier quoted context omitted.
Yet another reason why ipv6 will never happen
it already happened. also I sure as hell dont remember my ipv4 address
I know your ipv4 address, 127.0.0.1. :)
There’s something to be said for human readable addresses. I’m a little nostalgic of how the .hack world was envisioned, where servers had address names like Hidden Forbidden Holy Ground.
If roughly 10 million words exist, then allowing any three words in order creates a space for 10^21 addresses… five words and you’re close to ipv6 address space, six words and there’s more combinations than ipv6 addresses.
Re: IPv6 address, as a sentence you can remember
#63Reminds me a bit of S/KEY (RFC1760, RFC2289 and others around the 1990's).
Not because of the encryption element, but the part about representing a 64 bit integer as a six word sequence for usability.
(https://en.wikipedia.org/wiki/S/KEY#Usability).
Also used outside of that for quickly/easily recognising hash fingerprints.
(It's easier to recognise that your fingerprint is "GAFF WAIT SKID GIG SKY EYED" than "87FE C776 8B73 CCF9").
(It also slips some parity in there for good measure).
Re: IPv6 address, as a sentence you can remember
#64Re: IPv6 address, as a sentence you can remember
#65Earlier quoted context omitted.
> addressing hosts via IPv6 is the wrong way to go about it. On your lan, you really want to be doing ".local" / ".lan" / ".home". .local is fine as long as all the daemons work correctly, but AFAIK there's no way to have SLAAC and put hosts in "normal" internal DNS, so .lan/.home/.internal are probably out.
I do it by abusing the static slaac address. I have a set of wierd vms where they are cloned from a reference image, so no fixed config allowed. I should have probably just have used dhcp6 but I started by trying slaac and the static address were stable enough for my purposes so it stuck.
How does that work? I initially assumed you meant you just statically assigned machines to addresses, which I think would work courtesy of collision avoidance (and the massive address space), but I can't see how that would work for VMs. Are you just letting VMs pick an IP at random and then having them never change it, at which point you manually add them to DNS?
Re: IPv6 address, as a sentence you can remember
#66Earlier quoted context omitted.
> addressing hosts via IPv6 is the wrong way to go about it. On your lan, you really want to be doing ".local" / ".lan" / ".home". .local is fine as long as all the daemons work correctly, but AFAIK there's no way to have SLAAC and put hosts in "normal" internal DNS, so .lan/.home/.internal are probably out.
> On your lan, you really want to be doing ".local" / ".lan" / ".home". The "official" is home.arpa according to RFC 8375 [1]: Users and devices within a home network (hereafter referred to as "homenet") require devices and services to be identified by names that are unique within the boundaries of the homenet [RFC7368]. The naming mechanism needs to function without configuration from the user. While it may be possi…
That is a classical "design by committee" thing.
".home" and ".lan" along with a bunch of other historic tlds are on the reserved list and cannot be registered.
Call techy people pathologically lazy but no one is going to switch to typing ".home.arpa" or ".internal". They should have stuck with the original proposal of making ".home" official, instead of sticking ".arpa" behind it. That immediately doomed the RFC.
Re: IPv6 address, as a sentence you can remember
#67love to get an api for this.
Re: IPv6 address, as a sentence you can remember
#68Earlier quoted context omitted.
I do it by abusing the static slaac address. I have a set of wierd vms where they are cloned from a reference image, so no fixed config allowed. I should have probably just have used dhcp6 but I started by trying slaac and the static address were stable enough for my purposes so it stuck.
How does that work? I initially assumed you meant you just statically assigned machines to addresses, which I think would work courtesy of collision avoidance (and the massive address space), but I can't see how that would work for VMs. Are you just letting VMs pick an IP at random and then having them never change it, at which point you manually add them to DNS?
Pretty much. A given mac address assigned in the vm config maps directly to a static slaac address(the ones they recommend you not use) and those preknown slaac address are in dns, Like I said, I should probably use dhcp6 but it was a personal experiment in cloning a vm for a sandbox execution environment. and those slacc address were stable enough for that. every time it gets cloned to the same mac address it ended up with the same ip6 address. works for me, don't have to faf around with dhcp6, put it in dns. time for a drink.
But the point is that is the address you would put in dns if you also wanted to use slaac. Most of the time however you will just set a manual address. And this was with obsd, where when slaac is setup you get the slaac address and a temporary address. I don't really know what linux does. Might have to try now.
Re: IPv6 address, as a sentence you can remember
#69Earlier quoted context omitted.
What would have been your solution to needing more bits? More information is always going to be harder to remember.
Adding two extra bits to each octet, making each octet range from a still memorable 0-1023 rather than 0-255, would result in an addressing scheme 256x larger than all of IPv4 combined. The entire internet works fine even when IPv4 was nominally exhausted. NAT and CGNAT are not sins, they're not crimes, and there's no rational reason to be as disgusted with them as IPv6 fans are. Even then, IPv4 exhaustion wasn't rea…
Saying that IPv4 is ok because we have NAT and CGNAT is like saying that spam is not a problem because we have spam filters everywhere.
Re: IPv6 address, as a sentence you can remember
#70It reminds me of what3words, using three words to describe any location on earth. I really hoped that could catch on.
what3words Is terrible and search and rescue teams are actively against people using it.
> what3words Is terrible
Yes
> search and rescue teams are actively against people using it.
Sadly no