Also, your "your site" example is deceptively simple. It works nicely if your /48 happens to be full of 0s, but even assuming you were allocated a huge /32 and you got to choose the extra 16 bytes for memorability, the address is more likely to be something like 2a00:1450:4001:830::/48.
Even this seems overly optimistic. For example, www.google.com is not a /48, but seems to be closer to /124 from some basic probing: 2a00:1450:4001:830::2000 to 2a00:1450:4001:830::200f seem to all respond as www.google.com, but 2a00:1450:4001:830::2010 does not.
If Google chose not to allocate a whole /48 to www.google.com, I doubt many sites would.
Typically a University campus, or a company office block, or a datacentre, or your whole distributed org if you hang the networks for your other global offices off VPNs behind one front-end site.
This is similar to how many smaller orgs used 10.site.vlan.device but obviously it scales larger (site and vlan can each be 16 bits instead of 8) and everybody gets a unique public replacement for "10."
Are you sure about this, or have a source where I can read more? There are some counterpoints: both Japanese and Chinese use four-digit grouping for numbers, and it's common to see things like credit cards use four-digit groups.
>Variations in the amplitude of the N400 showed a better memory trace for items presented in [temporal groups] of three compared to those in groups of four.
2. You absolutely lost me with your IPv6 example:
* I need to remember whether to use one colon or two, for each delimited number
* How do I even know the range of each delimited value is the same?
* How can I be sure what basis each of the delimited values is? I mean, you can tell me it's hex, but without someone telling me, I'm never quite sure.
With IPv4, it's easy: Four dot-delimited numbers, each between 0 and 255, in decimal notation.Can you describe valid IPv6 addresses like that?
The first 64 bits are the network and the last 64 bits are the host address. You write them out in groups of four hex chars (16 bits per group) separated by colons.
To make them a little more memorable, leading 0s in a group can be omitted, and '::' will be expanded to fill the middle of an address with 0s.
The 64/64 split is always the same for local networks, unlike IPv4 CIDR where the widths of each part are based on how rich you are :)
In full, without any abbreviations, `2001:db8:60:12::1` breaks down into:
`2001:db8::` – your ISP.
`2001:db8:60::` – you, their customer. This is the number you end up typing a lot, just like you type "31.101.24.xxx" if you are lucky enough to own an IPv4 /24.
`2001:db8:60:12::` – an actual network, in this case your network number 12, e.g. your toilet soap dispenser level monitoring network
`2001:db8:60:12::1` – soap dispenser controller PC
`2001:db8:60:12:7223:24ff:fe02:844e` – random soap dispenser with a giant weird self-assigned address that you don't need to care about remembering because the dispenser connects to your controller PC, not the other way around (if you did, you'd assign it a memorable address :P)
I cannot get my ISP to allocate me a SINGLE static ipv6. So it's much MUCH more expensive to get an ipv6 address than an ipv4 static IP address.
For convenience, one stretch of all-0 numbers can be omitted. FFFF::2:1
For bizarre reasons, the last 2 numbers can be replaced with an IPv4 address... FFFF::0.2.0.1
With IPv4, you just stick to an IP range that has not been assigned, and just hand out addresses. You don't even have to understand subnets properly. The net mask just tells you when a packet goes to another computer directly vs. via a gateway. It's all very direct and basic.
Compared to IPv6 where it feels like there are five different kinds of addresses, and a part of the address comes from some external authority, a part is random, and a part is assigned by you. We have had telecom technicans and IT contractors come in to set up our network and the first thing they both did was to disable IPv6, with a comment like "hell god no you don't need that stuff". They didn't seem to understand it either.
It was supposed to be this way with IPv4 as well, until we ran out of addresses. Imagine if we did not have IPv4 address exhaustion and Comcast would give you a full /24. So you have xxx.xxx.xxx.0 to xxx.xxx.xxx.255 for your home network.
> part of the address comes from some external authority
Part of any public IPv4 comes from some external authority, that's what the subnet mask delineates. People are too stuck on NAT and as a result we'll never have a truly decentralized Internet. I will say I'm having trouble wrapping my head around the need for "link-local" stuff - isn't that Layer 2's job?
Also, considering how often I have to deal things like somebody setting a wrong static IP on a device, it comforts me that this is not unleashed on the greater internet, but all I can mess up is my own LAN...
6d08:048c:4c3b:57f0:0bca:f236:e8ab:b52e
with 6d08-048c-4c3b-57f0-0bca-f236-e8ab-b52e
Though the best solution is to fully embrace the ASCII lifestyle that modern teletypes allow, and use the record separator 0x1f: 6d08048c4c3b57f00bcaf236e8abb52e [abcd-ef01--2345]
C'est la vie.)Decimal representation didn't make much sense either but we have decades of normalizing it.
Why is 255 the max in an octet?
Why do we call them octets?
I have a /23 and I want to add 10 to 192.168.0.253, how can I do this?
0.253 + 10 = 1.7
0xfd + 0xa = 0x107
Which one makes more sense?
We like the decimal representation because that's how we grew up. It doesn't actually make much sense.
It's an 8 bit value
> Why is 255 the max in an octet?
255 is the largest 8 bit value
~$ bc obase=256 253+10 001 007
But adding 10 to 0xfd? That involves converting 10 to 0xa, then adding to FD
~$ bc obase=16 10 A ibase=16 FD+A 107
Far more involved.
setfacl exists is supported for years (although I prefer windows file permission logic to be honest)
If you feel sadistic, it's also legal to use octal encoding.
[1] https://datatracker.ietf.org/doc/html/rfc6943#section-3.1.1
The prefix I get from my ISP is 56 bits long. And there's no hope of using :: in there. So yes, the public addresses are long and unmemorable.
The information content reflects that. Internal services with IPv4 are tuples of:
(public-ip, proxy-port, rfc1918-ip, actual-port)
That’s about 32 characters to type and memorize (12 + 4 + 12 + 4).
Internal services with IPv6 are tuples of:
(site-prefix, network-suffix, host-id, port)
…which for your /56 is going to be 26 characters to type and memorize (14 + 4 + 4 + 4).
E.g. 2100:db8:4032:12::431 port 123
Count the number of 0s at the ends of each of these:
People whinge about IPv6 not being worth it but two of the things included in its ergonomics are hexadecimal address notation and netmasks that are multiples of 4.And IPv6 addresses are long and unmemorable? Addresses that you actually need to memorise are, in practice, only as long as your routing hierarchy is deep.
Your site:
Your office LAN: Your printer: *