From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Hannes Laimer" <h.laimer@proxmox.com>,
"Proxmox Datacenter Manager development discussion"
<pdm-devel@lists.proxmox.com>,
"Michael Köppl" <m.koeppl@proxmox.com>
Cc: pdm-devel <pdm-devel-bounces@lists.proxmox.com>
Subject: Re: [pdm-devel] [PATCH proxmox v2 4/4] pve-api-types: regenerate
Date: Mon, 10 Nov 2025 16:47:23 +0100 [thread overview]
Message-ID: <DE54RYLECNI4.3CFYEU939E3WK@proxmox.com> (raw)
In-Reply-To: <bb90579a-88fe-4597-b28c-c5dadb9be888@proxmox.com>
On Mon Nov 10, 2025 at 4:33 PM CET, Hannes Laimer wrote:
> which do you mean? IO and forward policy yes, I'll fix/drop those
> default in v3. Are there others?
>
Checked again, just to be sure. I noticed that PVE might be displaying
NDP wrong? The default should be 0, but in pve-manager it's 1, so this
might actually be correct here. Sorry for the confusion, I meant
"many of the structs" including the ones for IO and forward policy. The
remaining ones seem fine upon comparing them again.
> On 11/10/25 16:25, Michael Köppl wrote:
>> While testing this, I noticed that for many of the structs defined here
>> (ClusterFirewallOptions, NodeFirewallOptions, etc.), the default values
>> do not match with the default values defined in the documentation (see
>> [0] and [1]). Didn't go through each of them to check, but when looking
>> at what the PDM UI displays compared to the PVE UI if the firewall
>> hasn't been explicitly configured, many of the values differ (e.g.
>> ebtables).
>>
>> [0] https://pve.proxmox.com/pve-docs/chapter-pve-firewall.html#pve_firewall_cluster_wide_setup
>> [1] https://pve.proxmox.com/pve-docs/chapter-pve-firewall.html#pve_firewall_host_specific_configuration
>>
>> On Wed Nov 5, 2025 at 5:35 PM CET, Hannes Laimer wrote:
>>> + type: String,
>>> + },
>>> + policy_forward: {
>>> + optional: true,
>>> + type: FirewallFWPolicy,
>>> + },
>>> + policy_in: {
>>> + optional: true,
>>> + type: FirewallIOPolicy,
>>> + },
>>> + policy_out: {
>>> + optional: true,
>>> + type: FirewallIOPolicy,
>>> + },
>>> + },
>>> +)]
>>> +/// Object.
>>> +#[derive(Debug, serde::Deserialize, serde::Serialize)]
>>> +pub struct ClusterFirewallOptions {
>>> + /// Enable ebtables rules cluster wide.
>>> + #[serde(deserialize_with = "proxmox_serde::perl::deserialize_bool")]
>>> + #[serde(default, skip_serializing_if = "Option::is_none")]
>>> + pub ebtables: Option<bool>,
>>> +
>>> + /// Enable or disable the firewall cluster wide.
>>> + #[serde(deserialize_with = "proxmox_serde::perl::deserialize_u64")]
>>> + #[serde(default, skip_serializing_if = "Option::is_none")]
>>> + pub enable: Option<u64>,
>>> +
>>> + /// Log ratelimiting settings
>>> + #[serde(default, skip_serializing_if = "Option::is_none")]
>>> + pub log_ratelimit: Option<String>,
>>> +
>>> + #[serde(default, skip_serializing_if = "Option::is_none")]
>>> + pub policy_forward: Option<FirewallFWPolicy>,
>>> +
>>> + #[serde(default, skip_serializing_if = "Option::is_none")]
>>> + pub policy_in: Option<FirewallIOPolicy>,
>>> +
>>> + #[serde(default, skip_serializing_if = "Option::is_none")]
>>> + pub policy_out: Option<FirewallIOPolicy>,
>>> +}
>>
>>
>> _______________________________________________
>> pdm-devel mailing list
>> pdm-devel@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
>>
>>
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next prev parent reply other threads:[~2025-11-10 15:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 16:35 [pdm-devel] [PATCH proxmox{, -yew-comp, -datacenter-manager} v2 00/12] add basic integration of PVE firewall Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox v2 1/4] pve-api-types: update pve-api.json Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox v2 2/4] pve-api-types: add get/update firewall options endpoints Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox v2 3/4] pve-api-types: add list firewall rules endpoints Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox v2 4/4] pve-api-types: regenerate Hannes Laimer
2025-11-10 13:47 ` Michael Köppl
2025-11-10 14:04 ` Hannes Laimer
2025-11-10 15:25 ` Michael Köppl
2025-11-10 15:33 ` Hannes Laimer
2025-11-10 15:40 ` Hannes Laimer
2025-11-10 15:47 ` Michael Köppl [this message]
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-yew-comp v2 1/4] form: add helpers for extractig data out of schemas Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-yew-comp v2 2/4] firewall: add FirewallContext Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-yew-comp v2 3/4] firewall: add options edit form Hannes Laimer
2025-11-07 12:26 ` Lukas Wagner
2025-11-10 12:36 ` Michael Köppl
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-yew-comp v2 4/4] firewall: add rules table Hannes Laimer
2025-11-07 12:26 ` Lukas Wagner
2025-11-10 14:51 ` Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 1/4] pdm-api-types: add firewall status types Hannes Laimer
2025-11-07 12:27 ` Lukas Wagner
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 2/4] api: firewall: add option, rules and status endpoints Hannes Laimer
2025-11-06 16:58 ` Michael Köppl
2025-11-07 6:43 ` Hannes Laimer
2025-11-07 12:27 ` Lukas Wagner
2025-11-10 14:56 ` Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 3/4] pdm-client: add api methods for firewall options, " Hannes Laimer
2025-11-05 16:35 ` [pdm-devel] [PATCH proxmox-datacenter-manager v2 4/4] ui: add firewall status tree Hannes Laimer
2025-11-07 12:27 ` Lukas Wagner
2025-11-10 15:29 ` Hannes Laimer
2025-11-10 17:26 ` [pdm-devel] superseded: [PATCH proxmox{, -yew-comp, -datacenter-manager} v2 00/12] add basic integration of PVE firewall Hannes Laimer
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=DE54RYLECNI4.3CFYEU939E3WK@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=h.laimer@proxmox.com \
--cc=pdm-devel-bounces@lists.proxmox.com \
--cc=pdm-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.