https://github.com/plumber-cd/ez-ipam
TUI IPAM - subnets calculator
https://github.com/plumber-cd/ez-ipam
ipam ipv4 ipv6 network subnet subnet-calculator subnets subnetting teminal terminal-ui tui
Last synced: 4 months ago
JSON representation
TUI IPAM - subnets calculator
- Host: GitHub
- URL: https://github.com/plumber-cd/ez-ipam
- Owner: plumber-cd
- License: apache-2.0
- Created: 2024-09-12T21:42:00.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2025-01-20T05:04:26.000Z (over 1 year ago)
- Last Synced: 2025-04-14T22:36:56.518Z (about 1 year ago)
- Topics: ipam, ipv4, ipv6, network, subnet, subnet-calculator, subnets, subnetting, teminal, terminal-ui, tui
- Language: Go
- Homepage:
- Size: 1.38 MB
- Stars: 4
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# ez-ipam
This project was inspired by a great tool https://www.davidc.net/sites/default/subnets/subnets.html and its successor https://visualsubnetcalc.com/.
I only ever had two problems with these tools:
- I needed to be able to leave comments at supernet levels, not just at the last subnet of the tree
- I needed a state management that would not require availability of these websites
Other alternatives like SolarWinds or NetBox or phpIPAM were either not Open Source or just had too many dependencies on things like DB and Redis and required you to run it somewhere.
In my personal oppinion, the best tool is the one that you can run locally.
And also I was in TUI mood lately, and I felt like hacking something up with Go and https://github.com/rivo/tview.
What I ended up with is a TUI that would manage its state in the current working directory in the `.ez-ipam` folder as a bunch of YAML files. Additionally, it would generate a summary to [`EZ-IPAM.md`](./EZ-IPAM.md) in a human readable format, so you only ever need the tool to make changes.
This makes it agnostic to how you want to manage the state, you can put it on a NFS for all I care.
My personal idea was that the state along with the `EZ-IPAM.md` file can be in a Git repository.
That way history of changes is traceable, and Git provides out of the box conflict resolution for when multiple people made conficting changes
(and this is why state in the `.ez-ipam` directory is not a single YAML file, to minimize chances of any conflicts).
As a bonus, if you are using GitHub-like platform, the `EZ-IPAM.md` file can be right there in your browser for when you only want to read it.
This repository itself has a `.ez-ipam` folder with some state in it and a [`EZ-IPAM.md`](./EZ-IPAM.md) file generated from it as a demonstration.
# Installation
You can eiter compile it for yourself or download from pre-compiled binaries from https://github.com/plumber-cd/ez-ipam/releases/latest. Sorry, no fancy Brew as of now.
# Contributions
I got to admit that I am not in a business of managing networks for living, so I will only ever focus on what matters for me and my homelab setup, and how it matters to me. But hey - PRs are always welcome, also feel free to fork it as well!