Earlier 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…
IPv6 address, as a sentence you can remember
81–90 of 143 posts
Re: IPv6 address, as a sentence you can remember
#82Now, if only those people who designed IPv6 were smarter.. Hex aint that bad, LONG hex addresses are pain to use.
Now, lets say you have LAN like this [::1:0:0/56]. So, ::1:0:24 is easy to remember right? Managable? right?.. Also, bonus for :: shortening is, you immediatly know what are you dealing with, ::1 is loopback, ::1:1 is LL, ::1:0:1 is LAN.. everything else is Internet.
The truth is, IPv6 is really 64bit, the other 64bit part is just randomish node address...
Re: IPv6 address, as a sentence you can remember
#83Earlier quoted context omitted.
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 com…
Re: IPv6 address, as a sentence you can remember
#84Earlier quoted context omitted.
it already happened. also I sure as hell dont remember my ipv4 address
I don't remember my ipv4 addresses either, but I recognize them as mine when I see them. I've never recognized an IPv6 address or prefix used in my networks.
Re: IPv6 address, as a sentence you can remember
#85They should charge a small annual fee and let people reserve a custom word for a given IP. You could even have a small utility on your computer that automatically queries given names to "resolve" to IPs.
Re: IPv6 address, as a sentence you can remember
#86Earlier quoted context omitted.
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 https://media.neas.nhs.uk/news/3-words-can-save-lives
Re: IPv6 address, as a sentence you can remember
#87Earlier quoted context omitted.
DNS, Avahi are super usefuler.
Good luck when you're trying to troubleshoot and DNS not working is one of the symptoms. 8.8.8.8 and 4.2.2.x are easy to remember.
If it breaks, so much that you cannot do a dig, you need to re think your network.
Re: IPv6 address, as a sentence you can remember
#88Earlier quoted context omitted.
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 com…
Even easier.
Re: IPv6 address, as a sentence you can remember
#89Earlier 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…
Highly disagree. Middleboxes are a huge problem on global scale and have frozen any innovation below application layer. TCP and UDP even that they are on software not hardware layer cannot be updated or changed, see MPTCP efforts or QUIC giving up and building on top of UDP.
If this is so much privacy problem, IPv6 is there for many years reaching 50%+ deployments in some countries, I bet there should be concrete examples of such breaches and papers written.
> Reaching your own stuff is already a solved problem, too. Tailscale/Headscale
No address to receive communication - no problem install an app that would proxy it through someone who has the address. Tailscale/Headscale is great, using it daily, but they are not solution to the huge already build global network created to connect devices not connecting devices because lack of digits. Global is key here.
Re: IPv6 address, as a sentence you can remember
#90http://borg.uu3.net/~borg/?ipv6 Now, if only those people who designed IPv6 were smarter.. Hex aint that bad, LONG hex addresses are pain to use. Now, lets say you have LAN like this [::1:0:0/56]. So, ::1:0:24 is easy to remember right? Managable? right?.. Also, bonus for :: shortening is, you immediatly know what are you dealing with, ::1 is loopback, ::1:1 is LL, ::1:0:1 is LAN.. everything else is Internet. The tr…
So anyway it gives 128bits in total, 64 for network and 64 for node.
But I wish there was a better way to write just the local node part and global part being taken automatically.