From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id B6DF01FF189 for <inbox@lore.proxmox.com>; Fri, 4 Apr 2025 14:10:59 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E9B521DC28; Fri, 4 Apr 2025 14:10:45 +0200 (CEST) Date: Mon, 31 Mar 2025 14:38:08 +0000 To: Stefan Hanreich <s.hanreich@proxmox.com> In-Reply-To: <680964c9-8847-4a11-8ac2-431fb8c876f2@proxmox.com> References: <20241008040109.322473-1-andrew@apalrd.net> <mailman.223.1728378819.332.pve-devel@lists.proxmox.com> <d5f5ac3a-bc06-459d-adb3-3b64436d0ef1@proxmox.com> <DE78AE8B-31EE-447A-962D-719F3C924700@apalrd.net> <680964c9-8847-4a11-8ac2-431fb8c876f2@proxmox.com> X-Mailman-Approved-At: Fri, 04 Apr 2025 14:10:44 +0200 MIME-Version: 1.0 Message-ID: <mailman.622.1743768644.359.pve-devel@lists.proxmox.com> List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Post: <mailto:pve-devel@lists.proxmox.com> From: Andrew via pve-devel <pve-devel@lists.proxmox.com> Precedence: list Cc: Andrew <andrew@apalrd.net>, Proxmox VE development discussion <pve-devel@lists.proxmox.com> X-Mailman-Version: 2.1.29 X-BeenThere: pve-devel@lists.proxmox.com List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> Subject: Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan Content-Type: multipart/mixed; boundary="===============0586815953785964462==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> --===============0586815953785964462== Content-Type: message/rfc822 Content-Disposition: inline Return-Path: <andrew@apalrd.net> X-Original-To: pve-devel@lists.proxmox.com Delivered-To: pve-devel@lists.proxmox.com Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 4D36FCD172 for <pve-devel@lists.proxmox.com>; Mon, 31 Mar 2025 16:38:19 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3736A8FEE for <pve-devel@lists.proxmox.com>; Mon, 31 Mar 2025 16:38:19 +0200 (CEST) Received: from mail-4317.protonmail.ch (mail-4317.protonmail.ch [185.70.43.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-devel@lists.proxmox.com>; Mon, 31 Mar 2025 16:38:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apalrd.net; s=protonmail2; t=1743431892; x=1743691092; bh=Nx3qKODqArcCGK2UNCU+vQl5okrAhd3xxuGHGiYqtaE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=0QEWZA0Qc9MqoyPGOAhM9+fcI5Yq+jGZRHTpghYwiPDquZ1/IrhFb9GH6Ab+b/wE4 +NT0syTLy4u/5wsj/L/Zox0U45/ebbSwASWP4CUsm7MYAM0dPljWGkwK7JbcEQet+R x8zH22uiiJxm2MH+iV/pF40psseN2/8tjRCY18oVlG/Lt2DTZ0A/h7XTgZEpB6Pgfk yw3rMkzidiMhu4tXcydZNI/AzDInHJ9/J5/dcBiTTeBQw/6LHDrw6iqrnAOFXV/ZS+ KWLpS3wFY1d2LuJm1MG1yHOt4wPLwUbO9sonynnslUjWOHi8a/1UCpAUHGA/GkLWZX SdVqcfsZAhNyQ== Date: Mon, 31 Mar 2025 14:38:08 +0000 To: Stefan Hanreich <s.hanreich@proxmox.com> From: Andrew <andrew@apalrd.net> Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Subject: Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan Message-ID: <511405BE-CEF9-4C26-8E75-A4235FC58420@apalrd.net> In-Reply-To: <680964c9-8847-4a11-8ac2-431fb8c876f2@proxmox.com> References: <20241008040109.322473-1-andrew@apalrd.net> <mailman.223.1728378819.332.pve-devel@lists.proxmox.com> <d5f5ac3a-bc06-459d-adb3-3b64436d0ef1@proxmox.com> <DE78AE8B-31EE-447A-962D-719F3C924700@apalrd.net> <680964c9-8847-4a11-8ac2-431fb8c876f2@proxmox.com> Feedback-ID: 38364418:user:proton X-Pm-Message-ID: 8245e63926bfbaeb31f0ac36f3720173c2f842be MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.000 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust 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_PASS -0.001 SPF: HELO matches SPF record SPF_PASS -0.001 SPF: sender matches SPF record X-Mailman-Approved-At: Fri, 04 Apr 2025 14:10:44 +0200 Given the delays in ifupdown2 development (the patches for vxlan IPv6 have = been sitting un-reviewed for 5 months now, and this is the 3rd patch set in= * 5 years * that has tried to fix this issue without being merged), can we= continue waiting years for them to fix? The most recent patch in ifupdown2 does not modify the names of the attribu= tes, so going forward with this patch in PVE and updating pve-network accor= dingly will not cause rework in pve-network if ifupdown ever releases softw= are.=20 Andrew > On Mar 31, 2025, at 03:22, Stefan Hanreich <s.hanreich@proxmox.com> wrote= : >=20 > On 3/31/25 06:45, Andrew wrote: >> Just noticed I didn=E2=80=99t reply to this before - the patch set in if= updown2 does not actually address IPv6 local tunnel IPs at all. >=20 > 3.9 itself doesn't, but 3.10 should contain the respective patches >=20 --===============0586815953785964462== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel --===============0586815953785964462==--