51–60 of 143 posts
Earlier quoted context omitted.
Adoption has been flat under 50% for a year now.
It’s not flat: https://www.google.com/intl/en/ipv6/statistics.html You have to take into account seasonal trends. The summer is always higher, so yes, we’re currently below last summer, but we are above last April 1st, and this summer will be higher than last summer.
Earlier quoted context omitted.
You can set your ULA to something like "fddd:192:168::/48" and then on your vlan you prefix hint, say, "66". Now, any device on that vlan will be addressable by "fddd:192:168:66::$host". For example, your gateway ('router') for that vlan would be "fddd:192:168:66::1". If you want to be really wonky you can script DHCPv6 to statically assign ULA IPv6 leases that match the IPv4, and expire them when the IPv4 lease expi…
> 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.
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 possible for a name to be delegated by an ISP,
homenets must also function in the absence of such a delegation.
This document reserves the name 'home.arpa.' to serve as the default
name for this purpose, with a scope limited to each individual
homenet.
Being essentially impossible to memorize is one of the worst attributes of IPv6. I memorize and manually type IPv4 addresses all the time and it's super useful.
DNS, Avahi are super usefuler.
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 predates those by decades.
ipv6 is for faceless hordes of cellphones, which could just as easily be NAT despite being an ipv6 skeptic, i’ve been thinking to try using ipv6 for our new company network, but make the addresses purely readable
Being essentially impossible to memorize is one of the worst attributes of IPv6. I memorize and manually type IPv4 addresses all the time and it's super useful.
Earlier quoted context omitted.
what3words Is terrible and search and rescue teams are actively against people using it.
Care to elaborate why? I'm just curious since I didn't know (1) there was actually any kind of serious usage, or (2) there was pushback from rescue team...
They are missing feature of some codes that can have variable length for variable precision.
Earlier quoted context omitted.
You can set your ULA to something like "fddd:192:168::/48" and then on your vlan you prefix hint, say, "66". Now, any device on that vlan will be addressable by "fddd:192:168:66::$host". For example, your gateway ('router') for that vlan would be "fddd:192:168:66::1". If you want to be really wonky you can script DHCPv6 to statically assign ULA IPv6 leases that match the IPv4, and expire them when the IPv4 lease expi…
> 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.
Earlier 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…
Being essentially impossible to memorize is one of the worst attributes of IPv6. I memorize and manually type IPv4 addresses all the time and it's super useful.
So then I need to use DNS. At which point it could be IPv6.
I have 56 host entries in my dnsmasq.conf.