Nsh, a unified router style CLI for OpenBSD
github.com
github.com
To be honest with OpenBSD its not that difficult, and I don't see the point of a tool like NSH for OpenBSD because its so easy to back up and restore all the routing daemon configs.
For your OpenBSD router average setup (from memory, forgive me if I missed something):
- Copy /etc/rc.conf.local
- Copy config files for daemons referred to in /etc/rc.conf.local
- Copy /etc/hostname.if files
- Copy /etc/mygate (if not using dynamic routing)
- Copy /etc/resolv.conf
- Copy /etc/pf.conf
For Linux, really the answer is to use Salt or another config tool to get repeatable configs.
I think the point is getting rid of this risk:
> ... forgive me if I missed something
What risk ?
If I am (for example) running an OpenBSD firewall or OpenBSD BGP router then there's nothing to forget. It really is as simple as I said it was.
The "forgive me if I forget" was because I wrote my answer from memory instead of looking at my actual script.
There really is absolutely zero need for NSH or any tool like it on OpenBSD if you're just running a router/firewall.
When I saw the first paragraph of the Nsh Github Readme my initial thought was "why?".
You can and you should, in my opinion.
However, you really want to use "etckeeper" [0] to do that (as opposed to "maintaining" /etc as a git repo, manually, yourself).
---
ETA:
Seriously, look over etckeeper's README file [1] and/or man page [2]. Next, go read a couple articles or blog posts that describe "How-To store /etc in a git repository on debian linux" [3]. Then, if you're a sado-masochist, go ahead and actually try it that way for a while. Finally, install etckeeper, spend two minutes setting it up (if your packaging tool didn't do that for you automatically), and almost instantly regain your sanity!
---
[0]: http://etckeeper.branchable.com
[1]: http://etckeeper.branchable.com/README/
Yeah, but with a whole shidoodle of extra abstraction and complexity that people have to learn and manage.
The subject has been discussed at length on HN multiple times and (IIRC) the consensus is generally the same, the disadvantages introduced by the complexity of NixOs outweigh its benefits.
I'll stick to old-fashioned distros for now.
> I would love to have this for an entire OS, not just networking. The ability to capture the entire OS configuration in one file would be amazing.
When you can do exactly that with NixOS.
In my experience it’s not hard to set up a basic configuration on NixOS. But it’s too hard to set up all of my development requirements on NixOS.
uci show
Also NeXT/Apple .plist files worked like this.
And looking at modern "DevOps" tooling, we have YAML, or tools that transform YAML into templates and config loaded into other systems (Helm, some parts of Ansible, etc.)