Hide Forgot
Description of problem: enabling masquerading using --add-masquerade and --add-rich-rule 'rule masquerade' leads to different results in both ipv4 and ipv6 netfilter rules. Version-Release number of selected component (if applicable): firewalld-0.4.3.2-6.el7.noarch How reproducible: always Steps to Reproduce: exclusively configure either or: --add-masquerade --add-rich-rule 'rule masquerade' Actual results: add-masquerade: ==ipv4: -A POST_public_allow ! -o lo -j MASQUERADE -A FWDO_public_allow -j ACCEPT ==ipv6: !nothing richrule: ==ipv4: -A POST_public_allow ! -o lo -j MASQUERADE -A FWDO_public_allow -m conntrack --ctstate NEW -j ACCEPT ==ipv6: -A POST_public_allow ! -o lo -j MASQUERADE -A FWDO_public_allow -m conntrack --ctstate NEW -j ACCEPT Expected results: both config variants enable masquerading the same way. especially ipv6 rules are either always added or never. Additional info:
Created attachment 1198775 [details] generated rulesets normalized ruleset outputs for ipv4/ipv6 * all 3 variants basic of masquerading
Fixed upstream: https://github.com/t-woerner/firewalld/commit/e5a3fb14f6b3659037cebd2c2034626789f1d099
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1934