4 ms·
Nsh, a unified router style CLI for OpenBSD
- 1MachineElf 5y agoThat is so funny I was actually googling around for this around the same time it was submitted here. The project has been around for at least a decade now. I vaguely remembered what it was called although initially I misremembered it due to confusion with Gnome's nmcli. Happy to have found yellowman's nsh GitHub repo as well the flashrd one. Very cool to be able to interact with OpenBSD just like it was a Cisco or HP managed switch. One day I'd like to compare this with Vyatta.
- RedShift1 5y agoI 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. OS upgrade? Get new box, install, copy one config file, boom done. It would also make comparing configurations between hosts so much easier, for example when trying to find out why something works on one box and not on another.
- traceroute66 5y ago> I would love to have this for an entire OS, not just networking. 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 You can also git your /etc of course. For Linux, really the answer is to use Salt or another config tool to get repeatable configs.
- SpaceInvader 5y agoYes, I agree with that. Recently I've switched my FreeBSD router to OpenBSD, getting it running is trivial and for backups - just few files needs to be rsyncd to my backup machine and that's it.
- addingnumbers 5y ago> I don't see the point of a tool like NSH for OpenBSD I think the point is getting rid of this risk: > ... forgive me if I missed something
- traceroute66 5y ago> I think the point is getting rid of this risk: 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.
- INTPenis 5y agoAgreed, in fact I have all of those in Ansible. I've been using OpenBSD as a home router for over a decade. When I saw the first paragraph of the Nsh Github Readme my initial thought was "why?".
- gigatexal 5y agoI've been wanting to move my pfsense box to a vanilla locked down openbsd box -- I think this is really cool but will stick to the handbook and what not way of doing things so as to not be beholden to a third-party tool
- accrual 5y agoI used this tool a while back. It was fun since I was also working in Cisco IOS a lot at the time, so it was cool to see similarities in the syntax and to use them on my favorite OS. These days I stick as close to base as possible.