all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Hanreich <s.hanreich@proxmox.com>
To: Hannes Duerr <h.duerr@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH pve-docs v3 18/18] firewall: add documentation for forward direction
Date: Fri, 15 Nov 2024 08:49:07 +0100	[thread overview]
Message-ID: <3960d8bd-c343-473b-a5a5-b5bbf41a0c05@proxmox.com> (raw)
In-Reply-To: <b9674b96-f21a-4982-b950-b911293be26a@proxmox.com>



On 11/13/24 16:37, Hannes Duerr wrote:
> I am still not really conviced about the 'zone', but this does not have
> to change with this series.
> I like the other changes, but I think there are some minor issues.
> 
> On 12.11.24 13:26, Stefan Hanreich wrote:
>> diff --git a/pve-firewall.adoc b/pve-firewall.adoc
>> index b428703..d5c664f 100644
>> --- a/pve-firewall.adoc
>> +++ b/pve-firewall.adoc
>> @@ -48,18 +48,34 @@ there is no need to maintain a different set of
>> rules for IPv6.
>>   Zones
>>   -----
>>   -The Proxmox VE firewall groups the network into the following
>> logical zones:
>> +The Proxmox VE firewall groups the network into the following logical
>> zones.
>> +Depending on the zone, you can define firewall rules for incoming,
>> outgoing or
>> +forwarded traffic.
>>     Host::
>>   -Traffic from/to a cluster node
>> +Traffic going from/to a host or traffic that is forwarded by a host.
>> +
>> +You can define rules for this zone either at the datacenter level or
>> at the node
>> +level. Rules at node level take precedence over rules at datacenter
>> level.
> If I am too picky please tell me:
> First we talk about traffic through the 'host' and then we switch to
> talking about 'node level'.
> Shouldn't we at least stick with one word? I think this can confuse users.

Yes, that is indeed true. I'll try and unify the terminology

> 
>>     VM::
>>   -Traffic from/to a specific VM
>> +Traffic going from/to a VM or CT.
>> +
>> +You cannot define rules for the forward direction, only for
>> incoming / outgoing.
> Isn't the word 'traffic' missing at the end?

It's referring to the direction earlier in the sentence, but re-reading
it, it would just be better to make it explicit.

>> +
>> +VNet::
>>   -For each zone, you can define firewall rules for incoming and/or
>> -outgoing traffic.
>> +Traffic passing through a SDN VNet, either from guest to guest or
>> from host to
>> +guest and vice-versa. Since this traffic is always forwarded traffic,
>> it is only
> I think the verb is missing in this sentence also i'd change the
> structure to:
> Traffic is passing trough a SDN VNet, either from guest to guest, from
> host to guest or vice-versa.

Yes, that sounds better.

>> +possible to create rules with direction forward.
>> +
>> +
>> +IMPORTANT: Creating rules for forwarded traffic or on a VNet-level is
>> currently
>> +only possible when using the new
>> +xref:pve_firewall_nft[nftables-based proxmox-firewall]. Any forward
>> rules will be
>> +ignored by the stock `pve-firewall` and have no effect!



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  reply	other threads:[~2024-11-15  7:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-12 12:25 [pve-devel] [PATCH docs/firewall/manager/network/proxmox{-ve-rs, -firewall} v3 00/18] add forward chain firewalling for hosts and vnets Stefan Hanreich
2024-11-12 12:25 ` [pve-devel] [PATCH proxmox-ve-rs v3 01/18] firewall: add forward direction Stefan Hanreich
2024-11-12 12:25 ` [pve-devel] [PATCH proxmox-ve-rs v3 02/18] firewall: add bridge firewall config parser Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH proxmox-ve-rs v3 03/18] config: firewall: add tests for interface and directions Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH proxmox-ve-rs v3 04/18] host: add struct representing bridge names Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH proxmox-firewall v3 05/18] nftables: derive additional traits for nftables types Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH proxmox-firewall v3 06/18] sdn: add support for loading vnet-level firewall config Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH proxmox-firewall v3 07/18] sdn: create forward firewall rules Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH proxmox-firewall v3 08/18] use std::mem::take over drain() Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-firewall v3 09/18] sdn: add vnet firewall configuration Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-firewall v3 10/18] api: add vnet endpoints Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-firewall v3 11/18] firewall: move to arrow syntax for calling functions Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-manager v3 12/18] firewall: add forward direction to rule panel Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-manager v3 13/18] firewall: add vnet to firewall options component Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-manager v3 14/18] firewall: make base_url dynamically configurable in " Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-manager v3 15/18] sdn: add firewall panel Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-manager v3 16/18] firewall: rules: show warning when creating forward rules Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-network v3 17/18] firewall: add endpoints for vnet-level firewall Stefan Hanreich
2024-11-12 12:26 ` [pve-devel] [PATCH pve-docs v3 18/18] firewall: add documentation for forward direction Stefan Hanreich
2024-11-13 15:37   ` Hannes Duerr
2024-11-15  7:49     ` Stefan Hanreich [this message]
2024-11-15  9:30 ` [pve-devel] [PATCH docs/firewall/manager/network/proxmox{-ve-rs, -firewall} v3 00/18] add forward chain firewalling for hosts and vnets Wolfgang Bumiller
2024-11-15 11:25 ` Hannes Duerr
2024-11-15 12:13 ` 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=3960d8bd-c343-473b-a5a5-b5bbf41a0c05@proxmox.com \
    --to=s.hanreich@proxmox.com \
    --cc=h.duerr@proxmox.com \
    --cc=pve-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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal