On 8/2/20 12:27 PM, Jeffrey Ross wrote:
I'm looking to make routing decisions based upon either the source or destination TCP port and interface/destination IP, in the Cisco world I'd do this via policy based routing.
The same is true with iptables and firewalld. The article you linked is mostly usable. The only difference is that instead of using "service iptables save", you'll need to specify an iptables rule "directly" to firewalld:
firewall-cmd --permanent --direct --add-rule ipv4 raw OUTPUT 100 -p tcp -m tcp --dport 22 -j MARK –set-mark 0x1
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
