Posts

eir Mobile and GoMo now support IPv4v6 and IPv6

APNs data.myeirmobile.ie and broadband.myeirmobile.ie now also support IPv4v6 and IPv6 connections. To manually update a phone to also have IPv6 connectivity edit the APN protocol to "IPv6" or "IPv4/IPv6". Most Android phones let the APN protocol be edited. Apple iOS phones do not let this setting be edited by the user. Existing phones of all types will continue to request IPv4 connections until their software/configuration settings have been updated to request IPv4v6 or IPv6. In all cases phones will continue to have IPv4 connectivity even when the requested APN protocol is "IPv6". More technical details IPv6 end-to-end traffic bypasses the network NAT. The IPv6 DNS servers advertised by the eir network generate DNS64 AAAA responses to DNS queries made over IPv6 transport. i.e. DNS IPv6 AAAA records are synthesised for FQDNs that only have IPv4 A records. IPv4v6 is dual stack, the UE (User Equipment e.g. a smartphone) requests both an IPv4 address and an

Updates to eir fibre broadband IPv6 support

Delegated Prefix lease persistency enhanced To help prevent changes to the Delegated Prefix assigned to a requesting DHCPv6 client the DHCPv6 server now remembers the lease for 15 minutes after the lease has timed out. The server also remembers the lease even when the client sends a solicited-release for it. This lets the router be reconfigured without losing its lease. Leases are bound to the MAC address of the requesting router's WAN interface. If the router's WAN interface MAC changes a different Delegated Prefix will be assigned. A typical example of when this occurs is a router swap. If a different Delegated Prefix is desired; turn the client router off for 75 minutes so that the lease also times out at the DHCPv6 server. F2000 firmware update B050 This minor update began rolling out in mid August 2018. It improves the reliability of the IPv6 connection. Specifically B050 fixes a bug in the DHCPv6 client which can occur if the WAN link goes down and comes back u

Do not put IPv4-mapped IPv6 Addresses into AAAA DNS records

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

Internet Settings Tab in F2000

Image
B036_demo firmware

IPv6 in eir Fibre broadband

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

Some reasons IPv6 is good for the Internet

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