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 39BA51FF16E for <inbox@lore.proxmox.com>; Mon, 31 Mar 2025 13:57:58 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 8C5022007; Mon, 31 Mar 2025 13:57:47 +0200 (CEST) Date: Mon, 31 Mar 2025 04:45:16 +0000 To: Stefan Hanreich <s.hanreich@proxmox.com> In-Reply-To: <d5f5ac3a-bc06-459d-adb3-3b64436d0ef1@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> X-Mailman-Approved-At: Mon, 31 Mar 2025 13:57:46 +0200 MIME-Version: 1.0 Message-ID: <mailman.347.1743422266.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="===============1813670157137062430==" Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> --===============1813670157137062430== 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 648A5CC926 for <pve-devel@lists.proxmox.com>; Mon, 31 Mar 2025 06:53:17 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 3E2243B717 for <pve-devel@lists.proxmox.com>; Mon, 31 Mar 2025 06:52:47 +0200 (CEST) Received: from mail-41103.protonmail.ch (mail-41103.protonmail.ch [185.70.41.103]) (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 06:52:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apalrd.net; s=protonmail2; t=1743396319; x=1743655519; bh=k4JSsGhANQWwe3yoPDZfjnOl3GhP2z4QpWJCy2Dd5NE=; 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=BdblFTKou4D4IWBaKOm23GXo5qepsmyRG5pMMkEKI5GlLQoKFO0uAKuqSHgoI/SRi kwXbVhk0CiMX+SVfR0qS8jbDoF8pn3P2TPXzH2NNHgK6NW2LryJ/Jn6Cevpb+kNrYX MYSqiIyYHZSq61mWN8NOAip+JjZ+ubfiG1Bd/5IeRAPmccGtThgd/ZCw/k0ZoHFk2o MDMogp25fqmvEhjwer/NyY/62TqFDfCX/nHeWk78hQurqEPWcfVuGFhVDpbU5SLh8u G9/IrBQC83J46dqnggjNcMyeR/oe+nHcKrAtyNChAqjXCTOkqx6UVrSIwTFkmiJa+8 eCIDaPCqgTIsQ== Date: Mon, 31 Mar 2025 04:45:16 +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: <DE78AE8B-31EE-447A-962D-719F3C924700@apalrd.net> In-Reply-To: <d5f5ac3a-bc06-459d-adb3-3b64436d0ef1@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> Feedback-ID: 38364418:user:proton X-Pm-Message-ID: 93d157316f69a5ad65939b06e1fe4922eef165c5 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: Mon, 31 Mar 2025 13:57:46 +0200 Just noticed I didn=E2=80=99t reply to this before - the patch set in ifupd= own2 does not actually address IPv6 local tunnel IPs at all. > On Jan 23, 2025, at 04:26, Stefan Hanreich <s.hanreich@proxmox.com> wrote= : >=20 > Hi, it seems like ifupdown2 will be merging a PR for VXLAN IPv6 support > in the near future [1]. Hence why I think we should be holding off on > this, until we know which solution (there are several PRs for this > actually) they merge. Otherwise we run into the problem of having > incompatible / custom settings for this. >=20 > [1] > https://github.com/CumulusNetworks/ifupdown2/pull/318#issuecomment-254194= 7074 >=20 --===============1813670157137062430== 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 --===============1813670157137062430==--