Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

1.14. Configuring zone priorities for traffic classification by using firewalld

With zone priorities, you can control the packet classification order by specifying priorities for ingress and egress traffic. The benefit is that you can specify the traffic classification order in a zone.

So zone A may be considered before zone B regardless of the source address or interfaces. A zone of a lower priority value has higher precedence over a zone with a higher priority value. This classification has a pair of ingress priority value and egress priority value.

By using the --set-priority option, you can set a common value for both ingress and egress traffic classification without explicit specification.

Prerequisites

  1. Create a new zone: 

    # firewall-cmd --permanent --new-zone=example-zone

  2. Set a common zone priority value for the example-zone zone with --set-priority: 

    # firewall-cmd --permanent --zone example-zone --set-priority -10

    By setting a lower value ensures the higher precedence. This ensures that all configured operations for both traffic types in this zone will take precedence over operations from other zones.

  3. Apply permanent configuration to runtime: 

    # firewall-cmd --reload

Verification

  • Display the priority value for both traffic types: 

    # firewall-cmd --permanent --info-zone example-zone

example-zone
  target: default
  ingress-priority: -10
  egress-priority: -10
  ...
  icmp-block-inversion: no
  ...
  services: dhcpv6-client mdns samba-client ssh
  ...
  forward: yes
  masquerade: no
  ...

    This setting ensures that the traffic will be considered for classification into the example-zone before other zones.

By setting distinct values for ingress and egress traffic, you can set priorities for the traffic classification in a zone.

Procedure

  1. Create a new zone: 

    # firewall-cmd --permanent --new-zone=example-zone

  2. Set a zone priority value for ingress traffic in the example-zone zone with --set-ingress-priority: 

    # firewall-cmd --permanent --zone example-zone --set-ingress-priority -10

  3. Set a zone priority value for egress traffic in the example-zone zone with --set-egress-priority: 

    # firewall-cmd --permanent --zone example-zone --set-egress-priority 100

  4. Apply permanent configuration to runtime: 

    # firewall-cmd --reload

Verification

  • Display the priority value for both traffic types: 

    # firewall-cmd --permanent --info-zone example-zone

example-zone (active)
  target: default
  ingress-priority: -10
  egress-priority: 100
  icmp-block-inversion: no
  interfaces: eth0
  ...
  services: dhcpv6-client mdns samba-client ssh
  ...
  forward: yes
  masquerade: no
  ...

    These values indicate that the ingress traffic has priority over the egress traffic in the example-zone zone before other zones.

Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

Legal Notice

Theme

© 2026 Red Hat返回顶部