Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

next_network for state=assigned #363

Open
aesposito91 opened this issue Jul 23, 2019 · 0 comments
Open

next_network for state=assigned #363

aesposito91 opened this issue Jul 23, 2019 · 0 comments

Comments

@aesposito91
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant