Bug #8751
closed
Added by Marc Planquart almost 7 years ago.
Updated almost 6 years ago.
Description
Problem1 (bug):
Create prefix-list in the UI
Check prefix-list in vtysh
prefix-list doesn't exist
Note: prefix list is showing up incomplete in zebra.conf (only name + description)
Problem2 (feature):
Flag to specify an ipv6 prefix-list is missing
End to end requirement:
Ability to create an ipv6 prefix list and to add it to a route map
Problem3 (feature):
Unable to edit pre-defined OSPF6 prefix-lists and route MAPs
Issues exist in both 2.4.4 and 2.4.3-1.
I found the issue. This is not a bug but more a UI validation issue.
When things are entered as expected by FRR, it works.
Admins, feel free to close this bug!
Sorry for the inconvenience.
If the UI validation is wrong that could still be a bug. What did it allow you to enter incorrectly, and where? It would help to see the invalid vs valid input and know what page/field it was.
To re-create the problem, I entered a network with a prefix of X, a minimum prefix equal to X and a maximum prefix equal to Y. For example 10.198.0.0/16 ge 16 le 24.
The minimum prefix has to be at least X+1 otherwise the entry doesn't end up in vtysh (but is showing up correctly in Zebra.conf).
Now, if you omit the prefix when entering the network and only specify a min and a max prefix, the entry doesn't even show up in zebra.conf (I tried all kinds of permutations before I found out what worked).
Additional note:
I'd remove the following auto generated entry in the conf file of OSPF6
ipv6 prefix-list dnr6-list permit any
This ends up as:
ipv6 prefix-list dnr6-list seq 5 permit any in vtysh
It would be better for this to show up in Zebra.conf with a sequence number (so it can be modified)
Thanks.
- Status changed from New to Feedback
- % Done changed from 0 to 100
I added some input validation for prefix lists in the latest version of the FRR package. (pkg version 0.5.0)
- Status changed from Feedback to Resolved
Also available in: Atom
PDF