SDN VLAN zone with IPAM and DHCP
- Thread starter PSz
- Start date
Currently not, but support for this is already on the mailinglist [1] and will be added soon.
https://lists.proxmox.com/pipermail/pve-devel/2023-December/061136.html
https://lists.proxmox.com/pipermail/pve-devel/2023-December/061136.html
No we don't have that currently. We have some conceptual issues, particularly with VLAN / QinQ / VXLAN zones that need to be ironed out / considered before we can release it - sorry. We'd rather get this 100% right, than delivering a half-working solution that causes issues.
PVE 9 was released. I may ask, if there may be any news (maybe for PVE 9.1) on planned progress for SDN with automatic DHCP for VLAN zones, hopefully?
Am currently on PVE9 and ran into the same vlan SDN not having DHCP. This grinds SDN functionality/usability to a halt for me as Simple zones have DHCP but have no vlan control or from what I hear inter-cluster support, but Vlan zones do not have DHCP. I am either stuck with a simple zone and no control of where that traffic ends up on the trunk, or a VLAN zone that has no DHCP making server provisioning that much harder.
Might I ask what kind of issues enabling dhcp on the VLAN zone would cause and why it's still not an available option in more configs than the simple zone?
Might I ask what kind of issues enabling dhcp on the VLAN zone would cause and why it's still not an available option in more configs than the simple zone?
Main issue is that every host would need a unique IP in the VNet, which currently isn't possible with how the VNets / Subnets are designed. There are some weird hacks with specific arp_ignore settings, that we'd rather not do. There's currently no one working on this due to shifting priorities, so the easiest way would be to just set up a virtual/physical pfsense or even just a simple dhcp server in a container that handles DHCP.
Hmm, okay that makes sense. I ended up just giving each customer a vlan on our agg switch, and making a vlan vnet for each vlan on said agg where we configure dhcp. It's more config points then is optimal but is the only way to enforce a customer uses the right network and still gives them dhcp.