On Aug 26, 2016, at 13:25, Dan White <d_e_wh...@icloud.com> wrote: > > How about > http://www.firewalld.org/documentation -> firewall.direct(5) > https://twoerner.fedorapeople.org/firewalld/doc/firewalld.direct.html > > priority="priority" > The priority is used to order rules. Priority 0 means add rule on top of the > chain, with a higher priority the rule will be added further down. Rules with > the same priority are on the same level and the order of these rules is not > fixed and may change. If you want to make sure that a rule will be added > after another one, use a low priority for the first and a higher for the > following. > > Sounds like the way to force the order. > > Dan White | d_e_wh...@icloud.com > ------------------------------------------------ > “Sometimes I think the surest sign that intelligent life exists elsewhere in > the universe is that none of it has tried to contact us.” (Bill Waterson: > Calvin & Hobbes) > > On Aug 26, 2016, at 12:21 PM, Jeff White <jeff.wh...@wsu.edu> wrote: > > Is there any way to order rich rules in firewalld? If I remove all rules and > add them back in firewalld seems to put them in whatever order it feels like. > > Alternatively, how can I change the default policy of a firewalld zone? At > the moment I don't see any way to have a zone accept traffic by default other > than adding a rich rule allowing 0.0.0.0/0.
I believe the priority feature is introduced in a version later than what is in CentOS 7. However, I believe the 7.3 update (in beta now for RHEL) has a version that supports priority. -- Jonathan Billings _______________________________________________ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
