On Fri, 07 Nov 2025 15:31:20 +0100, Stefan Hanreich wrote:
> When parsing the vnet.cfg config file we also want to get the tag
> (vni or vlan). We need this so that we can lookup the vni of the passed
> vnet on the status api call. We need the vni so that we can filter the
> frr output.
>
> In the future we would probably want to do this better with an enum per
> vnet type and parse all possible options.
>
> [...]
Applied, thanks!
[4/7] ve-config: add optional tag property to vnet
commit: 899ad0970a26d127b402205e256a22d610707d24
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
