Since this only has an effect on applying the configuration, users
will still need to reapply the configuration when an interface changes
names / altnames. In order to add full altname support for IS-IS,
altname support would need to be implemented in FRR.
Signed-off-by: Stefan Hanreich <s.hanre...@proxmox.com>
---
Notes:
Gabriel is currently working on altname support in FRR [1]
[1] https://github.com/FRRouting/frr/pull/19156
src/PVE/Network/SDN/Controllers/IsisPlugin.pm | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/src/PVE/Network/SDN/Controllers/IsisPlugin.pm
b/src/PVE/Network/SDN/Controllers/IsisPlugin.pm
index 6e3574d..0ef9fb9 100644
--- a/src/PVE/Network/SDN/Controllers/IsisPlugin.pm
+++ b/src/PVE/Network/SDN/Controllers/IsisPlugin.pm
@@ -80,9 +80,12 @@ sub generate_controller_config {
my @iface_config = ("ip router isis $isis_domain");
+ my $altnames = PVE::Network::altname_mapping();
+
my @ifaces = PVE::Tools::split_list($isis_ifaces);
for my $iface (sort @ifaces) {
- push(@{ $config->{frr_interfaces}->{$iface} }, @iface_config);
+ my $iface_name = $altnames->{$iface} // $iface;
+ push(@{ $config->{frr_interfaces}->{$iface_name} }, @iface_config);
}
return $config;
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
