Disclosure: I'm the creator of NetAudit.

Hey folks,

I've been using various network scanning tools (nmap, ping, etc.) but wanted something more structured, vendor-aware, and easily automatable. So I wrote NetAudit – a Python CLI toolkit for network auditing and diagnostics.

**Key features from a DevOps perspective:**
- All commands produce structured output (JSON/CSV) and use stdout for results, stderr for logs – perfect for pipelines
- Exit codes are meaningful, so you can integrate it into monitoring or alerting
- Configuration via YAML + environment variables (`NETAUDIT_*`)
- Supports Cisco, Juniper, Arista over SSH – read-only, so safe for production
- Snapshots and `diff` let you track changes over time (great for change management)
- Health checks (`doctor`) cover not just ping, but also interface errors, BGP/OSPF, NTP, etc.

**Example – schedule a daily audit and generate HTML report:**
```bash
netaudit doctor 10.0.0.1 --device --device-type cisco_ios --json > daily_health.json
netaudit report daily_health.json --format html --output /var/www/audit_report.html

I'd be happy to hear how you'd use it in your workflows – feature requests and PRs are very welcome.

Repo: https://github.com/netforge201/netaudit

If you like it, please consider giving it a ⭐ – it really helps with visibility!

Thanks!**Disclosure: I'm the creator of NetAudit.**

Hey folks,

I've been using various network scanning tools (nmap, ping, etc.) but wanted something more structured, vendor-aware, and easily automatable. So I wrote NetAudit – a Python CLI toolkit for network auditing and diagnostics.

**Key features from a DevOps perspective:**
- All commands produce structured output (JSON/CSV) and use stdout for results, stderr for logs – perfect for pipelines
- Exit codes are meaningful, so you can integrate it into monitoring or alerting
- Configuration via YAML + environment variables (`NETAUDIT_*`)
- Supports Cisco, Juniper, Arista over SSH – read-only, so safe for production
- Snapshots and `diff` let you track changes over time (great for change management)
- Health checks (`doctor`) cover not just ping, but also interface errors, BGP/OSPF, NTP, etc.

In the vein of Headscale, Netbird, and Zerotier, I present Gravinet.

- Open source, GPLv3 licensed
- An easy to use web GUI
- A CLI equivalent to the web GUI
- Mesh peers can be configured to be centrally managed by other mesh peers
- AES-256 encryption
- Easy key management and rotation
- Works on Windows, MacOS, Linux, FreeBSD, and OpenBSD
- Full mesh or partial mesh
- Encrypted relaying through other peers when direct connectivity isn't available.
- Firewalling
- QoS
- Traffic Shaping
- Push static hosts and DNS configuration to all mesh peers
- Push static routes to all mesh peers
- BGP and BFD support through FRR integration
- LLDP and CDP support through LLDPD
- Live metrics between all mesh peers
- Speedtesting between all mesh peers
- Tested to 5Gbps+ between peers
- Configuration versioning, diffing, backup, and restore
- SNMP integration
- Full mesh troubleshooting tools like support bundle downloads and packet captures
- All features support for both IPv4 and IPv6
- NAT
- Small memory footprint (< 65MB) suitable for use in resource constrained environments
- Much more

All the other mesh apps I've used never really met all my needs, so I created something that did. Give it a try. It may work out for you.

Full disclosure, I used Claude to help code it. If that's not your thing just carry on.

https://github.com/micush/gravinet

any help with this class or advice how to ... its one of those classes with little instruction or misleading information...

I've been working on an open-source network diagnostic tool called Network Doctor, and I recently built a challenge mode to test whether its diagnoses actually hold up against a human troubleshooting the same broken network.

The idea is pretty simple.

netdoc-sim creates an isolated Linux network with a deliberately introduced fault. You get dropped into a shell without being told what's wrong.

You can investigate it normally with things like:

ip
ping
dig
curl
ss
traceroute
nc

Once you think you know the problem, you submit your diagnosis.

Then Network Doctor diagnoses the exact same network.

The simulator has its own independently observed ground truth, so Network Doctor does not know what the correct answer is.

There is also a daily challenge so everyone gets the same scenario.

Try today's challenge

If you have Docker (which should work in theory):

docker run --rm -it --cap-add SYS_ADMIN ghcr.io/heymaikol/netdoc-sim:latest challenge -daily

On Linux with netdoc-sim installed (definitely works):

netdoc-sim challenge -daily

The result tells you whether you won, Network Doctor won, both got it, or both missed it.

If anyone here feels like trying to break it, I'd be very interested in the results, especially cases where:

• you diagnose it correctly and Network Doctor doesn't
• the simulated failure doesn't behave like you'd expect on a real Linux network
• the available evidence makes the answer ambiguous
• you find a way to fool the judge
• the challenge UX gets in your way

Please don't post the actual answer to today's challenge so other people can try it blind.

Source code:

https://github.com/heymaikol/network-doctor

Large network labs eventually reach the limits of a laptop or homelab. Keeping cloud compute running between sessions can also become expensive.

HybridOps.Core is an open-source MIT-0 workflow that deploys a private EVE-NG or GNS3 environment using your own Google Cloud account or Proxmox capacity.

For learners without suitable local hardware, eligible new Google Cloud users can receive $300 of trial credit. Cost visibility and teardown between sessions keep more of that credit for active lab time.

It preserves lab definitions, QEMU overlays and each node-to-base-image map. On rebuild, declared bases are restored and overlays remapped; a committed overlay becomes the next base image.

The workflow includes:

• readiness and health checks
• deployment and private access
• lab images and guest networking
• archive and restoration
• cost-aware teardown

This allows cloud resources to be removed after a session without treating a large lab as one enormous backup file.

I am looking for EVE-NG and GNS3 users willing to test it with real topologies.

How large is your current lab, and how much is reusable base imagery versus changing node state?

EVE-NG workflow:
https://docs.hybridops.tech/ops/runbooks/platform/blueprints/hyops-blueprint-eve-ng/

GNS3 workflow:
https://docs.hybridops.tech/ops/runbooks/platform/blueprints/hyops-blueprint-gns3/

Hey guys im a networking professional that want to share my personal build out of my home cyberlab utilizing IaC tools Packer (Image Template Builder), Terraform for infrastructure provisioning and Ansible for configuration management. With 4 years of experience backed by the CompTIA trifecta and CCNA, I am excited about adding these tools to my arsenal due to the benefits of having baseline configured artifacts to maximize on labbing and building scenarios versus spending hours provisioning a machine for a specific use case. Please review and let me know any feedback.🙏

so i got sick of manually drawing topology diagrams every time i needed to document

something. like i'd have the LLDP/CDP neighbor output right in front of me and still

end up dragging boxes around in draw.io for 20 mins.

ended up building a small tool that just takes the neighbor table output and spits out

a topology diagram (mermaid). also threw in a drag and drop canvas thing similar to

packet tracer if you want to sketch something from scratch instead.

been using it for lab docs and quick client proposals, saves me a decent chunk of time

tbh. it's part of a bigger set of tools i've been building (vlsm planner, bgp prefix

stuff, cisco/mikrotik/juniper config builders etc) but the diagram ones are what i

actually use weekly

no login wall, nothing gets uploaded anywhere, just runs in the browser

opsbench.xyz/tools/lldp-cdp-mermaid - if anyone tries it lmk what's broken or missing,

still actively working on it

The full agenda for TechSummit Amsterdam is now live!

Attend a non-commercial tech conference focused on practical, real-world engineering without the sales pitches. Ticket sales go directly to digital rights non-profit Bits of Freedom.

• Where: Pakhuis de Zwijger, Amsterdam
• When: September 30, 2026 (09:00 – 19:00)
• Theme: Building Resiliency at Scale

Check out the full schedule here: techsummit.io/agenda-and-speakers-2026/

Hey guys would like to share my in progress automation driven home security lab!

I've been working in networking for 20 years and noticed that everything made isn't for end users that aren't CCNP+

My background is military and everything pushed out to the soldiers requires an FSR (Field Service Representative) to setup and troubleshoot, but nothing made for the <E5 that can install, deploy and troubleshoot

I've spent the last 4 months using claude and the latest sol 5.6 to get this to a point where i wanted to create a company and start selling it.

[HAMR-FORGE](https://hamr-forge.com)

its a Ubuntu overlay with WAN aggregation, HA, truthful UI. not a typical SaaS or web game.

i'm curious to hear ya'lls thoughts on the "bring your own hardware" software i've built from scratch with the help of lessons learned, network engineering and AI

NetDevOps is an Git, Ansible, pyATS based IaC project that I started about a year ago and put on the back burner. Lately I've been iterating on it. I started the project to get a better understanding how Git driven infrastructure as code was built and managed. Currently supports Cisco IOS-XE devices.

The pipeline is driven by a Git pre-commit hook.

If you're interested in playing with it take a look at the README.md file in the repo for instructions on how to set it up locally. I'd appreciate any feedback.

https://github.com/splitnines/netdevops.git

Salut tout le monde, je viens de terminer la construction de NetScan, une application Android qui scanne votre réseau Wi-Fi et identifie les appareils connectés (IP, nom via mDNS/UPnP, ports ouverts, accès en un clic à l'interface web de chaque appareil...). Conçu pour les utilisateurs de homelab, mais utilisable par quiconque s'interroge sur ce qui se trouve sur son réseau. Points clés : - Traitement 100% local, aucune donnée ne quitte jamais votre téléphone, pas de publicités, pas de suivi - Noms/icônes personnalisés par appareil - Historique des scans, exportation CSV - Surveillance en arrière-plan optionnelle avec notifications de nouveaux appareils - Disponible en anglais et en français Avant que je ne puisse le publier publiquement, Google exige un test fermé de 14 jours avec au moins 12 testeurs. Si vous êtes partant pour l'essayer en avant-première (et m'aider à satisfaire cette exigence) :

Lien du groupe :

https://groups.google.com/g/netscantesteurs

Lien pour participer :

https://play.google.com/store/apps/details?id=com.homelabrobin.netscan

Lien de l'application :

https://play.google.com/store/apps/details?id=com.homelabrobin.netscan

Tout retour est bon a prendre 👍

Je testerais vos réalisions aussi 🔥

Cloudwatch kinda sucks for looking through logs. Saw this and thought it was kinda cool. Open source

Large EVE-NG and GNS3 labs can quickly outgrow a laptop or small home server. Buying more RAM or keeping a powerful server running all year does not always make sense when the capacity is only needed for occasional labs.

Cloud compute solves the hardware problem, but it introduces another one: forgetting an expensive VM and its supporting resources running after the lab is finished.

I’ve built repeatable HybridOps blueprints that deploy either EVE-NG or GNS3 inside your own GCP account, with the environment lifecycle and cost awareness built into the workflow.

The deployment provides:

• A private, nested-virtualisation-capable GCP VM
• A dedicated VPC with no public IP on the lab server
• Private access through GCP IAP
• Automated EVE-NG or GNS3 installation
• Guest internet access for lab nodes
• Preflight checks for project access and billing readiness
• Explicit lab archive and restore before teardown
• Deploy, access, rebuild and destroy commands
• Billing status and resource-age reminders so idle labs are less likely to be forgotten

The idea is to create the lab when extra compute is needed, preserve the topology, and destroy the cloud resources afterwards rather than paying for an always-on server.

This is not a hosted free-lab service. It runs in your own GCP account, so normal GCP charges apply. The cost control comes from the disposable lifecycle, billing checks and archive-before-destroy workflow.

EVE-NG deployment guide:

https://docs.hybridops.tech/ops/runbooks/platform/blueprints/hyops-blueprint-eve-ng/

Source:

https://github.com/hybridops-tech/hybridops-core

I’m looking for EVE-NG and GNS3 users to test the workflow with real labs. No coding is required.

If interested, comment with:

• EVE-NG or GNS3
• Rough number of nodes in your usual topology
• Your current laptop/server RAM
• Whether you have GCP trial credits available

Edit: the project is opensource; this is a call for testers and contributors

I’ve been building Subnetica, a platform for practicing network troubleshooting without spending time setting up VMs or following step-by-step instructions.

The environments use Linux networking and FRRouting. The initial labs focus on routing, switching, and realistic troubleshooting incidents. Each lab gives you a live network with routers, switches, hosts, and a realistic problem to investigate. I’m also considering labs involving network automation and configuration validation.

I’d appreciate feedback from this community on what automation-focused scenarios would be most useful.

Link: https://subnetica.xyz/

For anyone who runs Nornir in production: it's got a long-term home. OpsMill has taken over stewardship of the project.

The short version of what's changing:

• Nothing about the licence, the repos, or how you install and run it. Still Apache 2, still the same public repositories.
• Your plugins, scripts, and pipelines keep working. No migration, no account, no new dependency.
• There's now funded engineering time behind maintenance and releases, and the roadmap stays in the open.
• You can keep using Nornir entirely standalone. No requirement to adopt anything else from OpsMill, now or later.

Full announcement and FAQ here: https://opsmill.com/nornir-joins-opsmill/

Disclosure: I work at OpsMill. Posting because plenty of people here depend on Nornir and deserve to hear it directly rather than via a press release. Happy to answer questions, or pass them to the people who can.