Re: [PATCH manager] ui: sdn: fabrics: require IPv4 prefix on fabrics without IPv6 support

[Gabriel Goller <g.goller@proxmox.com>]

On 20.05.2026 14:57, Dominik Csapak wrote:
> because i just looked at this while trying to make a similar change:
> 
> is the reverse not also possible? so ipv6-only fabrics?

not currently. We'll have to see how we implement ospfv3 (ospf with ipv6
support) in the future (if that is a separate ipv6-only fabric or integrate into
the existing ospf).

> i noticed that when i add a fabric i have to enter *either* a
> ipv4 or ipv6 address, but the subsequent node edit windows always
> show both (even thouh i didn't configure an ipv4 address)
> 
> not sure if that makes sense?

Yeah, that's a bit weird. Don't know if we can easily fix this and hide the
other input if the fabrics prefix of that address family is empty?

> On 5/20/26 2:51 PM, Gabriel Goller wrote:
> > For fabricrs that only support IPv4, the IPv4 prefix is the only
> > available prefix field. Mark it as mandatory in that case while keeping
> > it optional for fabric types that also support IPv6.
> > 
> > Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> > ---
> >   www/manager6/sdn/fabrics/FabricEdit.js | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/www/manager6/sdn/fabrics/FabricEdit.js b/www/manager6/sdn/fabrics/FabricEdit.js
> > index 1f7bab362075..760925c50b95 100644
> > --- a/www/manager6/sdn/fabrics/FabricEdit.js
> > +++ b/www/manager6/sdn/fabrics/FabricEdit.js
> > @@ -60,7 +60,7 @@ Ext.define('PVE.sdn.Fabric.Fabric.Edit', {
> >                   fieldLabel: gettext('IPv4 Prefix'),
> >                   labelWidth: 120,
> >                   name: 'ip_prefix',
> > -                allowBlank: true,
> > +                allowBlank: me.hasIpv6Support,
> >                   skipEmptyText: true,
> >                   deleteEmpty: '{!isCreate}',
> >               });
>