- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Any of you homelabbers/network guys want to test out my network management app?
Posted on 6/8/26 at 9:47 pm
Posted on 6/8/26 at 9:47 pm
We use Cisco DNAC/CCC in our environment at work, but I was looking into something more vendor neutral to use at home. Couldn't find anything that really fit, so I took it to make my own.
Spent a lot of time trying to learn how to code (I stick to my CLI's and Powershell
) and then went to Claude for more extensive help. I've tested it against Cisco equipment, TP Link Omada controllers (read only), Arista equipment, and older Brocade ICX gear. The framework is there for other vendors, but untested for now (trying to get it all tested through GNS3).
Here's the github link. Happy to help with any questions!
Spent a lot of time trying to learn how to code (I stick to my CLI's and Powershell
Here's the github link. Happy to help with any questions!
Posted on 6/9/26 at 2:37 pm to bluebarracuda
Since you mentioned TP-Link Omada, read-only, remember that Omada is a controller-based system, unlike the pure CLIs of Arista or Brocade.
Instead of trying to SSH into Omada-managed switches which usually gets overwritten by the controller anyway, keep utilizing Omada’s OpenAPI. It’s much cleaner for pulling JSON data about your home APs and ports without dealing with CLI scraping.
Instead of trying to SSH into Omada-managed switches which usually gets overwritten by the controller anyway, keep utilizing Omada’s OpenAPI. It’s much cleaner for pulling JSON data about your home APs and ports without dealing with CLI scraping.
Posted on 6/9/26 at 2:47 pm to bluebarracuda
Are you working on stabilizing the automated network discovery, scanning subnets and mapping what's out there? Or are you perfecting the VLAN/Port provisioning interface?
Posted on 6/9/26 at 2:56 pm to Breauxsif
quote:
Instead of trying to SSH into Omada-managed switches which usually gets overwritten by the controller anyway, keep utilizing Omada’s OpenAPI. It’s much cleaner for pulling JSON data about your home APs and ports without dealing with CLI scraping.
That's what it does. You integrate the controller's OpenAPI with SwitchDex's integrations
Clients info tab will bring you to a wireless clients page in SwitchDex, and clicking on the bottom "Open in the Omada controller to make changes" will bring you to your Omada controller login
This post was edited on 6/9/26 at 3:26 pm
Posted on 6/9/26 at 3:01 pm to Breauxsif
quote:
Are you working on stabilizing the automated network discovery, scanning subnets and mapping what's out there?
I've consider automated discovery and upnp, but since this is "vendor neutral", you get back a lot of crap that you don't want.
VLAN or subnet segmented discovery is a good call, though. Got that adding that list of things to check out
quote:
Or are you perfecting the VLAN/Port provisioning interface?
For now it's manually adding devices via SNMP or SSH (ideally via SNMP and then using the built in terminal for SSH to do the config edits). From there, SwitchDex with build out the topology via LLDP/CDP, automate config backups, alert on resource usage (or build out custom alerts), etc
Posted on 6/11/26 at 8:12 pm to bluebarracuda
Hopefully no one using Ubiquiti gear added this because it was full on broke
Finally got around to spinning up a UniFi OS VM and getting my old AP adopted to it
It is working now though
It is working now though
Popular
Back to top

2






