# IPv6 Published articles for IPv6. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CAPIF 5: Regional Interconnectivity in Central Asia DevFeed: [CAPIF 5: Regional Interconnectivity in Central Asia]() Original publisher: [Read original article]() Author: Anastasiya Pak Published: 2026-09-17T17:29:36Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Routing Security](), [networking](), [Networks]() Tags: [2026](), [adoption](), [aspa](), [atlas](), [central](), [connectivity](), [country](), [events](), [internet](), [ipv4](), [ipv6](), [ixps](), [measurements](), [progress](), [region](), [report](), [research](), [ripe](), [ris](), [routing](), [routing-security](), [rpki](), [traffic]() ### AI overview This report examines changes in Central Asia's Internet connectivity since CAPIF 1. It describes more direct regional routes, expanding IXPs, stronger routing security and new links toward Pakistan, China, Azerbaijan and Europe, while noting persistently low IPv6 adoption and continued, though reduced, reliance on routes through Russia. ### Source excerpt Central Asia's Internet looks very different than it did back at CAPIF 1. We trace the rise of direct regional routes, stronger routing security and new connectivity options - along with the gaps that remain. ## One or two nameservers? DevFeed: [One or two nameservers?]() Original publisher: [Read original article]() Author: Geoff Huston Published: 2026-09-15T06:01:49Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Query (disambiguation)](), [Server](), [Caching]() Tags: [2026](), [africa](), [article](), [china](), [dns](), [europe](), [experiment](), [india](), [internet](), [ipv4](), [ipv6](), [measurement](), [measurements](), [recursive-resolver](), [repeat](), [responses](), [server](), [tech-matters]() ### AI overview This article reports an experiment testing whether serving a DNS zone with two authoritative dual-stack nameservers changes repeated queries. Compared with one nameserver, two nameservers increased the single-query completion rate from 58% to 71% and reduced the average queries per test from 3.43 to 2.57. ### Source excerpt Do multiple dual-stack nameservers increase or decrease repeat DNS queries? The results of this experiment were a complete surprise. ## Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more DevFeed: [Cilium 1.20: Gateway API ExternalAuth, TCPRoute/UDPRoute, ENI IPAM for IPv6, and more]() Original publisher: [Read original article]() Author: Nico Vibert and Donia Chaiehloudj, Cilium Published: 2026-09-14T10:45:49Z Content type: article Language: en Sources: [Cloud Native Computing Foundation]() Topics: [Cilium](), [Open Source](), [API](), [networking](), [Kubernetes](), [Amazon Web Services](), [eBPF](), [VPC](), [nginx]() Tags: [2026](), [api](), [authentication](), [authorization](), [aws](), [blog](), [cilium](), [cloud](), [cni](), [ebpf](), [google](), [ingress-nginx](), [ipv4](), [ipv6](), [kubernetes](), [microsoft](), [network](), [networking](), [nginx](), [open-source](), [release]() ### AI overview Cilium 1.20 expands Gateway API support with ExternalAuth, CORS filters, ListenerSets, TCPRoute, and UDPRoute. The release also introduces extensible datapath plugins, advances networking standardization with Kubernetes, and adds beta IPv6 support for AWS ENI IPAM. ### Source excerpt Cilium 1.20, the second major open source Cilium release of 2026 after Cilium 1.19, is finally here. Three themes stand out in this release: Thank you to every contributor, reviewer and maintainer who made Cilium 1.20... ## Airtel plans to begin RPKI Route Origin Validation rollout on 22 September 2026 DevFeed: [Airtel plans to begin RPKI Route Origin Validation rollout on 22 September 2026]() Original publisher: [Read original article]() Published: 2026-09-14T09:00:47Z Content type: opinion Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [networking](), [Routing Security](), [Security]() Tags: [airtel](), [apnic-62](), [as9498](), [india](), [ipv4](), [ipv6](), [routing-security](), [rov](), [rpki]() ### AI overview Airtel has told customers it plans to begin rolling out RPKI Route Origin Validation on 22 September 2026. The article examines 726 RPKI-invalid routes in Airtel's table, including 108 IPv4 and 618 IPv6 routes, and discusses their visibility outside India. ### Source excerpt Just back from Mumbai after APNIC 62 and Equinix's India Peering Forum. On excellent news: Airtel has started sending emails to its customers about RPKI RoV (Route Origin Validation). As per the mail, Airtel will start RPKI RoV soon and has mentioned 22 Sep 2026 as the timeline when they will start rolling out RoV. This is excellent news on the routing security front, and kudos to Airtel (AS9498) for taking the lead here among other large Indian backbones. This brings up the important question of how many routes exist in their table which are RPKI RoV invalids as of today? Looking at their announcements, I see the following: RPKI Valids: 33,735 RPKI Unknown: 4632 RPKI invalids: 726 This is for their table, including downstream routes. One can view the complete list of those 726 invalids, including prefix and AS_PATH here. One interesting thing here is that out of 726, 140 are from Airtel fixedline AS24560 and 122 are from Airtel Mobility. In terms of address family, there are 108 invalids from IPv4 and 618 from IPv6. How many of these invalids are single-homed vs multi-homed? This is important to check, as often the argument against RoV given by various operators in past was that they were losing traffic to their competitors. When I checked, I do not see any of these prefixes visible outside of India behind a transit-free / tier 1 network without AS9498 in the path. It could be because Tata Comm AS6453 drops RPKI invalid already & most of these are not dual-homed via Jio AS64049. So unless a less specific RPKI valid announcement is there, these are anyway largely blackholed for now by networks & IXPs doing RoV outside of India. Let's hope other Indian backbones also start doing RPKI RoV soon. Happy routing! 😀 ## Configuring Management IP Addresses to Virtual Network Devices DevFeed: [Configuring Management IP Addresses to Virtual Network Devices]() Original publisher: [Read original article]() Published: 2026-09-14T05:29:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [configuration](), [Orchestration](), [Vagrant](), [Cloud](), [ssh]() Tags: [cli](), [cloud](), [devices](), [dhcp](), [ip](), [ipv4](), [ipv6](), [management](), [netlab](), [network](), [networking](), [orchestration](), [server](), [ssh]() ### AI overview The article explains how to assign predictable management IP addresses to virtual network devices. It contrasts manual console-based setup with automated assignment through orchestration, containers, DHCPv4/DHCPv6, custom Vagrant boxes, and IPv6 mechanisms such as SLAAC. ### Source excerpt It goes without saying that if you want to configure (virtual) network devices with any semi-sane configuration mechanism1, the device must have a working IP address. Here's the time-honored method2 to assign an IP address to a virtual network device: Start the virtual machine (using a GUI)3 Open a new window: either a telnet session to the virtual console port or a full-blown virtual console (GUI) session. Manually configure the IP address, the SSH server, and the user credentials on the first interface. Read more ... ## The /3 Body Problem DevFeed: [The /3 Body Problem]() Original publisher: [Read original article]() Author: Remco van Mook Published: 2026-09-10T09:22:46Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [networking](), [Internet](), [Internet Engineering Task Force (IETF)]() Tags: [article](), [ietf](), [internet](), [ipv6](), [networking](), [policy](), [space]() ### AI overview The article examines how IPv6 addressing and policy mechanisms may need to evolve for space networking. It argues that terrestrial assumptions break down beyond low Earth orbit and calls for addressing policy questions now, including through the proposed EXPANSE working group. ### Source excerpt A large chunk of IPv6 is heading for space, and every policy question about it is currently going to be deferred to the RIR communities. This article outlines what those questions look like, and argues why now is the time to start asking them. ## Worth Reading 090926 DevFeed: [Worth Reading 090926]() Original publisher: [Read original article]() Author: Russ Published: 2026-09-09T20:17:31Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [Internet](), [Networks](), [data]() Tags: [data](), [internet](), [ipv6](), [ixps](), [networks](), [peering](), [worth-reading]() ### AI overview A technology reading roundup touching on how Internet Exchange Points affect Internet performance, the meaning and use of industrial Modbus packet data, and the societal risks and benefits associated with IPv6. It also briefly evokes robotic pizza preparation. ### Source excerpt Information is not meaningful simply because it exists or because it is improbable. It becomes meaningful only if there exists a system that can interpret it and use it to perform a function. At first glance, asking whether Internet Exchange Points (IXPs) make the Internet faster may seem almost provocative at a peering forum. Surely the answer is simply 'yes'? If you're dealing with industrial protocols, you'll certainly have seen Modbus packets in your network. But what are these packets used for, and what data do they contain? Yet I have become increasingly concerned that, in the case of IPv6, we are evaluating the technology almost entirely from the perspective of what it allows networks to do, while giving insufficient attention to what it may allow network operators, corporations and governments to do to their users and if the benefits outweigh the risks. The future of fast food was supposed to look something like this: walk into a restaurant, place an order, and watch a robot assemble your pizza with machine-like precision. ## APNIC and NIXI partner to strengthen routing security and technical capacity in India DevFeed: [APNIC and NIXI partner to strengthen routing security and technical capacity in India]() Original publisher: [Read original article]() Author: Dan Fidler Published: 2026-09-09T09:01:06Z Content type: news Language: en Sources: [APNIC Blog]() Topics: [Routing Security](), [Security](), [Internet](), [Resilience](), [networking]() Tags: [apnic-62](), [collaboration](), [development](), [india](), [infrastructure](), [internet](), [ipv6](), [knowledge-sharing](), [nixi](), [partnership](), [resilience](), [routing](), [routing-security](), [rpki](), [security](), [skills](), [support]() ### AI overview APNIC and NIXI have signed an MoU to strengthen routing security and technical capacity in India. The partnership will expand IPv6 and RPKI deployment, pilot an RPKI repository mirror, promote routing security practices, and support technical training and knowledge sharing. ### Source excerpt The partnership will expand IPv6 and RPKI deployment including piloting an RPKI Repository Mirror to support a more secure and resilient Internet ecosystem. ## Welcome to APNIC 62 DevFeed: [Welcome to APNIC 62]() Original publisher: [Read original article]() Author: Timothy Hildred Published: 2026-09-08T03:33:07Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Networks](), [Cybersecurity](), [DNSSEC](), [threat detection](), [Threat Research](), [FIRST]() Tags: [apnic-62](), [community](), [conference](), [conferences](), [cybersecurity](), [dnssec](), [event](), [events](), [india](), [ipv4](), [ipv6](), [nixi](), [nro](), [policy-sig](), [tech-matters](), [threat-detection]() ### AI overview APNIC 62 in Mumbai previews technical, security, IPv6 deployment, DNSSEC, threat-detection, community, and policy sessions, alongside keynote talks, social events, newcomer activities, and NRO NC voting information. ### Source excerpt APNIC welcomes you to Mumbai, India for APNIC 62. Here is what you can look forward to over the coming days. ## Rootless Podman: Preserving Source IPs DevFeed: [Rootless Podman: Preserving Source IPs]() Original publisher: [Read original article]() Author: Jan Rodak Published: 2026-09-04T14:25:02Z Content type: article Language: en Sources: [blog.podman.io]() Topics: [podman](), [Containers](), [Networks](), [Access Control](), [Logging]() Tags: [blog](), [bridge](), [container](), [containers](), [ipv4](), [ipv6](), [logging](), [networks](), [podman](), [port](), [rate-limiting](), [routing](), [tips-and-tricks]() ### AI overview This article explains how Pesto, a companion tool from the passt project, addresses Rootless Podman's inability to preserve incoming client source IPs on bridge networks. Pesto updates pasta's forwarding table so traffic reaches containers without source-address rewriting, while retaining existing port-mapping capabilities. The article also documents configuration steps, traffic flow, supported networking features, and limitations when switching from the current forwarder. ### Source excerpt Rootless Podman has a long-standing limitation reported since 2020: containers on bridge networks can't see the real source IP of incoming connections. The `rootlessport` userspace proxy rewrites the source to the container's own subnet address, breaking IP-based access control, logging, and rate limiting. Pesto, a new companion tool from the passt project solves this. Pesto [...] ## Closing the IPv6 First-Packet Gap with GRAND DevFeed: [Closing the IPv6 First-Packet Gap with GRAND]() Original publisher: [Read original article]() Author: Seyed Pouria Mousavizadeh Tehrani Published: 2026-09-04T13:32:29Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Network](), [Internet](), [reactive](), [Latency]() Tags: [competition](), [internet](), [ipv6](), [latency](), [network](), [open-source](), [reactive]() ### AI overview The article explains an IPv6 Neighbour Discovery asymmetry: a host can reach its router immediately after configuring an address, while the router may not yet know how to reach the host. This can delay or drop the first return packets. GRAND addresses the gap by having the host proactively advertise its address, and the article describes an implementation of this mechanism in FreeBSD. ### Source excerpt There is a subtle asymmetry in IPv6 Neighbour Discovery: a host knows how to reach its router before the router necessarily knows how to reach the host. GRAND fixes that asymmetry by making the host proactively advertise its address, and I implemented that mechanism in FreeBSD. ## South Asia SRF highlights Member priorities on IPv6, routing security, and training DevFeed: [South Asia SRF highlights Member priorities on IPv6, routing security, and training]() Original publisher: [Read original article]() Author: Dale Roberts Published: 2026-08-25T06:04:35Z Content type: news Language: en Sources: [APNIC Blog]() Topics: [networking](), [Routing Security](), [SANOG](), [Availability]() Tags: [aspa](), [community](), [deployment](), [development](), [event](), [infrastructure](), [internet](), [ipv4](), [ipv6](), [network](), [networks](), [routing-security](), [rpki](), [sanog](), [south-asia](), [subregional-forum](), [training]() ### AI overview The South Asia APNIC Sub-Regional Forum, held alongside SANOG 44 in Kathmandu, brought together more than 100 Members and regional Internet stakeholders. Discussions emphasized IPv6 deployment, routing security using RPKI, ROV, and ASPA, Internet resource and registry management, policy participation, automation, IPv4 availability, and practical technical training. ### Source excerpt More than 100 APNIC Members attended the South Asia APNIC Sub-Regional Forum alongside SANOG 44 in Kathmandu. Member feedback gathered during the event will help inform APNIC's future priorities across the region. ## AI, IPv6, and the future Internet at IETF 126 DevFeed: [AI, IPv6, and the future Internet at IETF 126]() Original publisher: [Read original article]() Author: Anlei Hu Published: 2026-08-25T01:20:50Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Internet Engineering Task Force (IETF)](), [networking](), [Artificial Intelligence](), [AI Agent](), [Network](), [Security](), [Latency](), [telemetry]() Tags: [ai](), [dns](), [guest-post](), [ietf](), [infrastructure](), [internet](), [internet-infrastructure](), [ipv6](), [latency](), [low-latency](), [nat](), [network](), [networks](), [opinion](), [security](), [standards](), [tech-matters](), [telemetry]() ### AI overview The article reports on IETF 126 discussions about how AI is shaping Internet infrastructure. It presents IPv6 as important for the scale, globally unique addressing, and traceability required by distributed AI deployments and agents, while DNS remains central to service discovery. It also covers IPv4/IPv6 mapping, NAT-related identity and security concerns, SRv6, low-latency forwarding, IOAM telemetry, and proposals for DNS-based AI agent discovery. ### Source excerpt Guest Post: At IETF 126, discussions highlighted how AI is beginning to shape the future of Internet infrastructure. Participants identified IPv6 as a critical foundation for large-scale AI ecosystems and explored new approaches. ## Connect an ESP device and iPhone directly using Wi-Fi Aware DevFeed: [Connect an ESP device and iPhone directly using Wi-Fi Aware]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-25T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Wi-Fi](), [iOS](), [iphone](), [cross-platform](), [P2P](), [Internet of things](), [networking]() Tags: [android](), [app](), [blog](), [cross-platform](), [esp-idf](), [esp-idf-component](), [how-to](), [ios](), [iot](), [iphone](), [ipv6](), [p2p](), [pairing](), [practitioner](), [security](), [wi-fi](), [wi-fi-aware]() ### AI overview This tutorial explains how to connect an ESP device directly to an iPhone using Wi-Fi Aware. It describes service discovery, mandatory six-digit PIN pairing, and an encrypted IPv6 data link without an access point, DHCP server, or internet connection. On supported devices running iOS 26 or iPadOS 26, the connection can operate concurrently with normal Wi-Fi connectivity. ### Source excerpt iOS 26 brings Wi-Fi Aware™ support on iPhone 12 and later, enabling compatible devices to securely discover, pair, and communicate directly. This requires no Access Point and does not affect iPhone's network connectivity over Wi-Fi. This article walks through the steps to set up an ESP device and an iPhone so they can pair and connect using Wi-Fi Aware. ## APNIC 62 OPM: Just the facts DevFeed: [APNIC 62 OPM: Just the facts]() Original publisher: [Read original article]() Author: Dave Phelan Published: 2026-08-21T02:47:03Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Networks](), [Protocol (disambiguation)]() Tags: [apnic-62](), [article](), [community](), [dns](), [internet](), [ipv4](), [ipv6](), [management](), [networks](), [open](), [policy](), [policy-development-process](), [policy-sig]() ### AI overview An overview of policy proposals for the APNIC 62 Open Policy Meeting, covering IPv6 allocation flexibility, transitional IPv4 access for IPv6-only networks, and Internet abuse handling. ### Source excerpt The APNIC 62 Open Policy Meeting will consider a diverse set of policy proposals covering IPv4 management, IPv6 allocation practices, and Internet abuse handling. ## The Never-Ending IPv6 Loopback Prefix Saga DevFeed: [The Never-Ending IPv6 Loopback Prefix Saga]() Original publisher: [Read original article]() Published: 2026-08-17T06:02:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Hardware](), [datacenter](), [BGP]() Tags: [bgp](), [datacenter](), [hardware](), [ios](), [ipv6](), [is-is](), [netlab](), [network](), [ospf](), [vxlan]() ### AI overview The article examines the IPv6 loopback-prefix problem in high-speed routers and data-center switches. OSPFv3 requires loopbacks to be advertised as /128s, which can increase forwarding hardware demands when /64 addressing is preferred. It compares vendor behaviors and suggests IS-IS or BGP as possible alternatives. ### Source excerpt Remember the sage advice to simplify your life and use the IPv6 /64 prefixes everywhere? Not only does it make your life simpler (and wastes immesuarably less address space than the crazy "let's assign /64 to every device" stupidity), it also reduces the hardware requirements in your high-speed routers layer-3 switches. You see, doing lookups on 64 bits uses half the silicon it takes to do lookups on 128 bits. Alas, some people never got the memo. OSPFv3 standard clearly states in one of the bullets in section 4.4.3.9 that the loopback prefixes should always be advertised as /128s regardless of what's configured on the interface. Read more ... ## India's Internet ecosystem in 2026: Growth, resilience, and the road ahead DevFeed: [India's Internet ecosystem in 2026: Growth, resilience, and the road ahead]() Original publisher: [Read original article]() Author: Samantha Douglas Published: 2026-08-17T01:30:48Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Networks](), [Resilience](), [5G](), [cloud-infrastructure]() Tags: [5g](), [apnic-62](), [community](), [development](), [digital-platforms](), [digital-transformation](), [economy-report](), [education](), [finance](), [global](), [government](), [growth](), [healthcare](), [india](), [infrastructure](), [internet](), [ipv6](), [measurement](), [mobile](), [networks](), [resilience](), [scale]() ### AI overview India's Internet ecosystem has expanded through affordable mobile broadband, major digital infrastructure investment, and strong IPv6 adoption. The article examines the shift from rapid growth toward resilient, secure, and inclusive connectivity, while highlighting persistent rural and remote access gaps and the continued expansion of 4G, 5G, and fixed broadband. ### Source excerpt India has built one of the world's largest Internet ecosystems through affordable mobile broadband, digital infrastructure investment, and IPv6 leadership. As it prepares to host APNIC 62, the challenge is ensuring connectivity remains resilient, secure, and inclusive. ## Deploying IPv6-first EKS on AWS: What Still Doesn't Work, and What It Saves DevFeed: [Deploying IPv6-first EKS on AWS: What Still Doesn't Work, and What It Saves]() Original publisher: [Read original article]() Author: Spiro Stathakis Published: 2026-08-14T08:57:28Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Amazon Elastic Kubernetes Service](), [Amazon Web Services](), [VPC](), [networking](), [cloud-infrastructure](), [Kubernetes]() Tags: [2026](), [amazon](), [amazon-elastic-kubernetes-service](), [aws](), [cni](), [competition](), [cost](), [ip](), [ipv4](), [ipv6](), [kubernetes](), [nat](), [networking](), [networks](), [vpc]() ### AI overview A field report on deploying an IPv6-first Amazon Elastic Kubernetes Service platform on AWS. It explains how IPv6 pods, VPC networking, and an egress-only Internet gateway reduce dependence on NAT gateways and public IPv4 addresses, while legacy IPv4-only dependencies such as databases, payment APIs, and container registries still impose compatibility requirements and costs. ### Source excerpt In this field report on IPv6-first Amazon Elastic Kubernetes Service (EKS), the isp6 team shares which dependencies still drag IPv4 back in, what they learnt from /28s, and why the saving is large but not automatic. ## netlab 26.08: ArcOS, VPP (FD.io), ACLs, and DNS DevFeed: [netlab 26.08: ArcOS, VPP (FD.io), ACLs, and DNS]() Original publisher: [Read original article]() Published: 2026-08-10T09:58:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [networking](), [Containers](), [configuration](), [Routing (disambiguation)](), [Authorization]() Tags: [access-control](), [configuration](), [dns](), [getting-started](), [github](), [gre](), [installation](), [ipv4](), [ipv6](), [netlab](), [podman](), [release](), [release-notes](), [routing]() ### AI overview netlab 26.08 adds ArcOS support, VPP with FRR or BIRD control planes, SONiC containers, IPv4/IPv6 access control lists, DNS client and server configuration, GRE and WireGuard tunnel support, and Podman support for the clab provider. The article also notes bug fixes, configuration-template changes, upgrade guidance, and documentation for new users. ### Source excerpt netlab release 26.08 brings a few humongous additions: ArcOS support by @roc-ops VPP (FD.io) with FRR or BIRD control plane by @jbemmel SONiC containers (also by @roc-ops) IPv4/IPv6 access control lists in the routing module by @DanPartelly But wait, there's more: Read more ... ## IP Addressing, Part III: Inside the IP Packet DevFeed: [IP Addressing, Part III: Inside the IP Packet]() Original publisher: [Read original article]() Author: Franco Fernando Published: 2026-08-07T09:49:52Z Content type: tutorial Language: en Sources: [The Polymathic Engineer]() Topics: [Network](), [Protocol (disambiguation)]() Tags: [fragmentation](), [internet](), [ipv4](), [ipv6](), [network](), [payload](), [protocol]() ### AI overview This tutorial examines the IPv4 datagram and header fields, explains fragmentation and MTU constraints, discusses why TCP and IP use checksums, and describes changes introduced by IPv6. ### Source excerpt What actually travels on the wire: the IPv4 header, fragmentation, and what IPv6 changed. ## Introducing the J2sw MTU and Encapsulation Calculator DevFeed: [Introducing the J2sw MTU and Encapsulation Calculator]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-28T16:37:53Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Network](), [Tool](), [Ethernet](), [VXLAN]() Tags: [calculator](), [cisco](), [ethernet](), [fragmentation](), [gre](), [headers](), [ipsec](), [ipv4](), [ipv6](), [juniper](), [mikrotik](), [mpls](), [mtu](), [network-engineering-resources](), [network-tools](), [network-troubleshooting](), [overhead](), [payload](), [pppoe](), [vlan](), [vxlan]() ### AI overview The article introduces the J2SW MTU and Encapsulation Calculator, which estimates inner IP MTU and required underlay MTU for combinations of PPPoE, GRE, VLAN, MPLS, VXLAN, and other encapsulations. It explains how Layer 2 tags affect Ethernet frame size separately from IP MTU and describes overhead calculations, including cases where fragmentation can be avoided. ### Source excerpt Ever wondered what the effects of different combinations of PPPoE, GRE, and others have on the MTU of a packet? I am excited to announce the first of many J2 Network tools: the J2SW MTU and Encapsulation Calculator. You select the service MTU and the encapsulation used on the path. The calculator then works out ... Read more The post Introducing the J2sw MTU and Encapsulation Calculator appeared first on Justin Wilson (j2sw). ## Worth Reading 072826 DevFeed: [Worth Reading 072826]() Original publisher: [Read original article]() Author: Russ Published: 2026-07-28T10:59:47Z Content type: article Language: en Sources: [rule 11 reader]() Topics: [Internet](), [data](), [Internet Engineering Task Force (IETF)](), [Networks](), [5G](), [Machine learning]() Tags: [5g](), [ai](), [arp](), [article](), [data](), [ietf](), [internet](), [ipv6](), [networks](), [worth-reading]() ### AI overview A developer reading roundup covering Internet infrastructure, synchronization of replicated data, IPv6-only networking, IPv4 dependencies, ARP, an IETF proposal, 5G control-plane timers, modern machine-learning pipelines, and the integration of AI into everyday applications. ### Source excerpt Today's Internet runs on a vast infrastructure of replicated data, and the difference between order and chaos lies in maintaining consistency through synchronization across the many distributed points where that data is published. IPv6-only networks often still depend on IPv4 subnets and ARP. This article introduces an IETF proposal to eliminate both. Traditional software engineering approaches reliability as a binary state of uptime and downtime. Modern ML pipelines render this paradigm obsolete. Yet while the radios and protocols largely reuse terrestrial 5G designs, one small but crucial component has been left behind: The control plane timers that quietly govern how registration, mobility, and session procedures behave under real-world conditions. Apparently, nearly all of them have reached the same conclusion. I don't merely need AI occasionally. I need it waiting inside every search bar, messaging app, music player, and document reader I already use. ## Self-service peering with a PeeringDB login DevFeed: [Self-service peering with a PeeringDB login]() Original publisher: [Read original article]() Author: Bastiaan Brink Published: 2026-07-27T00:00:00Z Content type: opinion Language: en Sources: [AS215248 - Notes]() Topics: [Networks](), [OAuth](), [Server]() Tags: [automation](), [bgp](), [dashboard](), [ipv4](), [ipv6](), [ixp](), [login](), [mail](), [networks](), [oauth](), [peering](), [permission](), [request](), [self-service]() ### AI overview The article describes a self-service peering portal that uses PeeringDB OAuth to authenticate users, verify ASN update rights, and offer exchanges where both networks are present. Requests create disabled sessions for manual approval, with inherited filtering and validation policies, notifications, and approval-based removal. ### Source excerpt Peering requests used to be mail ping-pong. Now you log in with PeeringDB on the peering page, pick an exchange, and the session is waiting for my approval. ## osmo-ePDG - VoWifi Evolved Packet Data Gateway - osmo-epdg 0.1.2 released DevFeed: [osmo-ePDG - VoWifi Evolved Packet Data Gateway - osmo-epdg 0.1.2 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-07-22T09:00:22Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [gateway](), [changelog](), [version]() Tags: [bug](), [changelog](), [compiler](), [gateway](), [ipv6](), [issue](), [tracker](), [version]() ### AI overview Osmocom released osmo-epdg 0.1.2, an unstable release of its VoWifi Evolved Packet Data Gateway. The changelog lists IPv4/IPv6 support improvements, Diameter and GTP-related fixes, dependency updates, documentation changes, and test updates. ### Source excerpt Today we've released osmo-epdg 0.1.2. The changelog over 0.1.0 is as follows: osmo-epdg (0.1.2) unstable; urgency=medium [ clufn-sudo ] * Add required conversions for IPv6 and IPv4v6 support [ clufn ] * Enable the use of an UE requested IP type and address to be used for gtpv2 PDN Address Allocation [ Pau Espin Pedrol ] * gsup: Fix rx of AuthInfoReq without IP addr val * rebar.config: Update rebar3_diameter_compiler from 0.8.0 to v0.8.1 * dia/diameter_3gpp_ts29_173.dia: Fix trailing whitespace * dia/diameter_3gpp_ts29_273.dia: Fix trailing whitespace * dia/diameter_3gpp_ts29_229.dia: inherit only Line-Identifier * dia/diameter_3ggp_ts32_299.dia: Inherit RFC4005 instead of RFC7155 * dia: restrict AVPs inherited from RFC4005 * Remove duplicate 3GPP-AAA-Server-Name definition and break 3-way circular dependency * cosmetic: Fix typo in code documentation * aaa_ue_fsm: Avoid immediate stop of fsm during 2nd SWx RTR * aaa_diameter_swx: Avoid answering RTR with Success if already deregistering [ Alexander Couzens ] * s2b: set correct instance values for Bearers * diameter_3gpp_ts29_273_swx: add missing include for MAR * aaa_diameter_swx_tests: explicitly set Framed-IP-Address * aaa_diameter_swx_tests: use MAR record to improve readability [ Oliver Smith ] * editorconfig: new file [ Vadim Yanitskiy ] * rebar.config: use more recent rebar3_diameter_compiler * rebar.lock: use a more recent version of gen_netlink -- Oliver Smith Tue, 21 Jul 2026 14:12:41 +0200 osmo-epdg (0.1.1) unstable; urgency=medium [ Harald Welte ] * add notice about NLnet found ation to README.md * README.md: Use NLnet suggested language for funding acknowledgement * README.md: Update user manual section; we now have one. [ Oliver Smith ] * rebar.lock: update gtplib commit -- Oliver Smith Wed, 04 Dec 2024 15:24:46 +0100 [Next page]()