Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
@AtuM I've heard of it a long time ago already. Haven't checked it out. But if it's also as easy to brick your server due to fw errors as it is with firewall-cmd, then I'm still sticking with iptables 😁
-
hjk10156965y@AtuM Faster? You do know that all the actual rules and filtering is handled by the same netfilter kernel modules right? All the tools don't filter/forward squat. Just use whatever does it (set kernel rules) properly.
-
hooksie115ySomething is wrong if it's kicking you out. I regularly set firewall rules with firewalld (both manually and with Ansible) and don't get kicked out.
-
@hooksie1 interesting.. Two times this happened already: on my router and a new server. firewall-cmd allowed me to create on-fly rules - they worked well. Reran commands with parameter to persist them -- also no errors. Then reloaded firewalld and I'm out for good until reboot. After reboot I can login again [don't recall if my new rules got loaded tho].
On my router [cent8] Journalctl said firewall found an incorrect iptables command. And the logged command was perfectly fine. Running it manually have me no errors. On server [cent7] -- same thing.
Related Rants
-
gururaju53*Now that's what I call a Hacker* MOTHER OF ALL AUTOMATIONS This seems a long post. but you will definitely ...
-
linuxxx65This guy at my last internship. A windows fanboy to the fucking max! He was saying how he'd never use anythi...
-
creedasaurus60Another dev on my team just got a new machine. Before he came in today I made two separate USB installers and ...
IDK man, it took me a while to finally learn iptables and now switch to firewalld? Oh come on. It's not that I'm against learning new things, no. It's just that firewalld looks a bit.. crappy. If I get a server provisioned and run
firewall-cmd --add-port=53/udp --permanent
firewall-cmd --reload
and I get my ssh connection killed that's no good news, no sir! I mean come on, how can I rely on a tool this critical when a single line in its config file can make my machine inaccessible. Even better -- this config file is managed by that tool entirely!!! My commands passed all the tool's checks and they worked, but when I wanted to make those commands permanent and reload state from the config -- the tool starts spitting bile and blood and says "fuck off, it's my server now!"
IDK man.. It's just way too fishy. The good ol' iptables works very well and I'm kicking its retard younger brother out of the server.
shoosh you dirty pig firewalld, shoosh!
rant
sysadmin
linux
firewalld
does not work well
firewall
iptables
one man's rant