From: Lou Lecrivain via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Lou Lecrivain <lou.lecrivain@wdz.de>
Subject: [pve-devel] SPAM: [PATCH pve-network v2 0/4] dhcp: always generate dhcp-range
Date: Mon, 9 Dec 2024 12:31:54 +0100 [thread overview]
Message-ID: <mailman.90.1733743975.332.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4979 bytes --]
From: Lou Lecrivain <lou.lecrivain@wdz.de>
To: pve-devel@lists.proxmox.com
Subject: SPAM: [PATCH pve-network v2 0/4] dhcp: always generate dhcp-range
Date: Mon, 9 Dec 2024 12:31:54 +0100
Message-ID: <20241209113158.7343-1-lou.lecrivain@wdz.de>
Second version of the patch, changes made as seen with Stefan.
this patch series re-enables a previously disabled code path in order to
allow IP allocation directly from a prefix when no DHCP ranges are
configured for a subnet.
MfG
--
Lou Lecrivain
WDZ GmbH
Lou Lecrivain (4):
vnet: do not skip if no range is defined, ask for allocation inside
prefix instead
dhcp: always generate dhcp-range for dnsmasq
fix: register details in pve ipam db for add_next_freeip
update tests following changes to behaviour: - allocating IPs also
when prefix-only - PVE IPAM register details for every allocation
strategy
src/PVE/Network/SDN/Dhcp.pm | 3 ++-
src/PVE/Network/SDN/Dhcp/Dnsmasq.pm | 23 ++++++++++-------------
src/PVE/Network/SDN/Ipams/PVEPlugin.pm | 6 +++++-
src/PVE/Network/SDN/Vnets.pm | 3 +--
src/test/run_test_subnets.pl | 24 +++++++++++++++++++++---
src/test/run_test_vnets_blackbox.pl | 6 ++----
6 files changed, 41 insertions(+), 24 deletions(-)
--
2.39.5
[-- 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:[~2024-12-09 11:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.90.1733743975.332.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=lou.lecrivain@wdz.de \
/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