Prefix | Subnet Example | Total IP Addresses | # of /64 nets |
---|---|---|---|
4 | x:: | 2 124 | 2 60 |
8 | xx:: | 2 120 | 2 56 |
12 | xxx:: | 2 116 | 2 52 |
16 | xxxx:: | 2 112 | 2 48 |
20 | xxxx:x:: | 2 108 | 2 44 |
24 | xxxx:xx:: | 2 104 | 2 40 |
28 | xxxx:xxx:: | 2 100 | 2 36 |
32 | xxxx:xxxx:: | 2 96 | 4,294,967,296 |
36 | xxxx:xxxx:x:: | 2 92 | 268,435,456 |
40 | xxxx:xxxx:xx:: | 2 88 | 16,777,216 |
44 | xxxx:xxxx:xxx:: | 2 84 | 1,048,576 |
48 | xxxx:xxxx:xxxx:: | 2 80 | 65,536 |
52 | xxxx:xxxx:xxxx:x:: | 2 76 | 4,096 |
56 | xxxx:xxxx:xxxx:xx:: | 2 72 | 256 |
60 | xxxx:xxxx:xxxx:xxx:: | 2 68 | 16 |
64 | xxxx:xxxx:xxxx:xxxx:: | 2 64 (18,446,744,073,709,551,616) | 1 |
68 | xxxx:xxxx:xxxx:xxxx:x:: | 2 60 (1,152,921,504,606,846,976) | 0 |
72 | xxxx:xxxx:xxxx:xxxx:xx:: | 2 56 (72,057,594,037,927,936) | 0 |
76 | xxxx:xxxx:xxxx:xxxx:xxx:: | 2 52 (4,503,599,627,370,496) | 0 |
80 | xxxx:xxxx:xxxx:xxxx:xxxx:: | 2 48 (281,474,976,710,656) | 0 |
84 | xxxx:xxxx:xxxx:xxxx:xxxx:x:: | 2 44 (17,592,186,044,416) | 0 |
88 | xxxx:xxxx:xxxx:xxxx:xxxx:xx:: | 2 40 (1,099,511,627,776) | 0 |
92 | xxxx:xxxx:xxxx:xxxx:xxxx:xxx:: | 2 36 (68,719,476,736) | 0 |
96 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:: | 2 32 (4,294,967,296) | 0 |
100 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:x:: | 2 28 (268,435,456) | 0 |
104 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xx:: | 2 24 (16,777,216) | 0 |
108 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxx:: | 2 20 (1,048,576) | 0 |
112 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:: | 2 16 (65,536) | 0 |
116 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:x:: | 2 12 (4,096) | 0 |
120 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xx:: | 2 8 (256) | 0 |
124 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxx:: | 2 4 (16) | 0 |
128 | xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx | 2 0 (1) | 0 |
If auto configuration is desired, the smallest subnet that can be used locally is a standard size IPv6 subnet defined by the IETF, specifically, a /64.
In establishing service on the WAN, it is customary for an ISP to assign a subnet of /64 or smaller. On the other hand, for LAN use, an additional network is routed. The extent of the allocation is contingent on the ISP, however, it is not unusual for end users to be allotted a minimum of /64 and potentially even up to a /48.
Hurricane Electric, the operator of tunnelbroker.net, offers the provision of a /48 alongside a routed /64 subnet and a /64 interconnect.
In the case of larger assignments exceeding /64, it is common practice to allocate the initial /64 for local area network (LAN) implementation and divide the remaining pool of addresses according to specific needs, such as for establishing VPN tunnels, creating a DMZ, or setting up a guest network.
IPv6 provides reserved networks for special use. The Wikipedia IPv6 article contains a comprehensive list of these networks. Below, you will find six examples of special IPv6 networks along with their corresponding addresses in the section titled "IPv6 Special Networks and Addresses."
Network | Purpose |
---|---|
2001:db8::/32 | Documentation prefix used for examples |
::1 | Localhost |
fc00::/7 | Unique Local Addresses (ULA) - also known as “Private” IPv6 addresses. |
fe80::/10 | Link Local addresses, only valid inside a single broadcast domain. |
ff00::0/8 | Multicast addresses |
In the realm of local segments, IPv4 hosts establish connection with one another through the utilization of ARP broadcast messages. On the other hand, IPv6 hosts achieve the same purpose by means of dispatching Neighbor Discovery Protocol (NDP) messages. Commonly found within a particular broadcast domain, NDP, reminiscent of ARP, serves the purpose of locating other hosts within a designated subnet.
NDP, which stands for Neighbor Discovery Protocol, takes care of neighbor discovery, router solicitations, and route redirects in a manner similar to ICMP redirects in IPv4 by means of sending specialized ICMPv6 packets towards reserved multicast addresses.
In order for NDP to function, pfSense® software will automatically include firewall rules on interfaces that are IPv6 enabled. The firewall GUI located at Diagnostics > NDP Table provides visibility of all currently known IPv6 neighbors.
Instead of using DHCP, routers in IPv6 are discovered using Router Advertisement (RA) messages. Routers that can dynamically allocate addresses will broadcast their presence on the network and respond to requests for routers. When pfSense software is configured as a client for WAN interfaces, it will accept RA messages from upstream routers. On the other hand, when pfSense software is functioning as a router, it will send RA messages to clients on its internal networks. For further information, refer to Router Advertisements (Or: “Where is the DHCPv6 gateway option?”).
Various methods, including static addressing through SLAAC (Router Advertisements (Or: “Where is the DHCPv6 gateway option?”)), DHCP6 (IPv6 Router Advertisements), or alternative tunneling methods such as OpenVPN, can be utilized to allocate client addresses.
The rephrased text: Within the context of network configuration, DHCP6 Prefix Delegation refers to the provision of a routed IPv6 subnet to a DHCP6 client. To enable this, it is possible to configure a WAN type interface to receive a prefix via DHCP6 using the Track Interface mechanism. Additionally, a router positioned at the periphery of a sizeable network can offer prefix delegation to other routers within the network via DHCPv6 Prefix Delegation.