Hi, thank you for the super fast answer. Good to know this is already solved, we will be waiting for the new release.
Best regards Stefan Alfers Am Di., 30. Jan. 2024 um 11:56 Uhr schrieb Wei ZHOU <ustcweiz...@gmail.com>: > Hi, > > This issue has been resolved by > https://github.com/apache/cloudstack/pull/8122 > > It will be included in the coming 4.19.0.0 release (and 4.18.2.0) > > -Wei > > On Tue, 30 Jan 2024 at 11:41, Stefan Alfers <s...@23m.com.invalid> wrote: > > > Hi all, > > > > we are in the process of setting up Cloudstack and have hit a roadblock > > with how private L2 networks are allocated. > > > > It is my understanding that during creation of a zone you can specify a > > range of VLAN/VNI numbers, so that users can then later create private > > networks with an automatically assigned ID and use them for communication > > between VMs. > > Now when we try to edit the Physical Network belonging to the zone > > Cloudstack returns an error message: > > (Physical Network 1) Can't add vnet range to the physical network in the > > zone that supports Advanced network, Security Group enabled: true > > > > I can't seem to find any documentation on this limitation or why it > exists. > > What I don't understand is that I can create a Guest network of type L2 > and > > specify vxlan://20001 as the ID, successfully attach it to VMs and pass > > traffic through it. Works perfectly fine. > > This method of manual creation is understandably only available to admin > > users. > > > > We're using CloudStack 4.18.1.0. Any advice would be appreciated. > > > > Best regards > > > > Stefan Alfers > > > > -- > > 23M GmbH Johann-Krane-Weg 18 DE-48149 Münster Web: 23M.com Tel.: +49 251 > > 933 944 0 > > > -- 23M GmbH Johann-Krane-Weg 18 DE-48149 Münster Web: 23M.com Tel.: +49 251 933 944 0
