BB6

RFC 6890 - Special-Purpose IP Address Registries - provides the following table showing that these address should never be seen on a link and are not for Global use. +----------------------+---------------------+ | Attribute | Value | +----------------------+---------------------+ | Address Block | ::ffff:0:0/96 | | Name | IPv4-mapped Address | | RFC | [ RFC4291 ] | | Allocation Date | February 2006 | | Termination Date | N/A | | Source | False | | Destination | False | | Forwardable | False | | Global | False | | Reserved-by-Protocol | True

B036_demo firmware

The F2000 modem supports dual-stack Internet access. Modem WAN Interface The modem has to request IPv6  in addition to the old IPv4. IPv6 is provided in parallel with IPv4 in native Dual-Stack mode (neither DS-Lite or 6RD modes are used). The F2000 modem's DHCPv6 client requests a delegated prefix (IA_PD) from the network. The network DHCPv6 server responds with an Advertise message containing the delegated prefix with a valid-lifetime of 1 hour. The same prefix will be assigned as long as the modem is connected. If the modem is disconnected for 1 hour or sends a Release message (e.g. when set to IPv4 only) a different delegated prefix will be The Internet's assigned on a subsequent request. Modem LAN/WiFi Interface There's nothing to do on the LAN/WiFi side , it is all automatic. The modem selects a fixed /64 prefix from the delegated prefix and uses SLAAC to provide IPv6 addresses to connected wired and WiFi devices. The remainder of the delegated prefix is rese

The public IPv6 Internet can grow vastly larger, there are 18 billion billion /64 prefixes in comparison to IPv4's ~ 4 billion single addresses. IPv6 allows Internet Transparency (see RFC 4924) whereas sharing IPv4 addresses breaks it The Internet end-to-end principle is practical again using IPv6 Applications on hosts don't have to share addresses either The IPv6 Internet can free itself from the technical restrictions of public IPv4 rationing and of NAT There are no NAT restrictions on the range and number of TCP/UDP ports that an IPv6 host may use No additional restrictions due to multiple layers of address sharing, e.g. in the home router and in the provider's network No delays due to being diverted to and passing through stateful CGNAT No need to send frequent keepalives to keep UDP port mappings from timing out No broken Application Level Gateways (ALGs) to traverse Application creators do not have to support NAT traversal End-to-end connectivity need