# Network Configuration Published articles for Network Configuration. 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... ## 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 ## Engineering the Datadog Agent for FedRAMP High® Certification DevFeed: [Engineering the Datadog Agent for FedRAMP High® Certification]() Original publisher: [Read original article]() Author: Srdjan Grubor; Nathan Baker Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Datadog | The Monitor blog]() Topics: [Cryptography]() Tags: [architecture](), [compliance](), [cryptographic](), [cryptography](), [datadog-agent](), [engineering](), [fedramp](), [go](), [infrastructure](), [logs](), [metrics](), [network-configuration](), [observability](), [python](), [security](), [traces]() ### AI overview The article explains how Datadog engineered its Agent to meet FedRAMP High requirements in customer-managed environments, emphasizing cryptographic enforcement across Go and Python runtimes. ### Source excerpt Datadog achieves GovRAMP High authorization, bringing unified observability and security to state and local government agencies for critical systems. ## 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. ## A Recap on May/June Stability DevFeed: [A Recap on May/June Stability]() Original publisher: [Read original article]() Author: Nikita Shamgunov Published: 2025-07-16T19:54:56Z Content type: article Language: en Sources: [Blog -- Neon Docs]() Topics: [incident](), [networking](), [AI Bots]() Tags: [agentic-ai](), [architecture](), [database](), [engineering](), [incident](), [infrastructure](), [kubernetes](), [network-configuration](), [networking](), [terraform](), [testing]() ### AI overview A Neon stability recap explains how rapid database growth associated with agentic AI platforms exposed Kubernetes and network scaling limits, causing incidents. It outlines a planned horizontally scalable "Cells" architecture intended to prevent similar issues. ### Source excerpt Starting in May, we had a series of feature launches with agentic AI partners that gained far more momentum than we predicted. In two short timespans, the rate of new database creation increased more than 5x, and the rate of branch creation increased more than 50x. While we were... ## Resolving the Reverse Tunnel Remote port forwarding failed for listen port SSH Error DevFeed: [Resolving the Reverse Tunnel Remote port forwarding failed for listen port SSH Error]() Original publisher: [Read original article]() Author: Hiks Gerganov Published: 2025-06-09T04:49:53Z Content type: tutorial Language: en Sources: [Baeldung - Linux]() Topics: [ssh](), [OpenSSH](), [Network](), [Firewall](), [Virtual Private Network](), [Bash](), [Debian](), [Server](), [client](), [Protocol (disambiguation)](), [systems](), [aio]() Tags: [bash](), [debian](), [firewall](), [how-to](), [learn](), [linux](), [network](), [network-configuration](), [network-configuration-network-monitoring-security-ssh](), [remote](), [security](), [server](), [ssh](), [tutorial](), [vpn]() ### AI overview This tutorial explains reverse SSH tunnels, also called SSH remote port forwarding. It covers how they allow a protected client behind NAT, a firewall, a router, or a VPN to expose local services to a remote server, along with prerequisites and common connection problems. ### Source excerpt Learn about reverse SSH tunnels, i.e., SSH port forwarding, and issues that you might encounter when trying to use them. The post Resolving the Reverse Tunnel Remote port forwarding failed for listen port SSH Error first appeared on Baeldung on Linux. Related Stories Sending a Password via SSH or SCP Using subprocess.Popen in Linux What Is SELinux? How To Automatically Connect to a VPN in Linux ## 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. ## 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.