11–20 of 70 posts
Earlier quoted context omitted.
You're giving me flashbacks to working on ASAs and issuing a "reboot 15" before making config changes, so that the device would reboot into the last config if you locked yourself out. And those were still in the same building!
How would it reboot on the old config if you had just changed it?
When thinking about how to create IPtables rules for a tricky virtual server environment, I stumbled upon Shorewall. After following along with the documentation, creating the config files as I went, I was able to flip the switch to turn Shorewall on and my firewall behaved exactly as I intended, no trial and error required.
Thank you for all the hard work on this project, I sincerely hope it continues to be supported by the community. Enjoy your travels Tom!
I'm not looking forward to changing this setup.
Earlier quoted context omitted.
You're giving me flashbacks to working on ASAs and issuing a "reboot 15" before making config changes, so that the device would reboot into the last config if you locked yourself out. And those were still in the same building!
How would it reboot on the old config if you had just changed it?
Very impressive that this software was built and maintained by a mostly solo developer into their 70's. Talk about software lifecycle. I wonder if there is much of a community around this software and if there is someone who may take over the future direction, much like how Emacs' head maintainership was recently (relatively) given up by RMS.
Earlier quoted context omitted.
How would it reboot on the old config if you had just changed it?
Been a long time, but doesn't `write conf` write the config to NVRAM?
I'd be SSHd in and restart the rules, then the SSH session would hang. I was actively modifying rules and hey look I was a noobie sysadmin!
I made dumb mistakes back then. I believe that's when I made a catch all rule for my home IP on ssh in and out.
Regardless, thanks Tom!
Man I think I used this software back when I was working out of my closet back in 2004 trying to finish school. This was a nice abstraction on top of IPTables. I definitely remember screwing up rules which caused me to have to drive to the data center about 15 miles from my house after kicking myself out of machines I was SSH'd into.
>after kicking myself out of machines I was SSH'd into I still remember my first 'ifconfig eth0 down' over ssh!
Very impressive that this software was built and maintained by a mostly solo developer into their 70's. Talk about software lifecycle. I wonder if there is much of a community around this software and if there is someone who may take over the future direction, much like how Emacs' head maintainership was recently (relatively) given up by RMS.
Just think about the networking changes that have happened in the last 50 years. This guy is insane to have lived through, and engineered against soo many changes in computer networking. I mean... If you are looking back at this guy's career, you need to realize, to this guy, Linux is a young whipper snapper of an OS. Megabit-speed networks werent even really a thing until this guy was like in his late forties or som…
A project of this popularity and maturity essentially announcing they're shuttering because a single long-term contributor is retiring.. if ever there was a damning indictment of modern consumption-driven open source, I don't know what is
It is possible the maintainers of the various OS distribution packages will band together and maintain development. BTW, what's the general recommendation for people looking to migrate to another Linux firewall package?
Earlier quoted context omitted.
Just think about the networking changes that have happened in the last 50 years. This guy is insane to have lived through, and engineered against soo many changes in computer networking. I mean... If you are looking back at this guy's career, you need to realize, to this guy, Linux is a young whipper snapper of an OS. Megabit-speed networks werent even really a thing until this guy was like in his late forties or som…
It's just a wrapper around iptables...
Frankly, it sounds like your suggesting that because he didn't invent the underlying network stack, or network protocols, that makes it a quick and dirty half day or so project. 99.9% of development work in recent years hasn't been inventing new stuff, it's been building wrappers. Wrappers that compose other well though out tech (which are hard choices to make), while maintaining the flexibility to actually be useful for more than a single project and a short period of time.
I know you said none of those things, however, that's what I read between the lines of a putdown comment like "It's just a wrapper...".