I think manually configuring and saving firewall rules in Atomic Host is a special case. The default build is to support orchestrated containers, and that brings potential for iptables rules automation.
On Apr 21, 2017 10:17, "Dusty Mabe" <du...@dustymabe.com> wrote: > NOTE: if you respond to this message please 'reply-all'. > > I'd like to discuss firewalld on atomic host. Recently I was trying to > figure out the best way to explain to other users how to set firewall rules > on atomic host. > > Usually I would say add your rules and then iptables-save, but on Atomic > Host docker has added it's firewall rules in there dynamically so if you > iptables-save > you'll get a bunch of stuff that you don't want in your static > configuration. > > There are ways around this; manually create your config file, or use > iptables-save > and then rip the docker stuff out. Either way it's a bit of a pain. I think > firewalld would make this easier on the user. Not sure of the pro/con > ratio though. > > Thoughts? > Dusty > _______________________________________________ > cloud mailing list -- cl...@lists.fedoraproject.org > To unsubscribe send an email to cloud-le...@lists.fedoraproject.org >
