From: Hannes Laimer <h.laimer@proxmox.com>
To: "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 15:04:38 +0100 [thread overview]
Message-ID: <82b3e008-2e09-4ddd-bb40-385a171e9785@proxmox.com> (raw)
In-Reply-To: <DE527XS7UJQJ.E7GSC094F0IK@proxmox.com>
On 11/10/25 14:46, Michael Köppl wrote:
> On Wed Nov 5, 2025 at 5:35 PM CET, Hannes Laimer wrote:
>> CLUSTER_JOIN_INFO_PREFERRED_NODE_RE = r##"^(?i:[a-z0-9](?i:[a-z0-9\-]*[a-z0-9])?)$"##;
>> @@ -1645,6 +1740,204 @@ pub struct CreateZone {
>> pub zone: String,
>> }
>>
>> +#[api]
>> +/// Firewall IO policies.
>> +#[derive(Clone, Copy, Debug, Default, Eq, PartialEq, serde::Deserialize, serde::Serialize)]
>> +pub enum FirewallFWPolicy {
>> + #[serde(rename = "ACCEPT")]
>> + /// ACCEPT.
>> + Accept,
>> + #[serde(rename = "DROP")]
>> + #[default]
>
> If DROP is the default, then this differs from how PVE handles the case
> where policy_forward is not explicitly configured. At least pve-manager
> considers ACCEPT to be the default, even though the docs don't define a
> default (I think?). So if policy_forward is not explicitly configured
> (i.e. the cluster was just created), the PVE firewall options will
> display Forward Policy set to ACCEPT, whereas PDM will show DROP.
>
yes, this is wrong. The default should be ACCEPT here, as that if what
PVE assume if it is not configured.
>> + /// DROP.
>> + Drop,
>> +}
>> +serde_plain::derive_display_from_serialize!(FirewallFWPolicy);
>> +serde_plain::derive_fromstr_from_deserialize!(FirewallFWPolicy);
>> +
>> +#[api]
>> +/// Firewall IO policies.
>> +#[derive(Clone, Copy, Debug, Default, Eq, PartialEq, serde::Deserialize, serde::Serialize)]
>> +pub enum FirewallIOPolicy {
>> + #[serde(rename = "ACCEPT")]
>> + #[default]
>
> Kind of the same problem as above. Input policy default is DROP, whereas
> Output policy default is ACCEPT (at least for pve-manager). PDM would
> display ACCEPT for both if the values are not explicitly configured.
>
This is a little odd, I don't think we can have the same enum with
different defaults given how the de-duplication of the generator works.
I might be wrong though, I'll look into this, and if we can't then we
probably just have to drop the default here
>> + /// ACCEPT.
>> + Accept,
>> + #[serde(rename = "DROP")]
>> + /// DROP.
>> + Drop,
>> + #[serde(rename = "REJECT")]
>> + /// REJECT.
>> + Reject,
>> +}
>> +serde_plain::derive_display_from_serialize!(FirewallIOPolicy);
>> +serde_plain::derive_fromstr_from_deserialize!(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 14:04 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 [this message]
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
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=82b3e008-2e09-4ddd-bb40-385a171e9785@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=m.koeppl@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.