From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 55BEA1FF16B for ; Tue, 29 Jul 2025 08:23:04 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 6AE543FE3E; Tue, 29 Jul 2025 08:24:27 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Stefan Hanreich Date: Tue, 29 Jul 2025 08:21:29 +0200 Message-ID: <175377008747.1884646.12372072916902152630.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.2 In-Reply-To: <20250527135800.190084-1-s.hanreich@proxmox.com> References: <20250527135800.190084-1-s.hanreich@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1753770225519 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.031 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH docs/proxmox-firewall v2 0/4] migrate proxmox-firewall to proxmox-log + introduce subcommands X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Tue, 27 May 2025 15:57:56 +0200, Stefan Hanreich wrote: > Since we now have proxmox-log as the standard crate for logging purposes, > migrate proxmox-firewall to the new logging crate. > > The old logging setup was also tied with the debugging mechanisms described in > the documentation. I used that opportunity to implement specific subcommands for > debugging proxmox-firewall, instead of just relying solely on the log output. > > [...] A slightlier more convenient ping might have been sending a rebased v3, albeit it naturally could have been also looked at earlier, but IMO this better fits a new major release anyway. Applied, with dependencies updated for trixie and d/control and Cargo.toml conflicts resolved, thanks! [1/1] firewall: update 'useful commands' section with new subcommands commit: 0e3aaccaaed89e8df0028e03dccfcc8b5a12faa8 [1/3] firewall: use proxmox_log commit: cf57c86cb4592c603ea78e4ece707d1659f58f99 [2/3] proxmox-firewall: add subcommands commit: 7035e7de3e9f13ace14681141006eed2dc84e60a [3/3] proxmox-firewall: add localnet subcommand commit: f0ac2be37a2f0d188d087534a080050cd1327e21 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel