On 08/04/2025 18:32, Stefan Hanreich wrote: > Fixes the issue of the FRR service getting started, but not enabled when > applying an SDN configuration and updates the docs to reflect the new > behavior.
- started with fresh ISO with sha256sum: 695c1c9b247e62d851d29d39c3e9399d3a15dd7c1bdca68b357b6bd578ee9925 - set up evpn controller and zone, clicked apply => frr.service is disabled but running - reboot => frr.service is not running - applied this patch, clicked apply => frr.service is now enabled and running - reboot => frr.service is running So this looks good to me. I was wondering whether enabling frr may have any side effects on existing setups, but since we only enable if we restart anyway, I don't think this should cause any issues. Consider this Tested-by: Friedrich Weber <f.we...@proxmox.com> _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel