After trying to develop a good IPv6 tutorial for my fellow It’sFOSS members, I decided that it would be much more effective to gather resources that have already been developed by professionals with far greater understanding of the protocol than I have, so here’s a list of URLs pointing to the PDF documents I’ve found on the subject, and my search term:
Results of my IPv6 Internet search “introducttion to IPv6 documentation pdf”:
Yes, the time to write something is when available documents do not quite cover your topic., or if you think the presentation could be improved for your audience.
In this case, I don’t think either is true. The authors of all these manuscripts are much more knowledgeable about IPV6 than I am. While my research has taught me quite a bit about the protocol, I barely grasp what I’m reading most of the time, so I think I’ll come up a bit short on both fronts here
I hope what I’ve found, and my search term are as helpful to others as what I’ve posted here has been for me!
Interesting stuff - thanks for posting - still can’t get my head around IPV6…
I recently deployed ~20 or so RHEL 9 VMs (in VMWare) they all had to have IPV6 static addresses…
The standard for that environment is to use the last “octet” of the IPV4 address as the last “node” address for IPV6 - I don’t know what you call “octets” in IPV6 “parlance”…
I have zero idea how it works… Seems like black magic
All my home LAN machines have IPV6 addresses - but I never set them manually and my router / VDSL modem doesn’t support IPV6 DHCP (it does support IPV6 - but my ISP doesn’t)…
I have a shell script that obscures the IPV6 address… I don’t know what to do with them anyway… it basically just runs the “ip a” command - but “ip -4 a” instead…
╭─x@titanii ~/bin ‹main*›
╰─➤ bat 44.bash
───────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
│ File: 44.bash
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
1 │ #!/usr/bin/env bash
2 │ # show only ipv4 sh_te... who's got time to parse f__king ipv6???
3 │ ## ip -4 a
4 │ # probably only good for sh_t with only two NICs... e.g. wifi and eth0
5 │ clear
6 │ echo "----------------------------------------------"
7 │ echo ""
8 │ echo ""
9 │ echo ""
10 │ OUT1=$(ip -4 --brief a |grep -v lo |awk '{print $1,$3}'|head -1)
11 │ OUT2=$(ip -4 --brief a |grep -v lo |awk '{print $1,$3}'|tail -1)
12 │ # echo -e "\t\t$OUT1"|figlet -f cybermedium
13 │ echo -e "\t\t$OUT1"
14 │ echo ""
15 │ # echo -e "\t\t$OUT2"|figlet -f cybermedium
16 │ echo -e "\t\t$OUT2"
17 │ echo ""
18 │ echo ""
19 │ echo "----------------------------------------------"
╭─x@titanii ~/bin ‹main*›
╰─➤ ./44.bash
I call then “hextets” because there are eight of them in an IPv6 address (the word for eight in - I think - Latin is hex, and the values are expressed in hexadecimal notation), each hextet consisting of four 4-bit hexadecimal values (16 bits), for an address length of 128 bits. IIUC, the first four (64 bits) hextets represent your ISP, or the organization your Network belongs to, and the last four hextets represents, for example, your computer, or some othre device on your Network (LAN).
A lot about IPv6 is still Greek to me, but I hope what I gave you here helps, at least a little bit!
According to some research I did with Copilot they call it a hextet because hex is short for hexidecimal (base-16_ and -tet is patterned after octet (8 bits). In IPv4 they called it an octet because octet is 8 bits and octo means eight.
octet is a historical networking term (8 bits)
hextet was coined later to mirror the pattern, not the meaning
My first experiance of coding with files when i started work was in hexadécimal but cannot remember why as tye processors were all 8 bit. Datapoint operating system was well in advanced of many others.
I understand that, but I use the term because Hex is eight, and there are eight segments in a IPv6 address, so identifying one segment as a hextet makes sense to me, especially because the name for a segment in IPv4 was octet, for four eight bit segments. The apparent correlation is undeniable.
