# 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.

## Candidate Configuration on Cisco Nexus OS

DevFeed: [Candidate Configuration on Cisco Nexus OS](<https://devfeed.tech/articles/candidate-configuration-on-cisco-nexus-os-128962.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/11/candidate-active-configuration-nexus-os/>)

Published: 2026-11-11T07:16:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [configuration](<https://devfeed.tech/topics/configuration.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>)

Tags: [2020s](<https://devfeed.tech/tags/2020s.md>), [arista](<https://devfeed.tech/tags/arista.md>), [automation](<https://devfeed.tech/tags/automation.md>), [can](<https://devfeed.tech/tags/can.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-nexus](<https://devfeed.tech/tags/cisco-nexus.md>), [commit](<https://devfeed.tech/tags/commit.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [eos](<https://devfeed.tech/tags/eos.md>), [ios](<https://devfeed.tech/tags/ios.md>), [launch](<https://devfeed.tech/tags/launch.md>), [network](<https://devfeed.tech/tags/network.md>), [nexus](<https://devfeed.tech/tags/nexus.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [os](<https://devfeed.tech/tags/os.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [stage](<https://devfeed.tech/tags/stage.md>)

### AI overview

Cisco Nexus OS 10.6(3)F introduced a candidate configuration that snapshots the running configuration, lets users inspect changes with `show candidate-config diff` or the resulting configuration with `show candidate-config`, and supports commit, abort, and later resumption. The earlier two-stage commit was more limited: it lacked a reported equivalent of `show configuration merge`, worked only in interactive CLI according to the documentation, and allowed only one active session. The newer candidate feature still has feature gaps: on Nexus OS 10.6(4) Maintenance Release, an existing IS-IS configuration caused candidate mode to fail, and `show candidate-config last-unsupported` identified the affected IS-IS commands. The excerpt says OSPF is supported but IS-IS is not.

### Source excerpt

TL&DR: Third time is (supposedly) a charm. Not in this case. It's a bit hard to understand why one would launch an enterprise data-center-grade network operating system without candidate/active configuration in the 21st century, but that's what Cisco and Arista did with Nexus OS and EOS. Arista fixed that omission with configuration sessions more than a decade ago1. It took Cisco a bit longer. The first attempt was the so-called two-stage configuration commit, which is functionally almost identical to the Cisco IOS XR "candidate" configuration: Read more ...

## Tailscale Part 2: Access Your Entire Homelab With Subnet Routing

DevFeed: [Tailscale Part 2: Access Your Entire Homelab With Subnet Routing](<https://devfeed.tech/articles/tailscale-part-2-access-your-entire-homelab-with-subnet-routing-122128.md>)

Original publisher: [Read original article](<https://noted.lol/tailscale-subnet-routing-homelab/>)

Author: Jeremy

Published: 2026-11-07T12:27:19Z

Content type: tutorial

Language: en

Sources: [Noted](<https://devfeed.tech/sources/noted.md>)

Topics: [tailscale](<https://devfeed.tech/topics/tailscale.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [CIDR and subnets](<https://devfeed.tech/topics/cidr-and-subnets.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>)

Tags: [firewall](<https://devfeed.tech/tags/firewall.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [home-network](<https://devfeed.tech/tags/home-network.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [ip](<https://devfeed.tech/tags/ip.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [linux](<https://devfeed.tech/tags/linux.md>), [nas](<https://devfeed.tech/tags/nas.md>), [routing](<https://devfeed.tech/tags/routing.md>), [subnet](<https://devfeed.tech/tags/subnet.md>), [tailscale](<https://devfeed.tech/tags/tailscale.md>)

### AI overview

Tailscale subnet routing lets one always-on Tailscale-connected Linux server act as a gateway to homelab devices that do not run Tailscale, using their existing local IP addresses. Enable Linux IP forwarding, advertise the home subnet with `tailscale set --advertise-routes`, then approve the route in the admin dashboard unless automatic approval is configured. Tailnet access policies must permit connections; on Linux clients, enable route acceptance with `tailscale set --accept-routes`, while phones and Windows devices normally pick up approved routes automatically. Access still depends on the gateway being available and routing and firewall settings allowing the connection.

### Source excerpt

Learn how Tailscale subnet routing lets you securely access your entire homelab remotely without installing Tailscale on every device.

## Candidate and Active Configuration on IOS XR

DevFeed: [Candidate and Active Configuration on IOS XR](<https://devfeed.tech/articles/candidate-and-active-configuration-on-ios-xr-117165.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/11/candidate-active-configuration-iosxr/>)

Published: 2026-11-04T07:37:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>)

Tags: [all](<https://devfeed.tech/tags/all.md>), [automation](<https://devfeed.tech/tags/automation.md>), [band](<https://devfeed.tech/tags/band.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [changes](<https://devfeed.tech/tags/changes.md>), [command](<https://devfeed.tech/tags/command.md>), [commit](<https://devfeed.tech/tags/commit.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [copy](<https://devfeed.tech/tags/copy.md>), [days](<https://devfeed.tech/tags/days.md>), [device](<https://devfeed.tech/tags/device.md>), [devices](<https://devfeed.tech/tags/devices.md>), [disaster](<https://devfeed.tech/tags/disaster.md>), [introduced](<https://devfeed.tech/tags/introduced.md>), [ios](<https://devfeed.tech/tags/ios.md>), [juniper](<https://devfeed.tech/tags/juniper.md>), [make](<https://devfeed.tech/tags/make.md>), [making](<https://devfeed.tech/tags/making.md>), [memory](<https://devfeed.tech/tags/memory.md>), [more](<https://devfeed.tech/tags/more.md>), [xr](<https://devfeed.tech/tags/xr.md>)

### AI overview

Unlike snapshot-based candidate configurations, IOS XR starts configuration mode with an empty set of commands. You can inspect the pending commands with `show configuration`, preview the result of `commit` or `commit replace` with `show configuration merge` or `show configuration replace`, and view proposed differences with `show commit changes diff`. `commit` merges the entered commands; `commit replace` replaces the active configuration, so using it immediately after entering configuration mode can wipe that configuration. The excerpt describes these behaviors but does not cover safeguards or recovery.

### Source excerpt

Traditional network devices used a single (active or running) configuration, with a snapshot of it stored in permanent memory (startup configuration). The active configuration was modified with every configuration command, making it a perfect recipe for disaster in the days of in-band configuration1. The situation improved drastically when Juniper introduced the candidate configuration. You could make changes to a copy of the configuration, and then commit them as a single all-or-nothing transaction. While you could still cut yourself off from the device, at least it was harder to do with a single misordered command. Read more ...

## CVE-2026-57154 - OPNsense: Configuration line injection via multiple GUI text fields

DevFeed: [CVE-2026-57154 - OPNsense: Configuration line injection via multiple GUI text fields](<https://devfeed.tech/articles/cve-2026-57154-opnsense-configuration-line-injection-via-multiple-gui-text-fields-115509.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-57154>)

Author: CVEFEED.io; github.com

Published: 2026-11-03T19:18:06Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [Opnsense](<https://devfeed.tech/topics/opnsense.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [conf](<https://devfeed.tech/tags/conf.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-57154](<https://devfeed.tech/tags/cve-2026-57154.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [dhcp](<https://devfeed.tech/tags/dhcp.md>), [execution](<https://devfeed.tech/tags/execution.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gui](<https://devfeed.tech/tags/gui.md>), [ipsec](<https://devfeed.tech/tags/ipsec.md>), [monit](<https://devfeed.tech/tags/monit.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [ntp](<https://devfeed.tech/tags/ntp.md>), [openvpn](<https://devfeed.tech/tags/openvpn.md>), [opnsense](<https://devfeed.tech/tags/opnsense.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [sudo](<https://devfeed.tech/tags/sudo.md>), [unbound](<https://devfeed.tech/tags/unbound.md>)

### AI overview

Before OPNsense 26.1.11 and 26.4.1p1, authenticated Web UI or API users with delegated access to affected settings could insert CR or LF characters into single-line fields, adding attacker-controlled directives to privileged service configuration files. The confirmed Dnsmasq fields are rendered into /usr/local/etc/dnsmasq.conf; affected settings also span OpenVPN, DHCPv6, Unbound, IPsec, NTP, PPP or MPD, Monit, firewall, sudo, WebGUI, and System General. Applying or restarting a service could exceed delegated permissions, create service-side files, or cause denial of service. Monit injection demonstrated root command execution, while arbitrary shell execution was not confirmed for Dnsmasq. Fixed in versions 26.1.11 and 26.4.1p1.

### Source excerpt

CVE ID :CVE-2026-57154 Published : Nov. 3, 2026, 7:18 p.m. | 1 hour, 3 minutes ago Description :OPNsense is a FreeBSD based firewall and routing platform. Prior to 26.1.11 and 26.4.1p1, authenticated Web UI or API users with delegated access to affected settings can submit CR or LF characters in fields expected to contain one line, causing generated privileged service configuration files to contain additional attacker-controlled directives or policy lines. The confirmed Dnsmasq path includes dhcp_boot.filename, dhcp_boot.servername, dhcp_boot.address, and dhcp_options.value, which are rendered into /usr/local/etc/dnsmasq.conf; access through page-services-dnsforwarder covers api/dnsmasq/*. Related affected fields span OpenVPN, DHCPv6, Unbound, IPsec, NTP, PPP or MPD, Monit, firewall, sudo, WebGUI, and System General configuration. Applying or restarting the affected service can alter behavior beyond the delegated setting, create service-side files, cross RBAC boundaries, or cause denial of service. Line injection through Monit mail password and adjacent Monit text fields into /usr/local/etc/monitrc demonstrated root command execution. Arbitrary shell command execution was not confirmed for the Dnsmasq path. This issue is fixed in versions 26.1.11 and 26.4.1p1. Severity: 8.1 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## LocalStack for Azure Enters Public Preview with Security Settings Stored but Not Enforced

DevFeed: [LocalStack for Azure Enters Public Preview with Security Settings Stored but Not Enforced](<https://devfeed.tech/articles/localstack-for-azure-enters-public-preview-with-security-settings-stored-but-not-enforced-109654.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/localstack-azure-preview/>)

Author: Steef-Jan Wiggers

Published: 2026-10-31T07:57:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Azure](<https://devfeed.tech/topics/azure.md>), [Protection](<https://devfeed.tech/topics/protection.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Azure Kubernetes Service](<https://devfeed.tech/topics/azure-kubernetes-service.md>), [azure container apps](<https://devfeed.tech/topics/azure-container-apps.md>), [azure functions](<https://devfeed.tech/topics/azure-functions.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [aks](<https://devfeed.tech/tags/aks.md>), [announcement](<https://devfeed.tech/tags/announcement.md>), [api](<https://devfeed.tech/tags/api.md>), [api-management](<https://devfeed.tech/tags/api-management.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [azure](<https://devfeed.tech/tags/azure.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [coverage](<https://devfeed.tech/tags/coverage.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [development](<https://devfeed.tech/tags/development.md>), [devops](<https://devfeed.tech/tags/devops.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [free](<https://devfeed.tech/tags/free.md>), [infrastructure-as-code](<https://devfeed.tech/tags/infrastructure-as-code.md>), [localstack-azure-preview](<https://devfeed.tech/tags/localstack-azure-preview.md>), [network](<https://devfeed.tech/tags/network.md>), [news](<https://devfeed.tech/tags/news.md>), [preview](<https://devfeed.tech/tags/preview.md>), [public](<https://devfeed.tech/tags/public.md>), [security](<https://devfeed.tech/tags/security.md>), [terraform](<https://devfeed.tech/tags/terraform.md>), [tls](<https://devfeed.tech/tags/tls.md>)

### AI overview

LocalStack's free Azure emulator preview can run existing ARM, Bicep, Terraform, Pulumi, and Azure CLI deployments in isolated local sandboxes, aiming to test services together without Azure subscriptions. Its documentation shows substantial gaps between accepting configuration and reproducing Azure behavior: App Service access restrictions, authentication settings, and `httpsOnly` are stored but not enforced; networking does not route traffic or enforce security rules; and Storage bearer-token requests may succeed based on token presence unless RBAC enforcement is enabled. API coverage is partial, including 13 of 81 Storage Account operations and 143 of 616 App Service operations. Practical limitations include in-memory App Service state, Linux runtime for Windows plans, and amd64-only Oryx builds that fail on Apple Silicon. LocalStack positions the preview for development and testing, not as an Azure replacement. General availability is expected in early 2027; preview pricing and transition terms remain unsettled.

### Source excerpt

LocalStack has opened its Azure emulator to a free public preview, running Azure services locally and accepting existing ARM, Bicep, and Terraform without rewrites. Its own documentation reports partial operation coverage per service and a consistent pattern: configuration is stored and returned, while enforcement of access restrictions, TLS, and network rules is not implemented. By Steef-Jan Wiggers

## Nexus OS Fails to Send Syslog Records to a Silent Host

DevFeed: [Nexus OS Fails to Send Syslog Records to a Silent Host](<https://devfeed.tech/articles/nexus-os-fails-to-send-syslog-records-to-a-silent-host-102657.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/10/nexus-os-logging-silent-host/>)

Published: 2026-10-27T10:02:00Z

Content type: article

Language: en

Sources: [ipSpace](<https://devfeed.tech/sources/ipspace-net-blog-2.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [arp](<https://devfeed.tech/tags/arp.md>), [cache](<https://devfeed.tech/tags/cache.md>), [capture](<https://devfeed.tech/tags/capture.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-nexus](<https://devfeed.tech/tags/cisco-nexus.md>), [command](<https://devfeed.tech/tags/command.md>), [container](<https://devfeed.tech/tags/container.md>), [functionality](<https://devfeed.tech/tags/functionality.md>), [integration](<https://devfeed.tech/tags/integration.md>), [messages](<https://devfeed.tech/tags/messages.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [nexus](<https://devfeed.tech/tags/nexus.md>), [os](<https://devfeed.tech/tags/os.md>), [running](<https://devfeed.tech/tags/running.md>), [send](<https://devfeed.tech/tags/send.md>), [setup](<https://devfeed.tech/tags/setup.md>), [syslog](<https://devfeed.tech/tags/syslog.md>), [tests](<https://devfeed.tech/tags/tests.md>), [version](<https://devfeed.tech/tags/version.md>), [vm](<https://devfeed.tech/tags/vm.md>)

### AI overview

In a test with Cisco Nexus OS 10.6(2), syslog messages to a directly connected host were not sent while the switch's ARP cache was empty, even though the route and syslog configuration appeared valid. Pinging the host populated ARP, but the capture showed only ARP and ICMP traffic. After another configuration action generated a log entry, Nexus sent two buffered UDP syslog records; their timestamps show the first had been generated about nine minutes earlier. The observed behavior suggests Nexus buffers unsent messages but does not initiate the ARP resolution needed to deliver them to a silent host. The excerpt does not establish whether this occurs in other versions or setups.

### Source excerpt

Here's another you can't make this up SNAFU observation I made when running integration tests for netlab Syslog functionality: Cisco Nexus OS cannot send Syslog messages to a directly connected silent host. The setup is as trivial as it can get: a Cisco Nexus OS VM (running version 10.6(2)) connected to a dnsmasq container running rsyslogd. Read more ...

## APNIC 62 workshops help build network security, automation, and routing expertise across the region

DevFeed: [APNIC 62 workshops help build network security, automation, and routing expertise across the region](<https://devfeed.tech/articles/apnic-62-workshops-help-build-network-security-automation-and-routing-expertise-across-the-region-101319.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/10/27/apnic-62-workshops-help-build-network-security-automation-and-routing-expertise-across-the-region/>)

Author: Sheryl Hermoso

Published: 2026-10-27T01:27:49Z

Content type: news

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [network security](<https://devfeed.tech/topics/network-security.md>), [Network Operations](<https://devfeed.tech/topics/network-operations.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [saltstack](<https://devfeed.tech/topics/saltstack.md>), [Routing Security](<https://devfeed.tech/topics/routing-security.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [BGP](<https://devfeed.tech/topics/bgp.md>)

Tags: [apnic-62](<https://devfeed.tech/tags/apnic-62.md>), [apnic-academy](<https://devfeed.tech/tags/apnic-academy.md>), [apnic-training](<https://devfeed.tech/tags/apnic-training.md>), [automation](<https://devfeed.tech/tags/automation.md>), [bgp](<https://devfeed.tech/tags/bgp.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [ddos](<https://devfeed.tech/tags/ddos.md>), [development](<https://devfeed.tech/tags/development.md>), [distributed-denial-of-service](<https://devfeed.tech/tags/distributed-denial-of-service.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-security](<https://devfeed.tech/tags/dns-security.md>), [ethernet](<https://devfeed.tech/tags/ethernet.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [events](<https://devfeed.tech/tags/events.md>), [evpn](<https://devfeed.tech/tags/evpn.md>), [flex](<https://devfeed.tech/tags/flex.md>), [network](<https://devfeed.tech/tags/network.md>), [network-operators](<https://devfeed.tech/tags/network-operators.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [region](<https://devfeed.tech/tags/region.md>), [routing](<https://devfeed.tech/tags/routing.md>), [security](<https://devfeed.tech/tags/security.md>), [skills](<https://devfeed.tech/tags/skills.md>), [workshops](<https://devfeed.tech/tags/workshops.md>)

### AI overview

APNIC 62's workshops gave network engineers practical training in security, automation, and advanced service provider routing. The APNIC Academy security and automation workshops drew 55 participants; a separately organized INNOG routing workshop drew 27. Security exercises covered topics including DDoS mitigation, BGP and DNS security, RPKI, and open-source tools. The automation workshop covered configuration management, SALT, YAML and Jinja, and event-driven workflows, using a train-the-trainer format so participants could share skills with their teams and communities. INNOG's three-day routing workshop was designed for experienced provider engineers and used hands-on labs for Segment Routing, EVPN, Flex-Algo, Containerlab, and telemetry-driven monitoring. Participant feedback described plans to apply the training to security practices, incident response automation, and safer network operations.

### Source excerpt

More than 80 network engineers and operators strengthened their skills at APNIC 62 through hands-on workshops in network security, automation, and next-generation service provider routing.

## Here's My Network Troubleshooting Toolbox

DevFeed: [Here's My Network Troubleshooting Toolbox](<https://devfeed.tech/articles/here-s-my-network-troubleshooting-toolbox-90793.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/network-troubleshooting-toolbox/>)

Author: Patrick Bacon

Published: 2026-10-20T12:00:47Z

Content type: article

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [network troubleshooting commands](<https://devfeed.tech/topics/network-troubleshooting-commands.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [dig command examples](<https://devfeed.tech/topics/dig-command-examples.md>), [network-intelligence](<https://devfeed.tech/topics/network-intelligence.md>)

Tags: [command](<https://devfeed.tech/tags/command.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [device](<https://devfeed.tech/tags/device.md>), [display](<https://devfeed.tech/tags/display.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-configuration](<https://devfeed.tech/tags/dns-configuration.md>), [dns-servers](<https://devfeed.tech/tags/dns-servers.md>), [domain-name](<https://devfeed.tech/tags/domain-name.md>), [expression](<https://devfeed.tech/tags/expression.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [network-troubleshooting](<https://devfeed.tech/tags/network-troubleshooting.md>), [network-troubleshooting-commands](<https://devfeed.tech/tags/network-troubleshooting-commands.md>), [networking](<https://devfeed.tech/tags/networking.md>), [wireguard](<https://devfeed.tech/tags/wireguard.md>)

### AI overview

The excerpt gives a practical network troubleshooting toolbox for macOS and Linux. Use `netstat -rn -f inet` on macOS or `ip -4 route` on Linux to inspect routes; `route -n get` or `ip route get` to check the route to a specific address; and `scutil --dns` or `resolvectl status` to inspect DNS configuration. For name resolution, `dscacheutil` and `resolvectl query` use the system's configured resolvers, while `dig @server` queries a chosen DNS server. It also shows `ifconfig` and `ip -4 addr` for interface addresses, `lsof` for processes using a port, and `tcpdump` with interface and packet filters to monitor traffic. The author notes these tools have more options than the examples cover.

### Source excerpt

As I mentioned in an earlier post, I've been experimenting a bit with WireGuard lately. In the process, I've been learning about a number of network troubleshooting commands, and before I forget what they all are and do, I'm going to capture them here so I (and you!) can find them again. Here's my network [...] The post Here's My Network Troubleshooting Toolbox appeared first on Atomic Spin.

## MagicRoute beta selects and sticks with preferred subnet routers and app connectors

DevFeed: [MagicRoute beta selects and sticks with preferred subnet routers and app connectors](<https://devfeed.tech/articles/magicroute-routing-without-physical-routers-90223.md>)

Original publisher: [Read original article](<https://tailscale.com/blog/magicroute-beta>)

Author: Simon Law, Amal Bansode, Kevin Purdy

Published: 2026-10-19T14:00:00Z

Content type: release

Language: en

Sources: [Tailscale](<https://devfeed.tech/sources/blog-on-tailscale.md>)

Topics: [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [IP routing](<https://devfeed.tech/topics/ip-routing.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [capacity](<https://devfeed.tech/tags/capacity.md>), [connectors](<https://devfeed.tech/tags/connectors.md>), [datacenter](<https://devfeed.tech/tags/datacenter.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [dns](<https://devfeed.tech/tags/dns.md>), [failover](<https://devfeed.tech/tags/failover.md>), [jitter](<https://devfeed.tech/tags/jitter.md>), [routers](<https://devfeed.tech/tags/routers.md>), [routing](<https://devfeed.tech/tags/routing.md>), [subnet](<https://devfeed.tech/tags/subnet.md>)

### AI overview

Tailscale introduced MagicRoute, a beta feature for Premium and Enterprise customers that ranks subnet routers and app connectors from each client's perspective. It uses approximate location to favor nearby connectors, keeps clients on a preferred healthy connector to reduce disruptive switching, and fails over to another healthy choice when needed. The feature also supports tailnets using custom DERP servers.

### Source excerpt

Smarter routing for subnet routers, app connectors, exit nodes, and Services.

## Routing UDP to on-premises Network Load Balancer targets

DevFeed: [Routing UDP to on-premises Network Load Balancer targets](<https://devfeed.tech/articles/routing-udp-to-on-premises-network-load-balancer-targets-61006.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/networking-and-content-delivery/routing-udp-to-on-premises-network-load-balancer-targets/>)

Author: Tracy Honeycutt

Published: 2026-09-28T16:14:43Z

Content type: tutorial

Language: en

Sources: [Networking & Content Delivery](<https://devfeed.tech/sources/networking-content-delivery.md>)

Topics: [Load Balancing](<https://devfeed.tech/topics/load-balancing.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>), [QUIC](<https://devfeed.tech/topics/quic.md>)

Tags: [amazon-ec2](<https://devfeed.tech/tags/amazon-ec2.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-direct-connect](<https://devfeed.tech/tags/aws-direct-connect.md>), [aws-global-accelerator](<https://devfeed.tech/tags/aws-global-accelerator.md>), [desktop](<https://devfeed.tech/tags/desktop.md>), [elastic-load-balancing](<https://devfeed.tech/tags/elastic-load-balancing.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [hybrid-connectivity](<https://devfeed.tech/tags/hybrid-connectivity.md>), [india](<https://devfeed.tech/tags/india.md>), [load-balancer](<https://devfeed.tech/tags/load-balancer.md>), [network](<https://devfeed.tech/tags/network.md>), [networking](<https://devfeed.tech/tags/networking.md>), [networking-content-delivery](<https://devfeed.tech/tags/networking-content-delivery.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>), [udp](<https://devfeed.tech/tags/udp.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

The article explains why UDP traffic from AWS Network Load Balancers to on-premises targets can fail or degrade despite flow logs and service captures appearing normal. It describes using EC2 proxy instances with kernel NAT, one per Availability Zone, and discusses misleading health and protocol signals during troubleshooting.

### Source excerpt

On-premises migrations to AWS rarely finish in one wave. Dependencies and competing priorities keep some workloads on premises: a virtual desktop gateway, an IPsec VPN headend, applications awaiting modernization. Those workloads can still use the AWS global network. Assume your users are in India and their virtual desktops live in North America. That is a [...]

## Backing Up and Restoring Proxmox VE Host Configuration with ProxMenux

DevFeed: [Backing Up and Restoring Proxmox VE Host Configuration with ProxMenux](<https://devfeed.tech/articles/i-wiped-my-proxmox-host-to-see-if-this-backup-tool-could-bring-it-back-59506.md>)

Original publisher: [Read original article](<https://www.virtualizationhowto.com/2026/09/i-wiped-my-proxmox-host-to-see-if-this-backup-tool-could-bring-it-back/>)

Author: Brandon Lee

Published: 2026-09-24T12:33:25Z

Content type: tutorial

Language: en

Sources: [Virtualization Howto](<https://devfeed.tech/sources/virtualization-howto.md>)

Topics: [Proxmox](<https://devfeed.tech/topics/proxmox.md>), [virtualization](<https://devfeed.tech/topics/virtualization.md>), [backups](<https://devfeed.tech/topics/backups.md>), [virtual machines](<https://devfeed.tech/topics/virtual-machines.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [backup](<https://devfeed.tech/tags/backup.md>), [home-lab](<https://devfeed.tech/tags/home-lab.md>), [home-server](<https://devfeed.tech/tags/home-server.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [proxmox](<https://devfeed.tech/tags/proxmox.md>), [virtual-machines](<https://devfeed.tech/tags/virtual-machines.md>), [virtualization](<https://devfeed.tech/tags/virtualization.md>)

### AI overview

The article explains why disaster-recovery plans for Proxmox should protect the Proxmox VE host configuration in addition to virtual machines and LXC containers. It describes ProxMenux's host backup and restore functionality, including protection for operating configuration, installed components, cluster settings, and networking configuration.

### Source excerpt

There is a critical missing piece to most DR strategies in Proxmox. We all think first about backing up virtual machines and LXC containers that are running workloads and housing... The post I Wiped My Proxmox Host to See If This Backup Tool Could Bring It Back appeared first on Virtualization Howto.

## Configure domain-level VPC networking in Amazon SageMaker Unified Studio

DevFeed: [Configure domain-level VPC networking in Amazon SageMaker Unified Studio](<https://devfeed.tech/articles/configure-domain-level-vpc-networking-in-amazon-sagemaker-unified-studio-58995.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/configure-domain-level-vpc-networking-in-amazon-sagemaker-unified-studio/>)

Author: Prasad Nadig

Published: 2026-09-23T18:36:56Z

Content type: tutorial

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Amazon SageMaker](<https://devfeed.tech/topics/amazon-sagemaker.md>), [Amazon VPC](<https://devfeed.tech/topics/amazon-vpc.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [Security](<https://devfeed.tech/topics/security.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon-sagemaker-unified-studio](<https://devfeed.tech/tags/amazon-sagemaker-unified-studio.md>), [amazon-vpc](<https://devfeed.tech/tags/amazon-vpc.md>), [audit](<https://devfeed.tech/tags/audit.md>), [availability](<https://devfeed.tech/tags/availability.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-cloudtrail](<https://devfeed.tech/tags/aws-cloudtrail.md>), [aws-identity-and-access-management-iam](<https://devfeed.tech/tags/aws-identity-and-access-management-iam.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [isolation](<https://devfeed.tech/tags/isolation.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

A tutorial for configuring domain-level VPC networking in Amazon SageMaker Unified Studio. It explains how new projects inherit subnets, security groups, and VPC endpoints, how to handle existing projects, and how to validate connectivity while improving consistency and auditability.

### Source excerpt

Configuring VPC networking per project across a SageMaker Unified Studio domain creates inconsistent, hard-to-audit networks. This post shows administrators how to configure domain-level VPC networking once, so every new project automatically inherits consistent, private network isolation, then update existing projects and validate connectivity.

## Secure Compute and Static IP builds start 64% faster

DevFeed: [Secure Compute and Static IP builds start 64% faster](<https://devfeed.tech/articles/secure-compute-and-static-ip-builds-start-64-faster-31500.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/secure-compute-and-static-ip-builds-start-64-faster>)

Author: Karim Hasebou

Published: 2026-09-16T17:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Deployment](<https://devfeed.tech/topics/deployment.md>), [container](<https://devfeed.tech/topics/container.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [automatically](<https://devfeed.tech/tags/automatically.md>), [build](<https://devfeed.tech/tags/build.md>), [compute](<https://devfeed.tech/tags/compute.md>), [containers](<https://devfeed.tech/tags/containers.md>), [faster](<https://devfeed.tech/tags/faster.md>), [ip](<https://devfeed.tech/tags/ip.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [static](<https://devfeed.tech/tags/static.md>)

### 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)](<https://devfeed.tech/articles/8-reasons-your-raspberry-pi-wi-fi-is-slow-and-how-to-fix-it-10816.md>)

Original publisher: [Read original article](<https://raspberrytips.com/raspberrypi-wifi-fixes/>)

Author: Thomas Dyan

Published: 2026-09-12T05:00:00Z

Content type: tutorial

Language: en

Sources: [RaspberryTips](<https://devfeed.tech/sources/raspberrytips.md>)

Topics: [Network](<https://devfeed.tech/topics/network.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [ssh](<https://devfeed.tech/topics/ssh.md>), [Terminal](<https://devfeed.tech/topics/terminal.md>), [Operating system](<https://devfeed.tech/topics/operating-system.md>)

Tags: [command-line](<https://devfeed.tech/tags/command-line.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [how-to-tutorials](<https://devfeed.tech/tags/how-to-tutorials.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network](<https://devfeed.tech/tags/network.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [raspberry-pi-os](<https://devfeed.tech/tags/raspberry-pi-os.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [time](<https://devfeed.tech/tags/time.md>)

### 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](<https://devfeed.tech/articles/building-resilient-self-hosted-services-is-not-always-easy-10863.md>)

Original publisher: [Read original article](<https://blog.apnic.net/2026/09/09/building-resilient-self-hosted-services-is-not-always-easy/>)

Author: George Michaelson

Published: 2026-09-09T05:10:54Z

Content type: opinion

Language: en

Sources: [APNIC Blog](<https://devfeed.tech/sources/apnic-blog.md>)

Topics: [Pi-hole](<https://devfeed.tech/topics/pihole.md>), [Resilience](<https://devfeed.tech/topics/resilience.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [systems](<https://devfeed.tech/topics/systems.md>), [Server](<https://devfeed.tech/topics/server.md>)

Tags: [dns](<https://devfeed.tech/tags/dns.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [network](<https://devfeed.tech/tags/network.md>), [resilience](<https://devfeed.tech/tags/resilience.md>), [router](<https://devfeed.tech/tags/router.md>), [self-hosted](<https://devfeed.tech/tags/self-hosted.md>), [server](<https://devfeed.tech/tags/server.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tech-matters](<https://devfeed.tech/tags/tech-matters.md>)

### 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](<https://devfeed.tech/articles/netpicker-ai-assistant-ai-assisted-network-operations-and-compliance-30860.md>)

Original publisher: [Read original article](<https://www.packetcoders.io/netpicker-ai-assistant-ai-assisted-network-operations-and-compliance/>)

Author: Rick Donato

Published: 2026-09-03T12:27:49Z

Content type: article

Language: en

Sources: [Packet Coders - Learn Network Automation](<https://devfeed.tech/sources/packet-coders-learn-network-automation.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Network](<https://devfeed.tech/topics/network.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [network security](<https://devfeed.tech/topics/network-security.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [incident](<https://devfeed.tech/topics/incident.md>), [Software Testing](<https://devfeed.tech/topics/software-testing.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [blog](<https://devfeed.tech/tags/blog.md>), [configuration-management](<https://devfeed.tech/tags/configuration-management.md>), [incident](<https://devfeed.tech/tags/incident.md>), [network](<https://devfeed.tech/tags/network.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### 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

## Linux nameservers and DNS Resolution

DevFeed: [Linux nameservers and DNS Resolution](<https://devfeed.tech/articles/linux-nameservers-and-dns-resolution-20869.md>)

Original publisher: [Read original article](<https://linuxblog.io/linux-nameservers-dns-resolution/>)

Author: Hayden James

Published: 2026-08-10T10:56:20Z

Content type: tutorial

Language: en

Sources: [Hayden James](<https://devfeed.tech/sources/hayden-james.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [systemd](<https://devfeed.tech/topics/systemd.md>), [dig command examples](<https://devfeed.tech/topics/dig-command-examples.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [configure](<https://devfeed.tech/tags/configure.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dns-servers](<https://devfeed.tech/tags/dns-servers.md>), [domain](<https://devfeed.tech/tags/domain.md>), [failover](<https://devfeed.tech/tags/failover.md>), [fedora](<https://devfeed.tech/tags/fedora.md>), [glibc](<https://devfeed.tech/tags/glibc.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [ip](<https://devfeed.tech/tags/ip.md>), [linux](<https://devfeed.tech/tags/linux.md>), [resolver](<https://devfeed.tech/tags/resolver.md>), [retries](<https://devfeed.tech/tags/retries.md>), [security](<https://devfeed.tech/tags/security.md>), [server](<https://devfeed.tech/tags/server.md>), [sysadmins](<https://devfeed.tech/tags/sysadmins.md>), [troubleshoot](<https://devfeed.tech/tags/troubleshoot.md>)

### AI overview

Linux hostname lookup follows the order configured in /etc/nsswitch.conf; entries in /etc/hosts can therefore take precedence over DNS. DNS server settings are in /etc/resolv.conf, whose nameserver entries are tried in order with retries and failover under the traditional glibc resolver. Search and domain directives affect how short names are expanded, while ndots controls when that suffix is tried. On modern distributions, /etc/resolv.conf may be managed automatically, so direct edits can be overwritten after reboot or network changes. Check whether it is a regular file or a symlink to identify what manages it. The excerpt ends during this explanation and does not provide the promised full troubleshooting steps.

### Source excerpt

A practical guide to DNS resolution on Linux: how /etc/resolv.conf, systemd-resolved, and dig work together, and how to troubleshoot common nameserver failures. Continue reading...

## 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)](<https://devfeed.tech/articles/how-to-install-and-use-no-ip-on-raspberry-pi-dynamic-dns-10799.md>)

Original publisher: [Read original article](<https://raspberrytips.com/install-no-ip-raspberry-pi/>)

Author: Patrick Fromaget

Published: 2026-07-23T03:34:36Z

Content type: tutorial

Language: en

Sources: [RaspberryTips](<https://devfeed.tech/sources/raspberrytips.md>)

Topics: [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Homelab](<https://devfeed.tech/topics/homelab.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Server](<https://devfeed.tech/topics/server.md>), [Web](<https://devfeed.tech/topics/web.md>), [hosting](<https://devfeed.tech/topics/hosting.md>)

Tags: [article](<https://devfeed.tech/tags/article.md>), [dns](<https://devfeed.tech/tags/dns.md>), [home-server](<https://devfeed.tech/tags/home-server.md>), [hosting](<https://devfeed.tech/tags/hosting.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [how-to-tutorials](<https://devfeed.tech/tags/how-to-tutorials.md>), [internet](<https://devfeed.tech/tags/internet.md>), [linux](<https://devfeed.tech/tags/linux.md>), [raspberry-pi](<https://devfeed.tech/tags/raspberry-pi.md>), [server](<https://devfeed.tech/tags/server.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [web](<https://devfeed.tech/tags/web.md>)

### 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,...

## Guide to System Hardening: Checklist & Best Practices \[2026\] | Huntress

DevFeed: [Guide to System Hardening: Checklist & Best Practices \[2026\] | Huntress](<https://devfeed.tech/articles/guide-to-system-hardening-checklist-best-practices-2026-huntress-54581.md>)

Original publisher: [Read original article](<https://www.huntress.com/blog/system-hardening-checklist>)

Author: Brenda Buckman

Published: 2026-07-10T13:00:00Z

Content type: tutorial

Language: en

Sources: [Huntress Blog](<https://devfeed.tech/sources/huntress-blog.md>)

Topics: [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Security](<https://devfeed.tech/topics/security.md>), [vulnerability management](<https://devfeed.tech/topics/vulnerability-management.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>)

Tags: [compliance](<https://devfeed.tech/tags/compliance.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [data-breach](<https://devfeed.tech/tags/data-breach.md>), [guide](<https://devfeed.tech/tags/guide.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [logging](<https://devfeed.tech/tags/logging.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [patching](<https://devfeed.tech/tags/patching.md>), [practices](<https://devfeed.tech/tags/practices.md>), [ransomware](<https://devfeed.tech/tags/ransomware.md>)

### AI overview

This guide presents system hardening as a repeatable security process for reducing attack paths caused by default credentials, open ports, unnecessary services, weak permissions, and configuration drift. It covers areas including accounts, network configuration, logging, and physical security, and distinguishes hardening from patching.

### Source excerpt

Threat actors want an easy way in. Use this practical system-hardening checklist to close gaps and learn how to secure your environment today.

## Vercel Services: Run full stack on Vercel

DevFeed: [Vercel Services: Run full stack on Vercel](<https://devfeed.tech/articles/vercel-services-run-full-stack-on-vercel-787.md>)

Original publisher: [Read original article](<https://vercel.com/blog/vercel-services-run-full-stack-on-vercel>)

Author: Joe Haddad

Published: 2026-06-30T04:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Deployment](<https://devfeed.tech/topics/deployment.md>), [FastAPI](<https://devfeed.tech/topics/fastapi.md>), [Next.js](<https://devfeed.tech/topics/next-js.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Routing (disambiguation)](<https://devfeed.tech/topics/routing.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [cli](<https://devfeed.tech/tags/cli.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer-experience](<https://devfeed.tech/tags/developer-experience.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [next-js](<https://devfeed.tech/tags/next-js.md>), [rest](<https://devfeed.tech/tags/rest.md>), [routing](<https://devfeed.tech/tags/routing.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### 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](<https://devfeed.tech/articles/vercel-cli-now-supports-verifying-dns-configuration-1134.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-cli-now-supports-verifying-dns-configuration>)

Author: Elliot Dauber

Published: 2026-06-23T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [DNSSEC](<https://devfeed.tech/topics/dnssec.md>), [Continuous integration](<https://devfeed.tech/topics/continuous-integration.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [JSON](<https://devfeed.tech/topics/json.md>)

Tags: [automation](<https://devfeed.tech/tags/automation.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [dns](<https://devfeed.tech/tags/dns.md>), [dnssec](<https://devfeed.tech/tags/dnssec.md>), [json](<https://devfeed.tech/tags/json.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [verify](<https://devfeed.tech/tags/verify.md>)

### 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)](<https://devfeed.tech/articles/how-we-shipped-15-tbps-for-openai-in-90-days-session-1-of-3-34017.md>)

Original publisher: [Read original article](<https://sridharrajarao.com/blog/openai-15-tbps-session-1/>)

Author: Sridhar Rajarao

Published: 2026-06-08T00:00:00Z

Content type: article

Language: en

Sources: [Sridhar Rajarao](<https://devfeed.tech/sources/sridhar-rajarao.md>)

Topics: [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [Network architectures](<https://devfeed.tech/topics/network-architectures.md>), [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [OpenAI](<https://devfeed.tech/topics/openai.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [gpu](<https://devfeed.tech/tags/gpu.md>), [network](<https://devfeed.tech/tags/network.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [object-storage](<https://devfeed.tech/tags/object-storage.md>), [openai](<https://devfeed.tech/tags/openai.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [production](<https://devfeed.tech/tags/production.md>), [region](<https://devfeed.tech/tags/region.md>), [scale](<https://devfeed.tech/tags/scale.md>), [service](<https://devfeed.tech/tags/service.md>), [sre](<https://devfeed.tech/tags/sre.md>), [storage](<https://devfeed.tech/tags/storage.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### 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.

## Network configuration changes for Copilot coding agent now in effect

DevFeed: [Network configuration changes for Copilot coding agent now in effect](<https://devfeed.tech/articles/network-configuration-changes-for-copilot-coding-agent-now-in-effect-71986.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-03-02-network-configuration-changes-for-copilot-coding-agent-now-in-effect>)

Author: Allison

Published: 2026-03-02T20:42:32Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [Cisco Secure Client](<https://devfeed.tech/topics/cisco-secure-client.md>)

Tags: [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [networking](<https://devfeed.tech/tags/networking.md>), [private](<https://devfeed.tech/tags/private.md>)

### AI overview

Network configuration changes for Copilot coding agent took effect on February 27, 2026. Teams using self-hosted runners or larger runners with Azure private networking must allow subscription-specific hosts based on the initiating user's Copilot plan. The former api.githubcopilot.com host can be removed from the allowlist.

### Source excerpt

On February 13, 2026 we announced changes to the required network configuration for Copilot coding agent, taking effect on February 27. These changes only affect teams running Copilot coding agent...

## Network configuration changes for Copilot coding agent

DevFeed: [Network configuration changes for Copilot coding agent](<https://devfeed.tech/articles/network-configuration-changes-for-copilot-coding-agent-72040.md>)

Original publisher: [Read original article](<https://github.blog/changelog/2026-02-13-network-configuration-changes-for-copilot-coding-agent>)

Author: Allison

Published: 2026-02-13T15:37:05Z

Content type: release

Language: en

Sources: [GitHub Changelog](<https://devfeed.tech/sources/github-changelog.md>)

Topics: [Network Configuration](<https://devfeed.tech/topics/network-configuration.md>), [GitHub Copilot](<https://devfeed.tech/topics/github-copilot.md>), [self-hosted runner](<https://devfeed.tech/topics/self-hosted-runner.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [azure](<https://devfeed.tech/tags/azure.md>), [coding-agent](<https://devfeed.tech/tags/coding-agent.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [github-actions](<https://devfeed.tech/tags/github-actions.md>), [network](<https://devfeed.tech/tags/network.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [repositories](<https://devfeed.tech/tags/repositories.md>), [routing](<https://devfeed.tech/tags/routing.md>), [runner](<https://devfeed.tech/tags/runner.md>)

### AI overview

Starting February 27, 2026 at 00:00 UTC, Copilot coding agent will route AI inference and log streaming to a host determined by the initiating user's plan: Business uses `api.business.githubcopilot.com`, Enterprise uses `api.enterprise.githubcopilot.com`, and Pro or Pro+ uses `api.individual.githubcopilot.com`. Teams using self-hosted runners or larger runners with Azure private networking should check `.github/workflows/copilot-setup-steps.yml` and its `runs-on` value, then ensure those runners can reach the required host or hosts. Repositories without that file are not affected. If access is not configured by the deadline, agent tasks may fail to communicate with GitHub systems.

### Source excerpt

Copilot coding agent is our asynchronous, autonomous background agent. Delegate a task to Copilot, and Copilot works in the background in its own development environment, powered by GitHub Actions. Once...

[Next page](<https://devfeed.tech/topics/network-configuration.md?cursor=WyIyMDI2LTAyLTEzVDE1OjM3OjA1KzAwOjAwIiwgImE1OGM4MDgyLTQ2NjctNDNhOS04NTEzLWYwNDkwZmUxNGVlNyJd>)