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!

At this point of my side project I wanted to check out openresty for dynamic proxy creation in nginx.

Happy to check it out I installed centos 7 as guest using new command I just learned virt-builder that would automate vm creation.

Spend 10 hours debugging why I can ping and ssh but cannot get to application port from any network.

Checked iptables, restarted network, reinstalled vm again 3 times with different methods.
Scrolled trough whole internet and it’s mostly outdated problems.
Learned bunch of new commands without new results.

Results were always the same:
No route to host.

Turned out firewalld is fucking thing now.

systemctl firewalld stop helped

Now I know that systemd would kill me at some point for sure.

What I can add at this point ?

Please add more distros, differences, standards and programming languages so world definitely would be better place.
I need a short break now to actually start making shit that I wanted to start at 4-5pm on Saturday.
It’s Sunday 3:30am and time for breakfast.
At least I am happy it started working.

Someone send help. IBM has taken over my village. They're brainwashing the children; they wont use any packages that don't end in 'd'!

How are redhat docs SO EXTENSIVE yet SO USELESS if you need to use it as actual user documentation? I thought they had their shit together, but after two days struggling to find any useful information I found a golden stackoverflow answer (sorry, but it's true) which - in my opinion - should have been the official "getting started" documentation entry for firewalld...
Everybody expects that you have your basic set of ports open (ssh for example), but nobody ever covers the configuration for that very important port 22 before you are locked out of your device. Thanks harperville if you're on here <3

How does firewalld NOT have a service definition for snmpd?