Closed ipspace closed 1 month ago
Optional idea (in case I get bored): validate the mutually-exclusive attributes. For example, you cannot use 'ipv4' or 'ipv6' in a prefix that has the 'pool' attribute.
Latest commit: |
60e33cb
|
Status: | ✅ Deploy successful! |
Preview URL: | https://20f28ece.netlab-release.pages.dev |
Branch Preview URL: | https://prefix.netlab-release.pages.dev |
This PR implements 'named prefixes' -- a dictionary of prefixes that can be used in 'links.prefix', 'vlans.prefix', validation code, and (future) prefix lists.
The named prefixes can be static (ipv4 and/or ipv6 subnets, optionally with allocation mechanism) or allocation from one of the addressing pools, in which case the named prefix serves as a mechanism to prevent data duplication