# ipSpace.net blog Published articles for ipSpace.net blog. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Sunsetting netlab Vagrant/libvirt provider DevFeed: [Sunsetting netlab Vagrant/libvirt provider]() Original publisher: [Read original article]() Published: 2026-09-17T05:51:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [Infrastructure as code](), [Orchestration](), [Containerlab topology](), [Oracle-VM-VirtualBox]() Tags: [change](), [containers](), [infrastructure](), [infrastructure-as-code](), [netlab](), [orchestration](), [vagrant](), [virtualbox]() ### AI overview The netlab project is sunsetting its Vagrant/libvirt provider after the vagrant-libvirt plugin became effectively unmaintained and HashiCorp announced the closure of Vagrant Cloud by the end of 2026. Existing support and tests will remain for now, but no new libvirt features or device integration tests are planned; containerlab will become the primary orchestration path. ### Source excerpt When I started the netlab project, Vagrant was the go-to tool if you wanted to build a virtual environment described in a text configuration file (an idea popularized as infrastructure-as-code). It wasn't ideal for what we were doing, but a tool rarely does a great job when used far away from its intended use case. netlab initially supported Vagrant with VirtualBox, quickly adding support for KVM/libvirt through the vagrant-libvirt plugin. Life was good... until it wasn't. Read more ... ## How vagrant-libvirt Plugin Deals with Duplicate Subnets DevFeed: [How vagrant-libvirt Plugin Deals with Duplicate Subnets]() Original publisher: [Read original article]() Published: 2026-09-16T06:27:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Vagrant](), [virtual machines](), [Linux](), [Ubuntu]() Tags: [debugging](), [linux](), [vagrant](), [virtual-machines](), [virtualization]() ### AI overview The article explains that vagrant-libvirt can fail when an existing libvirt virtual network has the same IP subnet as the desired management network but a different name. It identifies the resulting network-name mismatch and reports that correcting the network definition in the Vagrantfile resolves the problem. ### Source excerpt TL&DR: Badly. The vagrant-libvirt plugin mysteriously crashes when an existing virtual network (with a different libvirt name) uses the same IP subnet as the desired management network. Background: netlab is using the vagrant-libvirt plugin to manage libvirt/KVM virtual machines with Vagrant. As I already have that infrastructure, I use it to start standalone virtual machines (usually to test various Ubuntu releases) on my Linux server. Things work great... until they don't. Here's how I managed to waste half a day chasing imaginary gremlins caused by a simple error. Read more ... ## MPLS/VPN with SR-MPLS Core DevFeed: [MPLS/VPN with SR-MPLS Core]() Original publisher: [Read original article]() Published: 2026-09-15T05:45:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [MPLS VPN](), [networking](), [BGP](), [IS-IS](), [Network](), [GitHub]() Tags: [bgp](), [devices](), [github](), [is-is](), [mpls](), [mpls-vpn](), [netlab](), [sr-mpls](), [vpn]() ### AI overview This article explains how to build and test an MPLS/VPN service over an SR-MPLS core. It describes the required lab topology changes, including enabling MPLS/VPN, disabling LDP, configuring PE routers with IS-IS, SR-MPLS, BGP, MPLS, and VRF modules, and moving PE-to-host links into tenant VRFs. It also outlines how to run the lab using GitHub Codespaces, an Arista cEOS container, and netlab. ### Source excerpt As we discussed in the BGP-Free Core with SR-MPLS blog post, SR-MPLS works as a drop-in replacement for the traditional MPLS control plane. No wonder it works well (when properly implemented) with MPLS/VPN services - the second "fun" scenario in my ITNOG10 Segment Routing workshop. It uses the same topology as the BGP-Free Core scenario: Simplest possible MPLS/VPN network with SR-MPLS core Read more ... ## Configuring Management IP Addresses to Virtual Network Devices DevFeed: [Configuring Management IP Addresses to Virtual Network Devices]() Original publisher: [Read original article]() Published: 2026-09-14T05:29:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [networking](), [configuration](), [Orchestration](), [Vagrant](), [Cloud](), [ssh]() Tags: [cli](), [cloud](), [devices](), [dhcp](), [ip](), [ipv4](), [ipv6](), [management](), [netlab](), [network](), [networking](), [orchestration](), [server](), [ssh]() ### AI overview The article explains how to assign predictable management IP addresses to virtual network devices. It contrasts manual console-based setup with automated assignment through orchestration, containers, DHCPv4/DHCPv6, custom Vagrant boxes, and IPv6 mechanisms such as SLAAC. ### Source excerpt It goes without saying that if you want to configure (virtual) network devices with any semi-sane configuration mechanism1, the device must have a working IP address. Here's the time-honored method2 to assign an IP address to a virtual network device: Start the virtual machine (using a GUI)3 Open a new window: either a telnet session to the virtual console port or a full-blown virtual console (GUI) session. Manually configure the IP address, the SSH server, and the user credentials on the first interface. Read more ... ## Worth Reading: NatJack DevFeed: [Worth Reading: NatJack]() Original publisher: [Read original article]() Published: 2026-09-11T07:02:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Security]() Tags: [attacks](), [nat](), [security](), [worth-reading]() ### AI overview The article recommends NatJack, a website documenting several attacks against typical NAT implementations. It argues that NAT should not be treated as a security feature and dismisses common objections to that conclusion. ### Source excerpt Every time I wrote something along the lines of NAT is not a security feature, I got the expected pushback from people defending their bad suboptimal design choices. Fortunately, rational1 engineers no longer need to have that discussion: the NatJack website documents2 a half-dozen attacks on typical NAT implementations. Obvious next step: coping mechanisms like "this is all theoretical", like the "but the remote host cannot reply" argument made 23 years after the Slammer worm 🤦♂. Read more ... ## Worth Reading: An Interactive Introduction to the STP DevFeed: [Worth Reading: An Interactive Introduction to the STP]() Original publisher: [Read original article]() Published: 2026-09-08T05:55:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Protocol (disambiguation)](), [WebAssembly]() Tags: [video](), [webassembly](), [worth-reading]() ### AI overview An enthusiastic recommendation for Vincent Bernat's interactive introduction to the spanning tree protocol, which begins with an STP implementation in WebAssembly and is also available as a video. ### Source excerpt I can't even start imagining how much time Vincent Bernat spent creating his interactive introduction to the spanning tree protocol (starting with STP implemented in WebAssembly); the results are simply phenomenal (there's also a video version for people who forgot how to read). I don't think we'll ever need another STP intro after this one ;) ## Please Help Me Follow Your Content DevFeed: [Please Help Me Follow Your Content]() Original publisher: [Read original article]() Published: 2026-09-04T05:37:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [RSS Feed](), [Web Development]() Tags: [blog-post](), [html](), [rss]() ### AI overview The author argues that email updates and RSS feeds are reliable ways to follow worthwhile blog content, unlike engagement-driven social media algorithms. They urge creators using static website generators to enable or add an RSS feed. ### Source excerpt Finding good content in the swamp of AI slop is hard, and whenever I find a blog post worth reading, I'd like to know when the author publishes the next one. For stupid reasons (like a day having only 24 hours, and me having a life), I can't periodically scan all websites I find interesting, but fortunately, I don't have to. Two well-known mechanisms work reliably: email updates and RSS feeds. Read more ... ## BGP-Free Core with SR-MPLS DevFeed: [BGP-Free Core with SR-MPLS]() Original publisher: [Read original article]() Published: 2026-09-03T05:30:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [BGP](), [networking](), [Network](), [Routing (disambiguation)](), [Containers](), [Linux](), [GitHub]() Tags: [bgp](), [containers](), [edge](), [examples](), [github](), [is-is](), [linux](), [mpls](), [netlab](), [network](), [router](), [routing](), [sr-mpls]() ### AI overview This article demonstrates how to build a BGP-free transport core with SR-MPLS using netlab. It describes a lab topology with IS-IS, BGP, Linux container hosts, and PE routers, then shows how SR-MPLS labels provide end-to-end connectivity without BGP routes on the core router. ### Source excerpt The beauty of SR-MPLS is that it's a drop-in replacement for the traditional (LDP- or RSVP-based) MPLS control plane. For example, you could replace LDP with SR-MPLS in a network using MPLS to implement a BGP-free transport core, and it just keeps working. This scenario was the first "fun" scenario in the ITNOG10 Segment Routing workshop. The core network uses the same topology as in the previous examples; I added two hosts and BGP routing. Simplest possible network using a BGP-free core Read more ... ## Networking Aspects of Running VMs in Containers DevFeed: [Networking Aspects of Running VMs in Containers]() Original publisher: [Read original article]() Published: 2026-09-02T05:44:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Containers](), [virtualization](), [networking](), [Linux](), [Orchestration]() Tags: [bridge](), [containers](), [docker](), [ethernet](), [linux](), [netlab](), [networking](), [podman](), [qemu](), [virtual-machines](), [virtualization]() ### AI overview The article explains how vrnetlab and a containerlab fork package virtual machines, especially network devices, as containers so container orchestration can provision network topologies. It focuses on connecting QEMU virtual network interfaces, Linux tap interfaces, bridges, and container veth pairs, including why data-plane and management interfaces require different handling. ### Source excerpt The vrnetlab project and its containerlab fork implement a wonderful idea: let's package virtual machines (primarily network devices that cannot be containerized) as containers to use reliable orchestration tools like containerlab to provision network topologies. That approach might have a few drawbacks (depending on how the container images are built), but the obvious elephant in the room is: how do you make the virtual network plumbing work? Read more ... ## MUST READ: Git - Going Pro DevFeed: [MUST READ: Git - Going Pro]() Original publisher: [Read original article]() Published: 2026-09-01T05:31:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Git](), [GitHub](), [GitHub Actions](), [ssh](), [Pull Request](), [Command-line interface]() Tags: [article](), [blog](), [cli](), [git](), [github](), [github-actions](), [reviews](), [ssh](), [worth-reading]() ### AI overview A recommendation for Tony Mattke's "Going Pro" article, which covers Git fundamentals and professional practices including SSH keys, pre-commit hooks, GitHub Actions, linting, branch protection, pull-request reviews, and the gh CLI. ### Source excerpt I sure wish Tony Mattke had started publishing his Git-related blog posts in 2017 when I was still struggling with the basics. In his latest Going Pro article he covers: Using SSH keys with Git and GitHub Pre-commit hooks GitHub Actions and linting GitHub Branch protection PR reviews gh CLI Absolutely worth every second you'll spend reading the article! ## Using netlab in Software Testing with Dinesh Dutt DevFeed: [Using netlab in Software Testing with Dinesh Dutt]() Original publisher: [Read original article]() Published: 2026-08-28T06:26:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Software Testing](), [networking](), [software-development](), [Ansible](), [Vagrant]() Tags: [ansible](), [development](), [netlab](), [network](), [networking](), [podcast](), [software](), [software-development](), [software-gone-wild](), [software-testing](), [testing]() ### AI overview This article introduces Episode 208 of Software Gone Wild, a conversation about using netlab to test network management software. It discusses how netlab helps Stardust Systems test new SuzieQ features, along with related history involving Vagrant and Ansible. ### Source excerpt I know a few software development companies use netlab to test their network management software (and contribute back to netlab - thanks a million!), and I always wanted to chat about that. As I have known Dinesh Dutt for ages, it wasn't hard to decide who to invite to have that chat with ;) As it turns out, it's dangerous to put Dinesh1 and me in the same (virtual) room - we were all over the place, from the ancient history of Vagrant in networking labs to the recent Ansible woes, but we did manage to cover how netlab helps Stardust Systems test new SuzieQ features. Read more ... ## Yak-Shaving netlab Podman Support DevFeed: [Yak-Shaving netlab Podman Support]() Original publisher: [Read original article]() Published: 2026-08-27T05:30:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Command-line interface](), [Orchestration](), [Docker](), [Ubuntu](), [Server]() Tags: [cli](), [docker](), [netlab](), [orchestration](), [podman](), [server](), [ubuntu]() ### AI overview The article describes the work required to make netlab support Podman as a runtime. It covers containerlab runtime configuration, Ubuntu-related issues, sudoless operation, Podman's socket-based API, installation automation, Docker-compatible commands, and differences in container visibility between Podman and Docker. ### Source excerpt Long, long time ago, in a long-forgotten PR adding support for Cumulus VX Ignite runtime, an off-the-cuff remark was made saying, "and this is how you use netlab with Podman". That remark was quietly sitting in the documentation for years until someone (A) tried to use Podman and (B) found enough time to report that it doesn't work with netlab. I don't know what that tells us: either very few people use Podman, or nobody (apart from a notable exception) cares enough to spend a few minutes telling us stuff doesn't work1. Anyway, based on Joey Buiteweg's wonderful research, I was able to put together a working solution pretty quickly, but it did involve a lot of yak shaving (more bovine details). Read more ... ## Multivendor SR-MPLS DevFeed: [Multivendor SR-MPLS]() Original publisher: [Read original article]() Published: 2026-08-25T05:44:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [SR-MPLS](), [networking](), [Routing (disambiguation)](), [IS-IS](), [GitHub]() Tags: [github](), [installation](), [is-is](), [mpls](), [netlab](), [network](), [routing](), [sr-mpls]() ### AI overview This tutorial demonstrates a multivendor SR-MPLS network built with netlab using Arista EOS, FRRouting, and SR Linux. It explains vendor-specific Segment Routing Global Block ranges, prefix segments, and MPLS LFIB label swapping, then outlines how to launch the lab through GitHub Codespaces. ### Source excerpt Summer is almost over, and it's time to resume regular programming with the next example from the Segment Routing workshop I had at ITNOG10: multi-vendor SR-MPLS. I used the same lab topology as in the previous examples but deployed Arista EOS on PE1, FRRouting on P, and SR Linux on PE21 Read more ... ## Arista cEOS Does Not Apply ACLs to Control-Plane Traffic DevFeed: [Arista cEOS Does Not Apply ACLs to Control-Plane Traffic]() Original publisher: [Read original article]() Published: 2026-08-24T05:20:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [BGP](), [Containers](), [Finite-state machine](), [configuration]() Tags: [bgp](), [containers](), [netlab](), [network](), [release](), [security](), [testing]() ### AI overview The article reports that Arista cEOS containers do not apply inbound ACLs to control-plane traffic or to traffic sent to the container's own IP addresses. This behavior differs from Arista vEOS virtual machines and can cause BGP connectivity tests using ACLs to produce unexpected results. ### Source excerpt When someone starts singing the Use Digital Twins to Test Your Network hymn (or, more recently, tells you how AI agents can do that to validate their ideas), ask them about these minor details. If they persist, point them (not that it would help) to this long list of gotchas. That list just got longer: Arista cEOS container does not apply inbound ACLs to control-plane traffic (Arista vEOS VM does). Read more ... ## Worth Reading: Reading the Git Crime Scene DevFeed: [Worth Reading: Reading the Git Crime Scene]() Original publisher: [Read original article]() Published: 2026-08-20T05:56:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Git](), [networking]() Tags: [article](), [git](), [how-to](), [worth-reading]() ### AI overview A recommendation for an article explaining how to investigate a Git repository to determine who made specific changes and why. ### Source excerpt Tony Mattke continues publishing excellent "Git for Networking Engineers" content. In his latest article, he described how to find who made what changes (and why) in a Git repository. Absolutely worth reading if you're new to Git, but even oldtimers might find a few useful tidbits (Git is one of those things one never truly masters). ## Worth Reading: On AI Coding and Its Discontents DevFeed: [Worth Reading: On AI Coding and Its Discontents]() Original publisher: [Read original article]() Published: 2026-08-19T06:24:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [ai-coding](), [coding](), [Code]() Tags: [agentic](), [ai](), [ai-coding](), [blog-post](), [coding](), [development](), [worth-reading]() ### AI overview The article argues that AI coding tools should not be treated like traditional compilers. Unlike deterministic, mature compilers, AI coding tools can produce bugs, and agentic loops do not eliminate that reliability gap. It points readers to Cal Newport's discussion of the drawbacks of AI-assisted coding. ### Source excerpt A lot of AI-coding enthusiasts are making claims along the lines of "AI coding tools are like compilers; you supply intent, they translate it into code, and who ever looked at the machine-code output?" Unfortunately, there is a bit of a gap between hope and reality; traditional compilers were always deterministic, and are (after decades of development and bug-fixing) pretty much bug-free. AI coding tools are neither, and no amount of "agentic loops" will solve that. Read more ... ## Exploring the BGP Neighbor CONNECT State DevFeed: [Exploring the BGP Neighbor CONNECT State]() Original publisher: [Read original article]() Published: 2026-08-18T05:16:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [BGP](), [networking](), [Finite-state machine](), [Routing (disambiguation)]() Tags: [bgp](), [blog-post](), [debug](), [routing]() ### AI overview An exploration of how Cisco IOS/XE presents the BGP neighbor CONNECT state during an incoming TCP session. The article tests several lab scenarios involving passive neighbors, static discard routes, ACLs, and suppressed ICMP unreachable messages, finding that CONNECT appears in BGP debugging output while the neighbor remains Idle in the displayed operational state. ### Source excerpt Sakar left an interesting comment on my The Curious Case of the BGP Connect State blog post, claiming that Cisco IOS/XE goes through a CONNECT state when opening an incoming BGP session. I wanted to double-check this behavior, so I needed a scenario where one router would keep sending TCP SYN requests, the other would not (or we wouldn't learn anything), and the two routers could not communicate (or they'd quickly go into the OPEN state). Here's my first attempt at meeting those requirements: Read more ... ## The Never-Ending IPv6 Loopback Prefix Saga DevFeed: [The Never-Ending IPv6 Loopback Prefix Saga]() Original publisher: [Read original article]() Published: 2026-08-17T06:02:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Network](), [Hardware](), [datacenter](), [BGP]() Tags: [bgp](), [datacenter](), [hardware](), [ios](), [ipv6](), [is-is](), [netlab](), [network](), [ospf](), [vxlan]() ### AI overview The article examines the IPv6 loopback-prefix problem in high-speed routers and data-center switches. OSPFv3 requires loopbacks to be advertised as /128s, which can increase forwarding hardware demands when /64 addressing is preferred. It compares vendor behaviors and suggests IS-IS or BGP as possible alternatives. ### Source excerpt Remember the sage advice to simplify your life and use the IPv6 /64 prefixes everywhere? Not only does it make your life simpler (and wastes immesuarably less address space than the crazy "let's assign /64 to every device" stupidity), it also reduces the hardware requirements in your high-speed routers layer-3 switches. You see, doing lookups on 64 bits uses half the silicon it takes to do lookups on 128 bits. Alas, some people never got the memo. OSPFv3 standard clearly states in one of the bullets in section 4.4.3.9 that the loopback prefixes should always be advertised as /128s regardless of what's configured on the interface. Read more ... ## Worth Reading: LLM Prompts for Network Engineers DevFeed: [Worth Reading: LLM Prompts for Network Engineers]() Original publisher: [Read original article]() Published: 2026-08-13T06:07:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Large Language Model](), [Prompt Engineering](), [Network](), [Artificial Intelligence]() Tags: [ai](), [llm](), [network](), [tokens](), [worth-reading]() ### AI overview A recommendation for network engineers to read a collection of LLM prompt suggestions intended to help them get more value from their tokens. ### Source excerpt Tony Mattke put together a long list of recommendations that might help you get more out of your LLM tokens. Definitely worth reading instead of yelling at the stupid AI. ## Compress netlab Lab Topologies with Dot Notation DevFeed: [Compress netlab Lab Topologies with Dot Notation]() Original publisher: [Read original article]() Published: 2026-08-12T05:55:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Python](), [YAML](), [BGP]() Tags: [bgp](), [blog](), [blog-post](), [netlab](), [post](), [python]() ### AI overview An article about using Python Box dotted notation to make netlab lab topology definitions easier to read and more concise, including examples in YAML for BGP routers and IPv4 links. ### Source excerpt netlab is using the Python Box library to make the code easier to read1. When I started the project, I hated the way you fetch values from Python dictionaries with stuff like node['ospf']['area']; Python Box lets you write node.ospf.area. Even better2, you can tell Python Box to create intermediate dictionaries as needed. node.ospf.area = 1 will automatically create the node.ospf dictionary. But wait, there's more (yes, we're getting to the topic of today's blog post): Box lets you use the same dotted notation in YAML files. Read more ... ## On ACLs and AI-Generated Device Configurations DevFeed: [On ACLs and AI-Generated Device Configurations]() Original publisher: [Read original article]() Published: 2026-08-11T05:11:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Artificial Intelligence]() Tags: [ai](), [driving](), [netlab](), [qos](), [youtube]() ### AI overview The article introduces a NetworkAutoMagic episode discussing ACL complexity, QoS, and the pitfalls of AI-generated network device configurations, with related notes and video options mentioned. ### Source excerpt Last Friday, I had a lovely chat with Steinn Bjarnarson and Urs Baumann, resulting in the NetworkAutoMagic episode 11. We couldn't avoid mentioning netlab, the seven layers of ACL hell (which is still balmy compared to the QoS hell), and the gotchas of AI-generated device configurations. Fortunately, I don't have to go into more details; Steinn published extensive notes, and if you don't feel like listening to us while driving, you can waste time watching us on YouTube. ## netlab 26.08: ArcOS, VPP (FD.io), ACLs, and DNS DevFeed: [netlab 26.08: ArcOS, VPP (FD.io), ACLs, and DNS]() Original publisher: [Read original article]() Published: 2026-08-10T09:58:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Release notes](), [networking](), [Containers](), [configuration](), [Routing (disambiguation)](), [Authorization]() Tags: [access-control](), [configuration](), [dns](), [getting-started](), [github](), [gre](), [installation](), [ipv4](), [ipv6](), [netlab](), [podman](), [release](), [release-notes](), [routing]() ### AI overview netlab 26.08 adds ArcOS support, VPP with FRR or BIRD control planes, SONiC containers, IPv4/IPv6 access control lists, DNS client and server configuration, GRE and WireGuard tunnel support, and Podman support for the clab provider. The article also notes bug fixes, configuration-template changes, upgrade guidance, and documentation for new users. ### Source excerpt netlab release 26.08 brings a few humongous additions: ArcOS support by @roc-ops VPP (FD.io) with FRR or BIRD control plane by @jbemmel SONiC containers (also by @roc-ops) IPv4/IPv6 access control lists in the routing module by @DanPartelly But wait, there's more: Read more ... ## On the Futility of Opening Ansible Issues DevFeed: [On the Futility of Opening Ansible Issues]() Original publisher: [Read original article]() Published: 2026-07-22T06:03:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [bug](), [Open Source](), [configuration](), [networking]() Tags: [ansible](), [bug](), [cli](), [github](), [network](), [open-source]() ### AI overview The author describes opening an Ansible issue after discovering that the cisco.ios.ios_config module did not report rejected Cisco IOS configuration commands. The issue was initially closed without the proposed error-message fix, but an update says it was later reopened and fixed shortly after publication. ### Source excerpt Remember the anonymous troll who chided me for writing a rant instead of opening a GitHub issue in the relevant Ansible repository? Well, I decided to be an open-source poster boy when I stumbled upon the next Ansible bug, and ended up feeling like a sweet summer child :( Read more ... ## Content: New Parameter in Multiple something\_config Ansible Modules DevFeed: [Content: New Parameter in Multiple something\_config Ansible Modules]() Original publisher: [Read original article]() Published: 2026-07-15T05:22:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [configuration](), [Network](), [issue tracker]() Tags: [ansible](), [network]() ### AI overview The article discusses new parameters added to several Ansible network device configuration modules after concerns about templating behavior and a change introduced in Ansible 12. It describes the author's issue report and notes that the issue's closure was due to poor issue management rather than rejection of the proposed solution. ### Source excerpt Last December, I wrote a pretty ranty post explaining how Ansible release 12 broke (some?) network device configuration playbooks. The inevitable anonymous troll (why are they always anonymous?) couldn't resist asking whether I opened an issue on GitHub. I didn't (more about that later), but when the solution to that rant was "we're deprecating using templates in src" parameter, I opened an issue arguing why that's not a good idea. Read more ... [Next page]()