all lists on lists.proxmox.com
 help / color / mirror / Atom feed
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 0/2] fix #5949
Date: Thu, 28 Nov 2024 18:09:40 +0100	[thread overview]
Message-ID: <mailman.831.1732813825.391.pve-devel@lists.proxmox.com> (raw)

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

From: Lou Lecrivain <lou.lecrivain@wdz.de>
To: pve-devel@lists.proxmox.com
Subject: SPAM: [PATCH pve-network 0/2] fix #5949
Date: Thu, 28 Nov 2024 18:09:40 +0100
Message-ID: <20241128170942.4717-1-lou.lecrivain@wdz.de>

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.

2nd commit is a workaround for dnsmasq crash when a dhcp lease is
updated via dbus and no dhcp-range is configured.

The whole patch series requires #5946 patch to work.

MfG
--
Lou Lecrivain
WDZ GmbH

Lou Lecrivain (2):
  vnet: do not skip if no range is defined, ask for allocation inside
    prefix instead
  dhcp: generate dhcp-range for dnsmasq even when no dhcp_ranges exist

 src/PVE/Network/SDN/Dhcp.pm         | 6 ++++--
 src/PVE/Network/SDN/Dhcp/Dnsmasq.pm | 5 ++++-
 src/PVE/Network/SDN/Dhcp/Plugin.pm  | 2 +-
 src/PVE/Network/SDN/Vnets.pm        | 4 ++--
 4 files changed, 11 insertions(+), 6 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-11-28 17:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28 17:09 Lou Lecrivain via pve-devel [this message]
2024-12-05 15:49 ` Stefan Hanreich
2024-12-05 15:56   ` Lou Lecrivain via pve-devel
2024-12-05 16:50 ` Stefan Hanreich

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.831.1732813825.391.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal