Skip to content

next_network for state=assigned #363

@aesposito91

Description

@aesposito91

It appears that state=assigned and state=reserved are identified as busy states. I believe this implies that this block is not be further carved into smaller blocks.

That doesn't appear to be the case... The idea is this network is deployed as an exact-match of /22 and as such should not be carved w/ next_network, however should be able to be queried for next_address...

nsot networks list -c 10.48.60.0/22 +-------------------------------------------------------------------------------------------------------------------------+ | ID CIDR (Key) Is IP? IP Ver. Parent State Attributes | +-------------------------------------------------------------------------------------------------------------------------+ | 13801 10.48.60.0/22 False 4 10.48.0.0/18 assigned | +-------------------------------------------------------------------------------------------------------------------------+ nsot networks list -c 10.48.60.0/22 next_network -p 24 10.48.61.0/24

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions