# Router Published articles for Router. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Dense vs. MoE Models: Active Parameters, Throughput, and When to Choose Each DevFeed: [Dense vs. MoE Models: Active Parameters, Throughput, and When to Choose Each]() Original publisher: [Read original article]() Author: Elizabeth Goodman Published: 2026-09-15T17:00:11Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Mixture of Experts (MoE)](), [Nemotron](), [Routing (disambiguation)]() Tags: [agentic-ai-generative-ai](), [ai-inference](), [architecture](), [cost](), [data-center-cloud](), [deployment](), [llms](), [memory](), [mixture-of-experts-moe](), [models](), [moe](), [nemo](), [nemotron](), [performance](), [router](), [routing](), [tokens]() ### AI overview This article explains how dense and Mixture-of-Experts models activate parameters, compares their effects on throughput, memory cost, and serving complexity, and discusses when each architecture fits different deployment constraints. It uses Nemotron 3.5 Lightning as an example of an MoE model. ### Source excerpt How can a 30B-parameter model activate only 3B parameters per token, and still use the capacity of the larger model? Nemotron 3.5 Lightning illustrates the... ## Accelerating Dropless MoE Training in JAX with NVIDIA Transformer Engine DevFeed: [Accelerating Dropless MoE Training in JAX with NVIDIA Transformer Engine]() Original publisher: [Read original article]() Author: Tanya Lenz Published: 2026-09-14T16:39:15Z Content type: article Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [Mixture of Experts (MoE)](), [Artificial Intelligence](), [GPU](), [Large Language Model](), [Nvidia](), [Routing (disambiguation)](), [GB200](), [Network](), [Python](), [deepseek](), [mixtral](), [qwen]() Tags: [agentic-ai-generative-ai](), [ai](), [communication](), [deepseek](), [developer-tools-techniques](), [gb200](), [gpu](), [mixtral](), [mixture-of-experts-moe](), [mlops](), [moe](), [networks](), [nvfp4](), [nvidia](), [performance](), [python](), [qwen](), [router](), [routing](), [tensors](), [token](), [tokens](), [training-ai-models]() ### AI overview This article explains how NVIDIA Transformer Engine and JAX kernel optimizations accelerate dropless Mixture of Experts (MoE) training. It describes bottlenecks from token routing, expert dispatch and gathering, all-to-all communication, and ragged expert matrix operations. In DeepSeek-V3 training on NVIDIA GB200, the optimized approach increased performance from 103 to 1,068 TFLOPS per GPU, a 10.4x improvement. ### Source excerpt Mixture of experts (MoE) has become one of the defining architectural trends in large-scale AI model training. DeepSeek, Qwen, and Mixtral are examples of MoE... ## One name in, whichever vendor you like out DevFeed: [One name in, whichever vendor you like out]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-10T11:21:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Tutorial](), [API](), [Large Language Model](), [App](), [Bot]() Tags: [ai-gateway](), [ai-governance](), [ai-strategy](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [developers](), [enterprise](), [llm](), [llm-governance](), [model](), [router](), [tutorial]() ### AI overview A tutorial explains how to use Tyk's Model Router as a single OpenAI-compatible endpoint that routes requests to registered LLM providers. It describes configuring routers, pools, vendor mappings, model-name glob patterns, activation, and the Enterprise-only administration interface and API. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given a router. Not the sort that sits in a cupboard blinking reproachfully at you. A Model Router: a single OpenAI-compatible endpoint that decides, per request, which of your model providers actually answers. Your application asks for a model by name. Which vendor serves [...] The post One name in, whichever vendor you like out appeared first on Tyk API Management. ## Building resilient self hosted services is not always easy DevFeed: [Building resilient self hosted services is not always easy]() Original publisher: [Read original article]() Author: George Michaelson Published: 2026-09-09T05:10:54Z Content type: opinion Language: en Sources: [APNIC Blog]() Topics: [Pi-hole](), [Resilience](), [Network Configuration](), [systems](), [Server]() Tags: [dns](), [infrastructure](), [network](), [resilience](), [router](), [self-hosted](), [server](), [systems](), [tech-matters]() ### AI overview The article reflects on the difficulties of running resilient self-hosted DNS services at home. It describes how reboots and router or DNS configuration changes can disrupt DHCP and the wider home network, arguing for independently configured redundant instances and a tested backup plan. ### Source excerpt Resiliency through more redundancy is important no matter the scenario. ## I Tested the Best Wi-Fi Adapters for Raspberry Pi DevFeed: [I Tested the Best Wi-Fi Adapters for Raspberry Pi]() Original publisher: [Read original article]() Author: Patrick Fromaget Published: 2026-09-05T05:00:00Z Content type: comparison Language: en Sources: [RaspberryTips]() Topics: [Hardware](), [USB](), [Linux]() Tags: [comparison](), [cost](), [hardware](), [inspiration](), [linux](), [raspberry-pi](), [raspberry-pi-5](), [router](), [speed]() ### AI overview A hands-on comparison of USB Wi-Fi adapters for Raspberry Pi, evaluating speed, signal strength, stability, Linux support, cost, and bulk against the Raspberry Pi 5's built-in Wi-Fi. The article highlights the BrosTrend AXE3000 as the best overall option, the TP-Link Archer T3U Plus as the best value, and notes that Raspberry Pi 5 users may not need an external adapter. ### Source excerpt Over the years, I've mostly used the default Wi-Fi on my Raspberry Pis, and it's good enough for most projects. But when you start putting the Pi in a case, moving it from the router, or using a fancy Wi-Fi access point that can handle faster speeds, it makes sense to look into better solutions.... ## When Traceroutes Lie: How TTL Jumps Can Give Us a False Impression of the Internet's Topology DevFeed: [When Traceroutes Lie: How TTL Jumps Can Give Us a False Impression of the Internet's Topology]() Original publisher: [Read original article]() Author: Sebastian Kappes Published: 2026-09-03T12:03:26Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Networks](), [debugging]() Tags: [atlas](), [competition](), [debugging](), [internet](), [measurements](), [networks](), [research](), [router]() ### AI overview This article explains how routers that rewrite or fail to decrement TTL values can cause traceroute to omit entire networks and create a false impression of Internet topology. It describes the normal traceroute mechanism and measurements using RIPE Atlas probes to investigate the behavior. ### Source excerpt Traceroute is a powerful tool for uncovering how packets travel across the Internet. However, as we recently discovered, some routers tamper with the TTL values in traceroute's probing packets, giving you a false view of how networks are actually interconnected. ## BGP-Free Core with SR-MPLS DevFeed: [BGP-Free Core with SR-MPLS]() Original publisher: [Read original article]() Published: 2026-09-03T05:30:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [BGP](), [networking](), [Network](), [Routing (disambiguation)](), [Containers](), [Linux](), [GitHub]() Tags: [bgp](), [containers](), [edge](), [examples](), [github](), [is-is](), [linux](), [mpls](), [netlab](), [network](), [router](), [routing](), [sr-mpls]() ### AI overview This article demonstrates how to build a BGP-free transport core with SR-MPLS using netlab. It describes a lab topology with IS-IS, BGP, Linux container hosts, and PE routers, then shows how SR-MPLS labels provide end-to-end connectivity without BGP routes on the core router. ### Source excerpt The beauty of SR-MPLS is that it's a drop-in replacement for the traditional (LDP- or RSVP-based) MPLS control plane. For example, you could replace LDP with SR-MPLS in a network using MPLS to implement a BGP-free transport core, and it just keeps working. This scenario was the first "fun" scenario in the ITNOG10 Segment Routing workshop. The core network uses the same topology as in the previous examples; I added two hosts and BGP routing. Simplest possible network using a BGP-free core Read more ... ## I replaced my DNS resolver and the smart home finally shut up DevFeed: [I replaced my DNS resolver and the smart home finally shut up]() Original publisher: [Read original article]() Author: Shed Stack Published: 2026-08-29T15:00:00Z Content type: article Language: en Sources: [Shed Stack]() Topics: [Internet of things](), [Network](), [Pi-hole](), [telemetry]() Tags: [apps](), [devices](), [dns](), [internet](), [local](), [network](), [router](), [smart-home](), [telemetry]() ### AI overview The article describes replacing Pi-hole with AdGuard Home, using device-level DNS rules and VLAN isolation to reduce telemetry from nearly 100 smart-home devices. It also notes maintenance costs, including occasional false blocks, app issues, and manual DNS configuration. ### Source excerpt AdGuard Home and some strict VLANs quieted almost 100 internet connected devices that all wanted to phone home. ## UniFi Travel Router Long-Range (UTR-LR): $99 Travel Router Released DevFeed: [UniFi Travel Router Long-Range (UTR-LR): $99 Travel Router Released]() Original publisher: [Read original article]() Author: Rob Andrews Published: 2026-08-28T13:29:56Z Content type: news Language: en Sources: [NAS Compares]() Topics: [UniFi Travel Router](), [Internet](), [Network]() Tags: [10-dbi-antenna](), [2x2-mimo](), [4-dbi-antenna](), [5g-tethering](), [amneziawg](), [antenna-gain](), [business-travel-tech](), [captive-portal](), [digital-nomad-gear](), [directional-antenna](), [dual-band-wifi](), [ethernet-uplink](), [existing](), [external-antenna](), [firewall](), [geo-based-policy](), [gigabit-ethernet](), [high-gain-antenna](), [hinged-antenna](), [hotel](), [hotel-wifi](), [internet](), [internet-latency-reporting](), [lcm-display](), [location-aware-policies](), [long-range-travel-router](), [mobile-networking](), [multi-uplink](), [network](), [network-cloning](), [networking](), [office](), [on-site-deployments](), [openvpn-client](), [property](), [router](), [travel](), [uncategorised](), [unifi](), [unifi-travel-router]() ### AI overview The UniFi Travel Router Long-Range (UTR-LR) is a compact $99 travel router for creating a private, managed network on shared hotel, rental property, office, or other internet connections. It joins the existing $79 UniFi Travel Router rather than replacing it. ### Source excerpt What is the UniFi Travel Router LR? The UniFi Travel Router Long-Range, or UTR-LR, is a compact $99 travel router designed to provide a private, managed network when using hotel, rental property, office or other shared internet connections. It joins the existing $79 UniFi Travel Router rather than replacing it, retaining the same general platform [...] ## GL.iNet Mango 2 (GL-MG1300) pocket travel router revealed DevFeed: [GL.iNet Mango 2 (GL-MG1300) pocket travel router revealed]() Original publisher: [Read original article]() Author: Rob Andrews Published: 2026-08-24T14:56:26Z Content type: article Language: en Sources: [NAS Compares]() Topics: [GL.iNet](), [GL.iNet Mango 2](), [GL-MG1300]() Tags: [compact-router](), [dual-band-travel-router](), [gigabit-travel-router](), [gl-inet](), [gl-inet-mango](), [gl-inet-mango-2](), [gl-inet-news](), [gl-inet-travel-router](), [gl-mg1300](), [hotel-wi-fi-router](), [ifa-2026](), [mango-2](), [mango-2-travel-router](), [mango-2-vs-unifi-travel-router](), [mango-router](), [mango-vs-mango-2](), [mini-travel-router](), [networking](), [networking-hardware](), [openvpn-router](), [openwrt-router](), [openwrt-travel-router](), [portable-router](), [portable-wi-fi-router](), [router](), [tailscale-router](), [travel](), [travel-router-comparison](), [travel-router-news](), [ubiquiti-utr](), [uncategorised](), [unifi-travel-router](), [usb-tethering-router](), [vpn-travel-router]() ### AI overview The article introduces the newly revealed GL.iNet Mango 2, also identified as the GL-MG1300. It describes the device as a small, relatively affordable pocket travel router that takes a simpler approach than GL.iNet's more powerful, expensive, and larger recent models. ### Source excerpt A New Pocket Travel Router on the way - The Mango 2 Revealed I have followed GL.iNet's travel routers for years, but many of its recent models have become increasingly powerful, expensive and physically larger. The newly revealed Mango 2 (GL-MG1300) takes the opposite approach, returning to the small and relatively affordable format of the [...] ## BGP Role model: tracking the adoption of RFC 9234 DevFeed: [BGP Role model: tracking the adoption of RFC 9234]() Original publisher: [Read original article]() Author: Mingwei Zhang Published: 2026-08-18T15:21:32Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [BGP](), [networking](), [Networks](), [Routing (disambiguation)](), [Protocol (disambiguation)](), [Cloudflare](), [Monitoring]() Tags: [analysis](), [bgp](), [cloudflare](), [internet](), [monitoring](), [network](), [networks](), [research](), [router](), [routing](), [routing-security](), [rpki]() ### AI overview This article examines the adoption of RFC 9234, which uses BGP Roles and the Only to Customer (OTC) attribute to help routers prevent and detect route leaks. Cloudflare measured deployment through its global peering presence and found that two large Tier-1 networks were stripping OTC attributes from forwarded routes. ### Source excerpt RFC 9234 lets routers reject route leaks on their own, using BGP Roles and the Only to Customer attribute. We measured who has deployed it, and found two Tier 1 networks unexpectedly stripping OTC. ## Use of VRF in dual WAN setup DevFeed: [Use of VRF in dual WAN setup]() Original publisher: [Read original article]() Published: 2026-08-03T20:58:23Z Content type: tutorial Language: en Sources: [Personal blog of Anurag Bhatia]() Topics: [networking](), [MikroTik](), [Prometheus](), [Containers]() Tags: [containers](), [mikrotik](), [prometheus](), [router](), [routing](), [routing-table](), [vrf]() ### AI overview This article describes migrating a MikroTik home router from multiple routing tables to a VRF-based dual-WAN design. It explains how shared routing domains caused router-bound traffic to return through the wrong ISP during partial outages and made ISP-specific routing for measurement containers difficult. VRFs provide separate layer-3 routing domains for the WAN links, while Prometheus and Semaphore handle packet-loss-based switchover. ### Source excerpt Over the weekend I migrated my home router from multiple routing tables to a VRF-based design, placing each WAN uplink into its own VRF. While multiple routing tables worked for basic policy routing, they have some limitations and that led to several edge cases that became increasingly difficult to work around. Issues with the setup: If the active default route pointed to ISP1, traffic arriving on ISP1 naturally returned via ISP1. However, traffic terminating on the router and arriving via ISP2 would also be replied to through ISP1, since both uplinks still shared the same routing domain. This did not cause issues for traffic on devices below the router but was bad for traffic terminating on the router interface itself. Due to the above reason, I recently lost access to my home router while I was out of the country because ISP1 had a partial outage (their transit went down, peering stayed up) & due to distributed tooling, the auto switch trigger could not happen either to take care of it. Packets from ISP 2 were being returned via the ISP1 route & thus blackholed. I have a special case where I want most of the devices on a redundant setup but some devices (containers) on specific ISP only. These are measurement containers running blackbox exporter behind a specific ISP as well as RIPE Atlas. I don't want these to switch over for accuracy of measurement. Without VRF it was ugly config-wise, as ISP1 failure will lead to ISP2 routing even when the specific routing table did not have that route. Old Setup My old setup was running multiple routing table pairs: ISP1 only & ISP1 as primary (ISP2 as secondary) ISP2 only & ISP2 as primary (ISP1 as secondary) All WAN interfaces, LAN interfaces and routing tables were in the same single "Main" VRF. This by default takes care of full outage events, fibre cuts, etc. For packet loss-based switchover, I have set up Prometheus + Semaphore as covered in this post last year. Understanding VRF VRF is Virtual Routing and Forwarding. It ## Make scalable routing system for your Flutter Apps DevFeed: [Make scalable routing system for your Flutter Apps]() Original publisher: [Read original article]() Author: Kanan Yusubov Published: 2026-07-29T15:25:43Z Content type: tutorial Language: en Sources: [Flutter Community - Medium]() Topics: [Flutter](), [Routing (disambiguation)](), [navigation](), [modules](), [Dependency injection](), [Usability]() Tags: [clean-architecture](), [dependency-injection](), [flutter](), [go-router](), [modular-router](), [modules](), [navigation](), [router](), [routing](), [routing-system](), [usability]() ### AI overview This tutorial describes a scalable, decoupled routing system for Flutter apps. It explains a wrapper built on go_router that adds typed route arguments, native and path parameters, cross-module modularization, nested routes, presentation modes, and type-safe route guards. ### Source excerpt Recently, I've been working on migrating our app's routing system. We previously used auto_route, but eventually realized its tightly coupled nature made it incredibly difficult to scale across independent modules. Furthermore, its heavy reliance on code generation became a bottleneck for our workflow. To resolve this, we decided to architect a clean, scalable, and highly decoupled routing system. Our new solution is a powerful wrapper built on top of go_router. It abstracts away the raw string navigation and supercharges the router with custom features to maximize usability and type safety. In this blog post, I will walk you through the core benefits of this new routing system, covering the following key topics: Unified Routing Protocol (AppRouteInfo) Strictly Typed Route Arguments Native & Path Parameters Support Cross-Module Modularization (AppModuleRouter) Hierarchical Back stack & Sub-Routes (Nested Route Definitions, Decoupled Cross-Module Navigation) Dynamic Presentation Modes (e.g., Native, ModalSheet, NoTransition) Guard Interceptor Mechanism (Type-Safe Redirects, Global Interceptors) Note: This blog will show the general usage and problems it solved. For more detailed code, you can check the following link: https://github.com/thisisyusub/scalable-routing-system-demoArchitectural Structure of Routing System Here is how the demo application is structured to achieve a fully decoupled, scalable routing system: scalable_routing_system_demo (main app): The entry point of the application responsible for wiring up all services, dependency injection, and global route configurations. app_routes: Houses all route definitions, parameters, routing protocols, and models to ensure fully type-safe navigation. This is decoupled from the core routing package to separate app-specific business needs from generic routing mechanics. routing_system (core router): A generic, domain-agnostic router package that has zero knowledge of the app's specific routes. It exclusively provid ## What's new in Graph Artifacts DevFeed: [What's new in Graph Artifacts]() Original publisher: [Read original article]() Author: Zack Warnimont Published: 2026-07-27T09:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [Platform API](), [Deployment](), [Command-line interface](), [Containers](), [CI/CD]() Tags: [announcement](), [api](), [apis](), [ci-cd](), [cli](), [container-registry](), [deployment](), [graphos](), [oci](), [registry](), [release](), [router]() ### AI overview This release adds GraphOS artifact tag management across Rover and Studio. Teams can assign, list, fetch, and delete tags from Rover, view tags alongside artifact digests in Studio, and use OCI-compliant registry APIs. User-managed tags support promotion and rollback workflows, while tag reassignment hot-reloads automatically on Router v2.11.0 and later. ### Source excerpt When we launched Graph Artifacts, we gave teams a way to pin their GraphOS Router to a specific, immutable supergraph schema version using SHA digests. Graph artifacts are stored using OCI-compliant registries, and tagging is a native concept at that layer. A tag is just a mutable pointer to an immutable digest. In principle, nothing stopped a team from tagging an artifact prod and having their router resolve it. ## How to build a contact form with SendGrid email delivery on Webflow Cloud DevFeed: [How to build a contact form with SendGrid email delivery on Webflow Cloud]() Original publisher: [Read original article]() Author: Ismail Ajagbe Published: 2026-07-26T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [webflow](), [Next.js](), [React](), [App](), [Routing (disambiguation)](), [Server](), [Streams](), [configuration](), [Deployment](), [Web Development](), [Command-line interface]() Tags: [code](), [development](), [guide](), [guides](), [how-to](), [html](), [router](), [routing](), [server](), [validation](), [webflow]() ### AI overview This guide explains how to build a Webflow Cloud contact form using a React component, a Next.js App Router route handler, server-side validation, honeypot bot filtering, CORS configuration, and SendGrid for confirmation and team notification emails. ### Source excerpt Learn how to build a contact form on Webflow Cloud that sends confirmation and notification emails via SendGrid. ## Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes DevFeed: [Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-24T16:28:00Z Content type: article Language: en Sources: [Justin Wilson (j2sw)]() Topics: [BGP](), [networking](), [Routing (disambiguation)](), [Internet](), [gateway](), [Networks]() Tags: [bgp](), [cpu](), [flexibility](), [internet-architecture](), [isp](), [memory](), [network-engineering](), [network-operations](), [route](), [router](), [routing](), [routing-policy](), [routing-table](), [traffic-engineering](), [visibility]() ### AI overview This article explains BGP route choices, comparing default routes, full routes, partial routes, and customer routes. It describes the tradeoffs between small routing tables, Internet visibility, traffic engineering control, and router resource requirements. ### Source excerpt 5 minute read time.Justin Wilson j2sw.com When you configure a BGP session, one of the first questions is what routes you actually want to receive. If you have ever filled out a questionnaire with Hurricane Electric or another transit provider, they ask you what "kind" of routes you want. In this article, I plan to ... Read more The post Understanding BGP Route Types: Full Routes vs Partial vs Default vs Customer Routes appeared first on Justin Wilson (j2sw). ## What Is IPoE? DevFeed: [What Is IPoE?]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-24T12:15:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [DHCP](), [Ethernet](), [Networks](), [Protocol (disambiguation)](), [gateway]() Tags: [broadband](), [dhcp](), [dns](), [ethernet](), [ipoe](), [mtu](), [network-operations](), [pppoe](), [router](), [vlan]() ### AI overview This article explains IPoE, or IP over Ethernet, as an access model in which a customer router uses DHCP to obtain an IP address and network configuration directly, without establishing a PPPoE session or storing login credentials. It describes DHCP relay and Broadband Network Gateway processing and outlines subscriber-identification methods such as VLANs, access ports, DHCP Option 82, circuit identifiers, ONT details, and MAC authentication. ### Source excerpt 4 minutes read time.Many of us ISP veterans are familiar with Point-to-Point Protocol over Ethernet (PPPoE), also referred to as Triple P O E. PPPoE is showing its age. It showed its age 15 years ago. DHCP was the simple fix for modern networks. It had less overhead and was simple. Now along comes IPoE. ... Read more The post What Is IPoE? appeared first on Justin Wilson (j2sw). ## Adding a backup Internet WAN on my OPNsense Router DevFeed: [Adding a backup Internet WAN on my OPNsense Router]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-07-23T21:00:00Z Content type: tutorial Language: en Sources: [Jeff Geerling]() Topics: [Firewall](), [networking](), [configuration](), [5G](), [Software]() Tags: [5g](), [backup](), [ethernet](), [firewall](), [internet](), [networking](), [opnsense](), [outage](), [router]() ### AI overview A practical guide to adding a portable 5G gateway as a backup WAN on an OPNsense router. It covers assigning a second Ethernet interface, configuring DHCP and outbound NAT, and manually changing gateway priorities to fail over between connections. ### Source excerpt AKA "Spectrum has gone down two weeks in a row and I'm sick of it". I've been borrowing a portable 5G gateway from my Dad for a few weeks, for testing... and two weeks in a row, I've used it as a backup Internet option, since my Spectrum Business cable Internet has gone down. And yes, I'd get AT&T Fiber if I had the option, sadly they don't yet provide service at my studio. So I'm stuck with only one high speed wired provider. I may add on my own 5G backup Internet connection in the future, but we're getting off track. ## How Passive Optical Networks (PON) Work DevFeed: [How Passive Optical Networks (PON) Work]() Original publisher: [Read original article]() Author: j2sw Published: 2026-07-22T12:35:00Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [Networks](), [gpon](), [Internet](), [Ethernet](), [gateway](), [Security](), [Deployment]() Tags: [ethernet](), [fiber](), [ftth](), [gateway](), [gpon](), [internet](), [internet-architecture](), [isp](), [networks](), [passive-optical-network](), [pon](), [providers](), [provisioning](), [router](), [security](), [xgs-pon]() ### AI overview This tutorial explains how Passive Optical Networks (PON) deliver residential fiber Internet. It describes the roles of the OLT, passive optical splitters, ONTs, and the customer router or gateway, including how providers share feeder fiber among subscribers and provision authorized ONTs. ### Source excerpt If you've spent any time looking into fiber Internet, you've probably run across terms like GPON, XGS-PON, OLT, and ONT. These are all parts of what's called a Passive Optical Network, or PON. Most residential fiber providers use PON because it lets them connect alot of homes without having to pull a separate fiber from ... Read more The post How Passive Optical Networks (PON) Work appeared first on Justin Wilson (j2sw). ## Apollo's New API IP Allowlist Policy DevFeed: [Apollo's New API IP Allowlist Policy]() Original publisher: [Read original article]() Author: David Glasser Published: 2026-07-15T12:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphOS](), [API](), [Firewall](), [gateway](), [Network](), [configuration]() Tags: [announcement](), [api](), [configuration](), [firewall](), [gateway](), [graphos](), [infrastructure](), [installation](), [network](), [operational](), [published](), [router](), [schema](), [trust-center]() ### AI overview Apollo has published an API IP Allowlist Policy for GraphOS Router and Apollo Gateway deployments that restrict outbound access by IP address. The policy covers Apollo Uplink endpoints, documents their current IP addresses, and promises at least 60 days' notice before adding new IPs. Apollo also plans to add a second IP per covered service no earlier than September 16, 2026. ### Source excerpt Restricting outbound traffic by IP? GraphOS Router now needs a second Uplink IP allowlisted before September 16, 2026. See what Apollo's new policy covers. ## netlab 26.07: GRE, Wireguard, Graceful Restart, and Scale-Out Labs DevFeed: [netlab 26.07: GRE, Wireguard, Graceful Restart, and Scale-Out Labs]() Original publisher: [Read original article]() Published: 2026-07-13T06:23:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [releases](), [BGP](), [Server](), [evpn](), [VXLAN](), [configuration](), [GitHub]() Tags: [bgp](), [configuration](), [evpn](), [getting-started](), [github](), [gre](), [guide](), [installation](), [netlab](), [ospf](), [policy](), [release](), [releases](), [router](), [upgrade](), [vxlan]() ### AI overview The netlab 26.07 release adds scale-out labs through a multiserver plugin, GRE and WireGuard tunnel support, graceful restart capabilities, BGP policy roles, and expanded BIRD, FortiOS, MikroTik RouterOS, and OpenBSD functionality. It also removes the VirtualBox provider, makes BIRD v3 the default, and changes MikroTik RouterOS 7 BGP template syntax. ### Source excerpt The highlights of netlab release 26.07 include: The multiserver plugin by @muddyblack distributes containerlab devices across multiple servers. The GRE tunnel plugin supports GRE tunnels on Cisco IOS, FRR, VyOS, and Junos (vSRX and vJunos-router) (most device implementations done by @ssasso and @jbemmel). The WireGuard tunnel plugin by @jbemmel supports WireGuard tunnels on FRR. The bgp.session plugin and the OSPF module support graceful restart on Arista EOS, BIRD, FortiOS, and FRR (by @jbemmel and @a-v-popov) The bgp.policy plugin supports the bgp.role attribute on FRR and BIRD (by @jbemmel). But wait, there's more ;) Read more ... ## DigitalOcean Evaluations: Production Model and Router Testing for the Inference Stack DevFeed: [DigitalOcean Evaluations: Production Model and Router Testing for the Inference Stack]() Original publisher: [Read original article]() Author: Grace Morgan Published: 2026-07-01T15:41:47Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [inference-endpoints](), [Large Language Model](), [model-deployment](), [Testing]() Tags: [configuration](), [cost](), [data](), [dataset](), [digitalocean](), [evaluation](), [inference](), [inference-endpoints](), [latency](), [llm](), [metric](), [model](), [models](), [performance](), [pii](), [product-updates](), [production](), [quality](), [router](), [testing](), [token]() ### AI overview DigitalOcean Evaluations adds production testing for models and inference router configurations in the DigitalOcean Inference Engine. Teams can run LLM-as-a-Judge evaluations on their own prompts and data, compare quality, latency, and cost, and use built-in or custom rubrics across models, imports, and router setups. ### Source excerpt Choosing the right model or inference router for production means more than reading a leaderboard. It means validating any model or routing configuration on your own data using your prompts and your evaluation criteria before it ever reaches production, and comparing quality, latency, and cost in one place. Evaluations, now available on the DigitalOcean Inference Engine, lets teams validate any model or inference router configuration on their own data before production. Run structured LLM-as-a-Judge evaluations across catalog models, fine-tuned models, BYOM imports, and router setups without stitching together a separate evaluation stack. DigitalOcean Evaluations Capabilities Evaluations provide everything teams need to validate model and router performance before production. LLM-as-a-Judge scoring runs across any candidate in your inference stack and returns per-item scores with judge rationale, plus latency, token, and cost tracking per run. Six pre-built metrics cover the most common evaluation needs out of the box. For teams that need full control: custom rubrics, reusable presets, MCP support, and full dataset management -- all in the same platform as the inference endpoints you use in production. View YouTube video Pre-Built and Custom Rubrics: Score Against Criteria That Match Your Domain The six pre-built metrics, correctness, completeness, faithfulness, PII, toxicity, and bias, cover common evaluation needs. For specialized domains, custom rubrics let teams define their own judge instructions and scoring criteria directly in the judge prompt. The judge evaluates responses against these criteria and returns per-item scores with rationale. Custom rubrics can also adapt the built-in correctness metric to different data formats instead of relying on a default interpretation. Evaluation Presets: Save Configurations and Re-Run Without Rebuilding Without saved configurations, every re-run becomes a rebuild with different judge models, parameters, or prompts, making ## LLM router architecture: best practices for 2026 DevFeed: [LLM router architecture: best practices for 2026]() Original publisher: [Read original article]() Author: Jim Allen Wallace Published: 2026-07-01T00:00:00Z Content type: tutorial Language: en Sources: [Redis Blog]() Topics: [Model Routing](), [LLMs](), [Latency](), [Availability](), [API](), [networking]() Tags: [architecture](), [availability](), [best-practices](), [cost](), [latency](), [llm](), [outage](), [router](), [routing](), [tech-de]() ### AI overview This guide explains model routers as middleware that selects the most suitable large language model for each request based on factors such as task complexity, cost, latency, availability, load, and safety requirements. It covers common routing strategies, production architecture patterns, proxy and recommendation-based designs, and how routing can reduce costs and improve reliability through fallback handling. ### Source excerpt You picked GPT-5 for every LLM call in your app because it was the safe call: chat, autocomplete, classification, summarization, all of it. Then the bill arrived, and you traced part of it back to queries like "what are your business hours?" getting r... ## Sam's First Visit to An Internet Exchange DevFeed: [Sam's First Visit to An Internet Exchange]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-25T03:54:15Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [networking](), [Networks](), [Internet Traffic](), [BGP]() Tags: [bgp](), [book](), [books](), [children](), [explainer](), [fiber](), [internet](), [internet-architecture](), [internet-exchange](), [internet-traffic](), [ix](), [ixp](), [j2-updates](), [j2sw](), [justin-wilson](), [network-engineering-resources](), [networking](), [networks](), [peering](), [router](), [sam](), [stem-book](), [traffic]() ### AI overview Justin Wilson announces A Kid's First Visit to An Internet Exchange, a children's picture book in which Sam learns how networks connect, peer, and move Internet traffic. The book is available in Kindle and paperback editions. ### Source excerpt Justin Wilson announces his second children's networking book, A Kid's First Visit to an Internet Exchange. Follow Sam as he learns how networks meet, peer, and move Internet traffic. The post Sam's First Visit to An Internet Exchange appeared first on Justin Wilson (j2sw). [Next page]()