# Network Configuration Configuration of a computing system's network interfaces and related DNS, routing, and host settings. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Secure Compute and Static IP builds start 64% faster DevFeed: [Secure Compute and Static IP builds start 64% faster]() Original publisher: [Read original article]() Author: Karim Hasebou Published: 2026-09-16T17:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Deployment](), [Containers](), [Network Configuration]() Tags: [automatically](), [build](), [compute](), [containers](), [faster](), [ip](), [network-configuration](), [static]() ### AI overview Vercel reports that builds using Secure Compute or Static IPs now start 64% faster on average, improving from 6.7 seconds to 2.4 seconds. The change uses prewarmed build containers with network configuration attached at build start and requires no configuration changes. ### Source excerpt Builds using Secure Compute or Static IPs now start 64% faster, with the average time from deployment creation to build start dropping from 6.7 seconds to 2.4 seconds. Previously, each build waited for a new build container to boot with its network configuration. These builds now use prewarmed build containers, with your network configuration attached when the build starts. The improvement is applied automatically to builds using Secure Compute or Static IPs, with no configuration changes required. Learn more about Secure Compute and Static IPs. Read more ## 8 Reasons Your Raspberry Pi Wi-Fi is Slow (and How to Fix it) DevFeed: [8 Reasons Your Raspberry Pi Wi-Fi is Slow (and How to Fix it)]() Original publisher: [Read original article]() Author: Thomas Dyan Published: 2026-09-12T05:00:00Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Network](), [Network Configuration](), [Linux](), [Command-line interface](), [ssh](), [Terminal](), [Operating system]() Tags: [command-line](), [how-to](), [how-to-tutorials](), [linux](), [network](), [network-configuration](), [raspberry-pi](), [raspberry-pi-os](), [ssh](), [time]() ### AI overview A practical guide to diagnosing and fixing slow Raspberry Pi Wi-Fi. It focuses on common causes such as Wi-Fi power-saving settings, weak signal, incorrect country code, older hardware, and network configuration issues, with initial troubleshooting steps and command-line guidance. ### Source excerpt Whenever my Raspberry Pi is slow over Wi-Fi, I've learned that the problem is usually not the Wi-Fi network itself. Most of the time, it comes down to the Pi's setup. And when you look into it, it's often one of the same few causes. If you're having the same issue, here are the first... ## 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. ## Netpicker AI Assistant: AI-Assisted Network Operations and Compliance DevFeed: [Netpicker AI Assistant: AI-Assisted Network Operations and Compliance]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-09-03T12:27:49Z Content type: article Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [Artificial Intelligence](), [Network](), [Network Configuration](), [network security](), [configuration](), [incident](), [Testing]() Tags: [ai](), [blog](), [configuration-management](), [incident](), [network](), [network-configuration](), [network-security](), [testing]() ### AI overview The article explains how Netpicker's AI Assistant connects natural-language interaction with network data and operational capabilities such as configuration backups, compliance results, CVE information, device state, and automation jobs. It describes use cases for network troubleshooting, security operations, and configuration management, including investigating recent configuration changes during incidents. ### Source excerpt Introduction The real value is not in asking a model how BGP works or how to configure a VLAN. It comes from connecting AI to the tools and data we already use to operate the network, including configuration backups, compliance results, CVE data, device state and automation jobs. This is ## How to Install and Use No-IP on Raspberry Pi? (Dynamic DNS) DevFeed: [How to Install and Use No-IP on Raspberry Pi? (Dynamic DNS)]() Original publisher: [Read original article]() Author: Patrick Fromaget Published: 2026-07-23T03:34:36Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Network Configuration](), [Homelab](), [Linux](), [Server](), [Web](), [hosting]() Tags: [article](), [dns](), [home-server](), [hosting](), [how-to](), [how-to-tutorials](), [internet](), [linux](), [raspberry-pi](), [server](), [ssh](), [tutorial](), [web]() ### AI overview This tutorial explains how to install and use No-IP dynamic DNS on a Raspberry Pi. It covers linking a hostname to a changing public IP address so Raspberry Pi and self-hosted services can be accessed remotely, along with an overview of No-IP pricing plans and limitations. ### Source excerpt If, like me, your Internet connection doesn't have a static public IP address, or if you want an easy-to-remember domain for accessing (or sharing) your services, this article is for you. Using No-IP and a Raspberry Pi, we can associate a hostname with our current IP address (and keep it updated when it changes). Today,... ## Vercel Services: Run full stack on Vercel DevFeed: [Vercel Services: Run full stack on Vercel]() Original publisher: [Read original article]() Author: Joe Haddad Published: 2026-06-30T04:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [Deployment](), [FastAPI](), [Next.js](), [Developer experience](), [Routing (disambiguation)](), [JavaScript](), [Network Configuration](), [Python]() Tags: [cli](), [configuration](), [deployment](), [developer-experience](), [infrastructure](), [next-js](), [rest](), [routing](), [vercel]() ### AI overview Vercel Services is introduced in public beta as a way to run multiple frameworks in one Vercel Project. It supports coordinated deployments and previews, internal service communication, shared routing, service bindings, centralized logs, and local multi-service development for full-stack applications. ### Source excerpt To a user, an app with a Next.js frontend and a FastAPI backend feels like one product, and the same should be true for the engineers who build it. Instead, the two pieces are often deployed across different clouds with different development and deployment workflows. Today we're introducing Vercel Services in public beta, which lets you run multiple frameworks in one Vercel Project. This unlocks: Atomic deployments: Your frontend, backend, and other services stay in sync and deploy or roll back together Shared preview deployments: See how any change affects all your services Internal service communication: Services can talk to each other without routing through the public Internet Vercel handles the rest: routing, builds, deployments, and auto-scaling in production. The developer experience you already know from Vercel now covers your entire application. Compose applications with Vercel Services Declare your services under the services key in vercel.json keeping the routing configuration explicit: Services can be mounted to a shared routing table without the need for a reverse proxy or CORS. The services configuration is recognized at multiple levels of the Vercel platform: The Deployments panel shows a visualization of services graph The Logs UI allows filtering by individual service The vercel dev CLI automatically runs all services giving you a production-like environment locally Service bindings Services can talk to other services internally, without routing through the public Internet. Here's an example how the new bindings configuration key enables that: Now the JavaScript frontend code can talk to the Python service internally via the URL stored in the BACKEND_INTERNAL_URL environment variable: Service-to-service traffic stays on the Vercel network rather than egressing to the public internet. Many independent services can become one application connected by the same wiring, rather than separate deployments that you stitch together across hosts. Framework-def ## Vercel CLI now supports verifying DNS configuration DevFeed: [Vercel CLI now supports verifying DNS configuration]() Original publisher: [Read original article]() Author: Elliot Dauber Published: 2026-06-23T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Command-line interface](), [Network Configuration](), [Vercel](), [DNSSEC](), [ci](), [Automation](), [JSON]() Tags: [automation](), [ci](), [cli](), [dns](), [dnssec](), [json](), [vercel](), [verify]() ### AI overview Vercel CLI now includes the `vercel domains verify` command for diagnosing DNS configuration. It checks ownership, DNS records, nameservers, DNSSEC, conflicting records, and project attachment, provides corrective guidance, and supports JSON output, project scoping, exact matching, non-interactive use, CI, and automation. ### Source excerpt You can now use the Vercel CLI to diagnose a domain's DNS configuration. Using the vercel domains verify command, you can check whether a domain is correctly configured, attached to the right project, and verified. If not, it returns the exact steps to fix it. vercel domains verify inspects ownership, DNS records, nameservers, DNSSEC, conflicting records, and project attachment, and tells you precisely what to change. When the domain is correctly configured, you get a single line back: With --format json, the command returns the full diagnosis: status, reason, recommended records, detected conflicts, and suggested next commands. It exits non-zero when misconfigured or unverified, making it scriptable for CI and automation: You can also scope to a project, enforce exact matching, or run non-interactively: Upgrade your Vercel CLI to version 54.15.1 to get started. Learn more in the vercel domains verify documentation. Read more ## How we shipped 15 Tbps for OpenAI in 90 days (Session 1 of 3) DevFeed: [How we shipped 15 Tbps for OpenAI in 90 days (Session 1 of 3)]() Original publisher: [Read original article]() Author: Sridhar Rajarao Published: 2026-06-08T00:00:00Z Content type: article Language: en Sources: [Sridhar Rajarao]() Topics: [cloud-infrastructure](), [Network architectures](), [Network Configuration](), [OpenAI]() Tags: [architecture](), [gpu](), [network](), [network-configuration](), [object-storage](), [openai](), [platform-engineering](), [production](), [region](), [scale](), [service](), [sre](), [storage](), [teams]() ### AI overview Session 1 describes how a team closed the architecture for OpenAI's second Object Storage instance in the same physical region as its primary. The production system was designed for 15 Tbps of GPU-fleet traffic and a three-month delivery timeline, with major architecture decisions completed in one week. ### Source excerpt OpenAI wanted a second Object Storage instance, in customer-facing production, at 15 Tbps, in three months. Session 1 covers the first week: closing the architecture. ## Ansible network configuration modules still fail to process Jinja2 templates DevFeed: [Ansible network configuration modules still fail to process Jinja2 templates]() Original publisher: [Read original article]() Published: 2025-12-16T07:28:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [Network Configuration](), [bug](), [networking]() Tags: [2025](), [ansible](), [bug](), [configuration](), [network-automation](), [networking](), [ubuntu]() ### AI overview The article argues that Ansible's network device configuration modules continued failing to process templated configurations after several releases. It also reports that templated configuration support in the network configuration modules is scheduled to disappear in January 2028, and that netlab now generates device configurations outside Ansible. ### Source excerpt A month ago, I described how Ansible release 12 broke the network device configuration modules, the little engines (that could) that brought us from the dark days of copy-and-paste into the more-survivable land of configuration templates. In the meantime, the Ansible networking team fixed the ansible.netcommon collection, but (according to that PR) the ability to process templated configurations directly in the network configuration modules is scheduled to disappear in January 2028 (more details). I moved on; netlab is now generating device configurations outside of Ansible. Three releases later (they just released 13.1), the same bug is still there (at least it was on a fresh Python virtual environment install I made on a Ubuntu 24.04 server on December 13th, 2025), making all device_config modules unusable (without changing your Ansible playbooks) for configuration templating. Even worse: Read more ... ## Static Routes in netlab Lab Topologies DevFeed: [Static Routes in netlab Lab Topologies]() Original publisher: [Read original article]() Published: 2025-06-23T05:50:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [Routing (disambiguation)](), [Networks](), [Network Configuration](), [configuration]() Tags: [configuration](), [ipv4](), [ipv6](), [netlab](), [networks](), [routing]() ### AI overview This tutorial explains how to define static routes in netlab lab topologies. It describes destination prefixes, next hops, optional VRF information, gateway and discard-route support, and examples using automatically assigned interface addresses. ### Source excerpt As much as we'd love everything in our networks to be dynamic, auto-configured, or software-defined, reality often intervenes and forces us to use static routes, so we needed a mechanism to specify them in netlab lab topologies. A static route has two components: the destination prefix and the next hop - the device that we hope knows how to reach that destination. The next hop is usually specified as an IPv4 or IPv6 address, but may also include outgoing interface information1. Read more ... ## 14 Best Practices to Secure SSH Bastion Host DevFeed: [14 Best Practices to Secure SSH Bastion Host]() Original publisher: [Read original article]() Author: sakshyam.shah@goteleport.com (Sakshyam Shah) Published: 2022-01-13T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Security](), [OpenSSH](), [ssh](), [Server](), [Network Configuration](), [zero trust networking](), [Ubuntu](), [Amazon Web Services]() Tags: [bastion](), [bastion-host](), [best-practices](), [configuration](), [deployment](), [hardening](), [high-availability](), [infrastructure](), [linux](), [lts](), [network](), [network-configuration](), [networking](), [openssh](), [operations](), [security](), [server](), [ssh](), [ubuntu](), [zero-trust-networking]() ### AI overview This tutorial presents 14 best practices for building and deploying a security-hardened SSH bastion host using OpenSSH. It covers reducing the server attack surface, configuring the surrounding network, applying zero trust networking principles, hardening the operating system and authentication, and deploying for high availability. ### Source excerpt Learn 14 best practices to build and deploy a security-hardened SSH bastion host based on OpenSSH server. ## Orange FTTH on a custom router DevFeed: [Orange FTTH on a custom router]() Original publisher: [Read original article]() Author: Marek Published: 2020-08-01T22:00:00Z Content type: tutorial Language: en Sources: [Marek Majkowski]() Topics: [Network Configuration](), [Debian](), [Network](), [Firewall](), [DHCP](), [huawei]() Tags: [debian](), [dhcp](), [firewall](), [ftth](), [huawei](), [interfaces](), [internet](), [iptables](), [ipv4](), [ipv6](), [mikrotik](), [network](), [pppoe](), [router](), [server](), [vlan]() ### AI overview A tutorial describing how to replace Orange's FunBox 3.0 with a custom Debian router for Orange FTTH in Poland. It covers obtaining an ONT and PPPoE credentials, configuring VLAN 35 and PPP, setting up iptables, and providing DHCP for the local network. ### Source excerpt Orange FTTH on a custom router Here in Poland, Orange has a decent FTTH offer - less than $16 for 300Mbit down, 50Mbit up. People reversed it over the years, most impressively Pierre Kim in 2016: Recently, it has been possible to replace the router the provider gives, called "FunBox 3.0", with a custom one. There are couple of reasons for that: - My understanding it's impossible to get a stable IPv6 on FunBox 3. - FunBox is proprietary and evil. ## What the interns have wrought, 2019 edition DevFeed: [What the interns have wrought, 2019 edition]() Original publisher: [Read original article]() Author: Yaron Minsky Published: 2019-08-30T00:00:00Z Content type: article Language: en Sources: [Jane Street]() Topics: [data](), [Latency](), [OCaml](), [systems](), [JavaScript](), [Neovim](), [Network Configuration](), [Library](), [web applications]() Tags: [analysis](), [data](), [intern](), [internship](), [javascript](), [latency](), [library](), [network-configuration](), [ocaml](), [web](), [web-applications]() ### AI overview Jane Street reviews selected projects completed by its 2019 interns, including latviz, a tool for visualizing latency data, vcaml, an OCaml layer for extending Neovim, and an LDAP library implementation. ### Source excerpt Jane Street's intern program yet again is coming to an end, which is a nice opportunity to look back over the summer and see what they've accomplished. ## HomeKit on Espressif's ESP32 DevFeed: [HomeKit on Espressif's ESP32]() Original publisher: [Read original article]() Author: John Lee Published: 2019-02-10T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Espressif](), [SDK](), [SDKs](), [Internet of things](), [API](), [Network Configuration](), [configuration]() Tags: [api](), [blog](), [esp32](), [espressif](), [homekit](), [internet-of-things](), [iot](), [latency](), [network-configuration](), [product-management](), [sdk]() ### AI overview Espressif describes its HomeKit SDK for ESP32-based connected products. The SDK is designed to simplify common tasks such as network configuration, discovery, cloud communication, interoperability, and device control through an API, while remaining extensible for less typical applications. ### Source excerpt IoT is not one thing, it means different things to different people. So also, there are so many ways of building connected products. And that means there are so many questions for every aspect of your connected product: - What communication protocols do we use? - Which network configuration mechanism should we use? - What do we use for remote communication? - What's the most secure method for doing this? - Do we offer low-latency control options through local network access? ## Forge AWS VPC / Subnet Improvements DevFeed: [Forge AWS VPC / Subnet Improvements]() Original publisher: [Read original article]() Author: Taylor Otwell Published: 2018-10-22T16:46:00Z Content type: article Language: en Sources: [Laravel Blog]() Topics: [Amazon Web Services](), [VPC](), [Network Configuration](), [Provisioning](), [Laravel]() Tags: [aws](), [configuration](), [laravel](), [network](), [network-configuration](), [provisioning](), [vpc]() ### AI overview Laravel Forge now lets users choose the subnet for AWS servers during provisioning, providing greater control over network configuration. It also supports creating additional VPCs when creating servers. ### Source excerpt Beginning today, Forge now allows you to select the subnet that AWS servers should be place in when provisioning. This feature gives you more control over the network configuration of your Forge AWS servers. ## Espressif's Alexa SDK v1.0b1! DevFeed: [Espressif's Alexa SDK v1.0b1!]() Original publisher: [Read original article]() Author: John Lee Published: 2018-09-24T00:00:00Z Content type: release Language: en Sources: [Blog on Developer Portal]() Topics: [SDKs](), [Espressif](), [ESP32](), [C](), [Android](), [Authentication](), [Network Configuration](), [Hardware]() Tags: [alexa](), [amazon](), [android](), [authentication](), [blog](), [c](), [esp32](), [espressif](), [framework](), [hardware](), [iot](), [network-configuration](), [release](), [sdk](), [v1]() ### AI overview Espressif announces the availability of Alexa SDK v1.0b1, a low-footprint C-based SDK for ESP32-LyraT development boards. It supports Alexa conversations, music and audio services, alerts, hands-free operation, and an Android phone app for network configuration and Amazon authentication. ### Source excerpt The Espressif's Alexa SDK v1.0b1 is now available on github here: This is a low-footprint C-based SDK that includes support for all of the following features: - Conversations (Calendar, Shopping, News, Todo, Info, Movies, Sports) - Music/Audio Services : Amazon Prime Music, Audible, Kindle, TuneIn and iHeartRadio - Alerts : Alarms, Timers, Reminders and Notifications Supported Hardware# By default, the SDK supports ESP32-LyraT development boards. ## Production metrics Bitly monitors beyond standard checks DevFeed: [Production metrics Bitly monitors beyond standard checks]() Original publisher: [Read original article]() Author: Wordbitly Published: 2014-01-28T16:11:25Z Content type: article Language: en Sources: [Bitly]() Topics: [Monitoring](), [DevOps](), [systems](), [cURL](), [Network Configuration]() Tags: [curl](), [devops](), [metrics](), [monitoring](), [network-configuration](), [ops](), [process](), [systems]() ### AI overview This Bitly article describes production-monitoring lessons beyond standard disk, memory, load, and ping metrics. The supplied text discusses fork rate, network flow-control packets, swap-in/out rate, server boot notifications, and NTP clock offset, including incidents involving IPv6 configuration, curl, and dropped traffic. ### Source excerpt There is always a set of standard metrics that are universally monitored (Disk Usage, Memory Usage, Load, Pings, etc). Beyond that, there are a lot of lessons that we've learned from operating our production systems that have helped shape the breadth of monitoring that we perform at bitly. One of my favorite all-time tweets is from @DevOps_Borat "Law of Murphy for devops: if thing can able go wrong, is mean is already wrong but you not have Nagios alert of it yet." What follows is a small list of things we monitor at bitly that have grown out of those (sometimes painful!) experiences, and where possible little snippets of the stories behind those instances. 1 - Fork Rate We once had a problem where IPv6 was intentionally disabled on a box via options ipv6 disable=1 and alias ipv6 off in /etc/modprobe.conf. This caused a large issue for us: each time a new curl object was created, modprobe would spawn, checking net-pf-10 to evaluate IPv6 status. This fork bombed the box, and we eventually tracked it down by noticing that the process counter in /proc/stat was increasing by several hundred a second. Normally you would only expect a fork rate of 1-10/sec on a production box with steady traffic. check_fork_rate.sh 2 - flow control packets TL;DR; If your network configuration honors flow control packets and isn't configured to disable them, they can temporarily cause dropped traffic. (If this doesn't sound like an outage, you need your head checked.) $ /usr/sbin/ethtool -S eth0 | grep flow_control rx_flow_control_xon: 0 rx_flow_control_xoff: 0 tx_flow_control_xon: 0 tx_flow_control_xoff: 0 Note: Read this to understand how these flow control frames can cascade to switch-wide loss of connectivity if you use certain Broadcom NIC's. You should also trend these metrics on your switch gear. While at it, watch your dropped frames. 3 - Swap In/Out Rate It's common to check for swap usage above a threshold, but even if you have a small quantity of memory swapped, it's actually th ## Newsletter 49: Network Configuration, Kernel Timing Bugs, and PSEH 2.0 DevFeed: [Newsletter 49: Network Configuration, Kernel Timing Bugs, and PSEH 2.0]() Original publisher: [Read original article]() Published: 2008-11-17T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [Network Configuration](), [bug](), [interfaces](), [Deadlock](), [race-condition]() Tags: [bug](), [deadlock](), [free](), [interfaces](), [network-configuration](), [open-source](), [os](), [race-condition](), [react](), [reactos](), [win32](), [winapi]() ### AI overview This newsletter reports work on ReactOS network configuration, including fixes for a registry-key error that prevented DNS information retrieval and caused application crashes. It also covers kernel timing bugs that could cause a race condition and deadlock, and describes improvements in PSEH 2.0 over version 1.1. ### Source excerpt Network Configuration Johannes Anderwald has been working to fix a persistent bug in the network settings that resulted after he reimplemented the network configuration and settings dialog in netcfgx.dll using COM interfaces. Johannes also had to implement the COM interfaces, since they didn't exist before, and they are now in netshell.dll. Unfortunately, it seems that the dhcpclient was storing settings in the wrong registry key, which resulted in failure to retrieve DNS information and crashing of applications that relied on such information.