From: Alex Goodkind via pve-devel <pve-devel@lists.proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Alex Goodkind <alex@goodkind.io>,
pve-devel@lists.proxmox.com, tarick@bedeir.com
Subject: Re: [pve-devel] [PATCH container 1/1] fix #5538: network: enable accept_ra for DHCPv6 configurations
Date: Tue, 11 Nov 2025 17:55:33 -0800 [thread overview]
Message-ID: <mailman.956.1762912558.362.pve-devel@lists.proxmox.com> (raw)
In-Reply-To: <CAAbO5hZ4SzcQRivyJC7tompikRMESgE+FJincNX7hryjY2TyHA@mail.gmail.com>
[-- Attachment #1: Type: message/rfc822, Size: 6146 bytes --]
From: Alex Goodkind <alex@goodkind.io>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: pve-devel@lists.proxmox.com, tarick@bedeir.com
Subject: Re: [PATCH container 1/1] fix #5538: network: enable accept_ra for DHCPv6 configurations
Date: Tue, 11 Nov 2025 17:55:33 -0800
Message-ID: <CAAbO5hapcJjpJ-tzEY+HtuX--fJsdcr0DWOBMpUq3MzcDmzZ_w@mail.gmail.com>
What happens from here in terms of getting this merged?
On Tue, Nov 11, 2025 at 09:02 Alex Goodkind <alex@goodkind.io> wrote:
> No problem, just sent the signed individual CLA to office@proxmox.com
>
> On Tue, Nov 11, 2025 at 07:46 Thomas Lamprecht <t.lamprecht@proxmox.com>
> wrote:
>
>> Am 11.11.25 um 08:14 schrieb Alex Goodkind:
>> > DHCPv6 requires Router Advertisements to function as specified in
>> > the IPv6 standard. Previously, accept_ra was only enabled for 'auto'
>> > mode, causing DHCPv6 configurations to fail when RAs were needed.
>> >
>> > Enable accept_ra for both 'auto' and 'dhcp' IPv6 modes.
>> >
>>
>> Many thanks for your patch, looks alright.
>>
>> Would you mind sending in a signed CLA [0] for this? I know the change
>> itself
>> is relatively trivial, but we rather want to stay on the safe side here.
>>
>> [0]:
>> https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright
>>
>>
>>
>>
[-- 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
next prev parent reply other threads:[~2025-11-12 1:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251111071450.10188-1-alex@goodkind.io>
2025-11-11 7:14 ` Alex Goodkind via pve-devel
2025-11-11 11:50 ` Gabriel Goller
2025-11-12 7:57 ` [pve-devel] applied: " Thomas Lamprecht
[not found] ` <20251111071450.10188-2-alex@goodkind.io>
2025-11-11 15:46 ` [pve-devel] " Thomas Lamprecht
2025-11-11 17:02 ` Alex Goodkind via pve-devel
[not found] ` <CAAbO5hZ4SzcQRivyJC7tompikRMESgE+FJincNX7hryjY2TyHA@mail.gmail.com>
2025-11-12 1:55 ` Alex Goodkind via pve-devel [this message]
2025-11-13 13:05 ` Gabriel Goller
2025-11-13 14:40 ` Alex Goodkind 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.956.1762912558.362.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=alex@goodkind.io \
--cc=t.lamprecht@proxmox.com \
--cc=tarick@bedeir.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