You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Is it possible to allocate an address by prefix role?
Example:
We have a number of non contiguous prefixes as "containers" assigned a particular role (e.g framed addresses for broadband users).
Is it possible to allocate an address by role rather than specific parent prefix ?
(i.e we don't care which prefix it is allocated from so long as that prefix has a particular role)
2. Is it possible to add constraints to a prefix role or prefix ?
Building on the above example, would it be possible to limit the child prefix size?
In this example, limiting to /32 only.
3. When allocating an address, is there any logic applied to find the smallest available gap ?
Example:
192.0.2.0/24
192.0.2.0/26 - Allocated
192.0.2.96/27 - Allocated
If we wanted a a /27 allocation, would it assign 192.0.2.64/27 or 192.0.2.128/27 ?
The former being preferable otherwise we are breaking up a perfectly good contiguous /25 when a perfectly sized block already exists.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
Couple of questions.
1. Is it possible to allocate an address by prefix role?
Example:
We have a number of non contiguous prefixes as "containers" assigned a particular role (e.g framed addresses for broadband users).
Is it possible to allocate an address by role rather than specific parent prefix ?
(i.e we don't care which prefix it is allocated from so long as that prefix has a particular role)
2. Is it possible to add constraints to a prefix role or prefix ?
Building on the above example, would it be possible to limit the child prefix size?
In this example, limiting to /32 only.
3. When allocating an address, is there any logic applied to find the smallest available gap ?
Example:
If we wanted a a /27 allocation, would it assign 192.0.2.64/27 or 192.0.2.128/27 ?
The former being preferable otherwise we are breaking up a perfectly good contiguous /25 when a perfectly sized block already exists.
Beta Was this translation helpful? Give feedback.
All reactions