public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Stefan Lendl <s.lendl@proxmox.com>
To: Stefan Hanreich <s.hanreich@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH pve-network] ipam: improve update / delete behavior
Date: Wed, 22 Nov 2023 14:45:30 +0100	[thread overview]
Message-ID: <87ttpdzyth.fsf@gmail.com> (raw)
In-Reply-To: <20231122122951.215905-1-s.hanreich@proxmox.com>


I tested this with multiple Subnets:

It works if MAC is 1x in IPv4 subnet and 1x in IPv6 subnet.
- updating either IPv4 or IPv6
  - other one persists
- update IPv4 to be in another subnet
  - auto-selects the new subnet

Encountered issues:
- change IPv4 to IPv6 (and vice versa)
> can't find any subnet for ip at /usr/share/perl5/PVE/Network/SDN/Subnets.pm line 114. (500)

- When manually creating a mapping, there is no way to set a VMID (but works)

- consecutive updating the mapping does not work
> vmid: type check ('integer') failed - got ''

- Updates to the IPAM mapping do not propagate to dnsmasq's ethers file
  - also not after Reload
  - In comparison `qm set 109 --net1 model=virtio,bridge=dhcpnat3` will
    update ethers immediately




      parent reply	other threads:[~2023-11-22 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 12:29 Stefan Hanreich
2023-11-22 12:29 ` [pve-devel] [PATCH pve-manager] ipam: send ip to delete endpoint Stefan Hanreich
2023-11-22 13:36   ` [pve-devel] applied: " Thomas Lamprecht
2023-11-22 13:18 ` [pve-devel] [PATCH pve-network] ipam: improve update / delete behavior Thomas Lamprecht
     [not found]   ` <55cfaf0f-b4c9-4698-89a5-faaf8ca6a000@proxmox.com>
2023-11-22 13:26     ` [pve-devel] applied: " Thomas Lamprecht
2023-11-22 13:45 ` Stefan Lendl [this message]

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=87ttpdzyth.fsf@gmail.com \
    --to=s.lendl@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --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