From: Gabriel Goller <g.goller@proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
Subject: [pve-devel] [PATCH ve-rs v2 1/2] fix: firewall: introduce iptables to nftables mapping for icmp-types
Date: Mon, 6 Oct 2025 12:19:29 +0200 [thread overview]
Message-ID: <20251006101933.90655-2-g.goller@proxmox.com> (raw)
In-Reply-To: <20251006101933.90655-1-g.goller@proxmox.com>
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
Some of the icmp-type options that we expose in the UI don't exist as
standalone nftables options, so we need to create them using a custom
type and code id.
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
proxmox-ve-config/src/firewall/types/rule.rs | 9 +--
.../src/firewall/types/rule_match.rs | 67 ++++++++++++++++---
2 files changed, 63 insertions(+), 13 deletions(-)
diff --git a/proxmox-ve-config/src/firewall/types/rule.rs b/proxmox-ve-config/src/firewall/types/rule.rs
index 3ad8cf059f09..d20145cb902e 100644
--- a/proxmox-ve-config/src/firewall/types/rule.rs
+++ b/proxmox-ve-config/src/firewall/types/rule.rs
@@ -254,7 +254,7 @@ mod tests {
alias::{AliasName, AliasScope},
ipset::{IpsetName, IpsetScope},
log::LogLevel,
- rule_match::{Icmp, IcmpCode, IpAddrMatch, IpMatch, Ports, Protocol, Udp},
+ rule_match::{Icmp, IcmpCode, IcmpType, IpAddrMatch, IpMatch, Ports, Protocol, Udp},
};
use super::*;
@@ -338,9 +338,10 @@ mod tests {
),
)
.ok(),
- proto: Some(Protocol::Icmp(Icmp::new_code(IcmpCode::Named(
- "port-unreachable"
- )))),
+ proto: Some(Protocol::Icmp(Icmp::new_ty_and_code(
+ IcmpType::Numeric(3),
+ IcmpCode::Numeric(3)
+ ))),
log: Some(LogLevel::Nolog),
..Default::default()
}),
diff --git a/proxmox-ve-config/src/firewall/types/rule_match.rs b/proxmox-ve-config/src/firewall/types/rule_match.rs
index 7fcd35c80d86..f99a936b454a 100644
--- a/proxmox-ve-config/src/firewall/types/rule_match.rs
+++ b/proxmox-ve-config/src/firewall/types/rule_match.rs
@@ -463,10 +463,10 @@ impl Icmp {
}
}
- pub fn new_code(code: IcmpCode) -> Self {
+ pub fn new_ty_and_code(ty: IcmpType, code: IcmpCode) -> Self {
Self {
+ ty: Some(ty),
code: Some(code),
- ..Default::default()
}
}
@@ -487,19 +487,61 @@ impl Icmp {
}
}
+/// Some icmp_types are not supported by nftables. See:
+/// https://wiki.nftables.org/wiki-nftables/index.php/Supported_features_compared_to_xtables#icmp
+/// Some have an exact equivalent in nftables and for some others we need to set a custom type and
+/// code combination.
+#[sortable]
+const IPTABLES_ICMP_TYPES_MAPPING: [(&str, IcmpTypeMap); 23] = sorted!([
+ ("network-unreachable", IcmpTypeMap::Custom((3, 0))),
+ ("host-unreachable", IcmpTypeMap::Custom((3, 1))),
+ ("protocol-unreachable", IcmpTypeMap::Custom((3, 2))),
+ ("port-unreachable", IcmpTypeMap::Custom((3, 3))),
+ ("fragmentation-needed", IcmpTypeMap::Custom((3, 4))),
+ ("source-route-failed", IcmpTypeMap::Custom((3, 5))),
+ ("network-unknown", IcmpTypeMap::Custom((3, 6))),
+ ("host-unknown", IcmpTypeMap::Custom((3, 7))),
+ ("network-prohibited", IcmpTypeMap::Custom((3, 9))),
+ ("host-prohibited", IcmpTypeMap::Custom((3, 10))),
+ ("TOS-network-unreachable", IcmpTypeMap::Custom((3, 11))),
+ ("TOS-host-unreachable", IcmpTypeMap::Custom((3, 12))),
+ ("communication-prohibited", IcmpTypeMap::Custom((3, 13))),
+ ("host-precedence-violation", IcmpTypeMap::Custom((3, 14))),
+ ("precedence-cutoff", IcmpTypeMap::Custom((3, 15))),
+ ("network-redirect", IcmpTypeMap::Custom((5, 0))),
+ ("host-redirect", IcmpTypeMap::Custom((5, 1))),
+ ("TOS-network-redirect", IcmpTypeMap::Custom((5, 2))),
+ ("TOS-host-redirect", IcmpTypeMap::Custom((5, 3))),
+ ("ttl-zero-during-transit", IcmpTypeMap::Custom((11, 0))),
+ ("ttl-zero-during-reassembly", IcmpTypeMap::Custom((11, 1))),
+ ("ip-header-bad", IcmpTypeMap::Custom((12, 0))),
+ ("required-option-missing", IcmpTypeMap::Custom((12, 1))),
+]);
+
impl FromStr for Icmp {
type Err = Error;
fn from_str(s: &str) -> Result<Self, Self::Err> {
let mut this = Self::default();
- if let Ok(ty) = s.parse() {
- this.ty = Some(ty);
- return Ok(this);
+ // Some icmp types exist in iptables, but do not in nftables. Some of these map exactly
+ // onto other types, for others we need to use a custom type/code combination.
+ if let Ok(index) = IPTABLES_ICMP_TYPES_MAPPING.binary_search_by(|v| v.0.cmp(s)) {
+ match IPTABLES_ICMP_TYPES_MAPPING[index].1 {
+ IcmpTypeMap::Map(mapped_nftables_type) => {
+ this.ty = Some(IcmpType::Named(mapped_nftables_type));
+ return Ok(this);
+ }
+ IcmpTypeMap::Custom((ty, code)) => {
+ this.ty = Some(IcmpType::Numeric(ty));
+ this.code = Some(IcmpCode::Numeric(code));
+ return Ok(this);
+ }
+ }
}
- if let Ok(code) = s.parse() {
- this.code = Some(code);
+ if let Ok(ty) = s.parse() {
+ this.ty = Some(ty);
return Ok(this);
}
@@ -646,6 +688,13 @@ impl Icmpv6 {
}
}
+enum IcmpTypeMap {
+ /// This icmp type can be mapped exactly to an equivalent nftables type
+ Map(&'static str),
+ /// This icmp type needs to be represented using a custom type and code combination
+ Custom((u8, u8)),
+}
+
impl FromStr for Icmpv6 {
type Err = Error;
@@ -938,8 +987,8 @@ mod tests {
assert_eq!(
icmp,
Icmp {
- ty: None,
- code: Some(IcmpCode::Named("port-unreachable"))
+ ty: Some(IcmpType::Numeric(3)),
+ code: Some(IcmpCode::Numeric(3))
}
);
}
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-10-06 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 10:19 [pve-devel] [PATCH proxmox-firewall/ve-rs v2 0/3] Fix ICMP types in nftables Gabriel Goller
2025-10-06 10:19 ` Gabriel Goller [this message]
2025-10-07 11:43 ` [pve-devel] [PATCH ve-rs v2 1/2] fix: firewall: introduce iptables to nftables mapping for icmp-types Gabriel Goller
2025-10-06 10:19 ` [pve-devel] [PATCH ve-rs v2 2/2] fix: firewall: introduce iptables to nftables mapping for icmpv6-types Gabriel Goller
2025-10-06 10:19 ` [pve-devel] [PATCH proxmox-firewall v2 1/1] tests: add icmpv6 type mapping test Gabriel Goller
2025-10-08 13:17 ` [pve-devel] [PATCH proxmox-firewall/ve-rs v2 0/3] Fix ICMP types in nftables Stefan Hanreich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251006101933.90655-2-g.goller@proxmox.com \
--to=g.goller@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=w.bumiller@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox