public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Andrew via pve-devel <pve-devel@lists.proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>
Cc: Andrew <andrew@apalrd.net>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan
Date: Mon, 31 Mar 2025 04:45:16 +0000	[thread overview]
Message-ID: <mailman.347.1743422266.359.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <d5f5ac3a-bc06-459d-adb3-3b64436d0ef1@proxmox.com>

[-- Attachment #1: Type: message/rfc822, Size: 4619 bytes --]

From: Andrew <andrew@apalrd.net>
To: Stefan Hanreich <s.hanreich@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH ifupdown2 1/1] Correctly handle IPv6 addresses in vxlan
Date: Mon, 31 Mar 2025 04:45:16 +0000
Message-ID: <DE78AE8B-31EE-447A-962D-719F3C924700@apalrd.net>

Just noticed I didn’t reply to this before - the patch set in ifupdown2 does not actually address IPv6 local tunnel IPs at all.

> On Jan 23, 2025, at 04:26, Stefan Hanreich <s.hanreich@proxmox.com> wrote:
> 
> 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.
> 
> [1]
> https://github.com/CumulusNetworks/ifupdown2/pull/318#issuecomment-2541947074
> 




[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

  reply	other threads:[~2025-03-31 11:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20241008040109.322473-1-andrew@apalrd.net>
2024-10-08  4:01 ` apalrd via pve-devel
2025-01-23  9:26   ` Stefan Hanreich
2025-03-31  4:45     ` Andrew via pve-devel [this message]
     [not found]     ` <DE78AE8B-31EE-447A-962D-719F3C924700@apalrd.net>
2025-03-31  7:22       ` Stefan Hanreich
2025-03-31 14:38         ` Andrew via pve-devel
     [not found] ` <20241008040109.322473-2-andrew@apalrd.net>
2024-10-09 15:37   ` DERUMIER, Alexandre via pve-devel
     [not found]   ` <9045eca45de7aa50fd817fb9221cfa04c524ff19.camel@groupe-cyllene.com>
2024-10-09 16:55     ` Andrew via pve-devel
     [not found]     ` <17214981-4406-4100-AFF6-9F70E12E421B@apalrd.net>
2024-10-09 21:05       ` DERUMIER, Alexandre via pve-devel
     [not found]       ` <99349e23b9a957cdf81d5bf2fa8c6af9f6b24ad0.camel@groupe-cyllene.com>
2024-11-25 10:25         ` Stefan Hanreich
2024-11-25 15:09           ` Andrew via pve-devel

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=mailman.347.1743422266.359.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=andrew@apalrd.net \
    --cc=s.hanreich@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal