Actions
Feature #16378
openAdd Option for ip ospf message-digest-key
Status:
New
Priority:
Normal
Assignee:
-
Category:
FRR
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Description
Currently, the FRR GUI does not have an option to define a message-digest-key for OSPFv2. The default behavior currently is to always use a digest key of 1. If a customer has anything but 1 defined on the OSPF neighbor for something like MD5 Hash, the customer cannot connect up to the neighbor for routing.
A GUI element should be added to define a digest key that defines this value via command "ip ospf message-digest-key"
No data to display
Actions