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

allow creation of container and subnet of the same prefix and length #264

Open
miesi opened this issue Sep 6, 2023 · 2 comments
Open

allow creation of container and subnet of the same prefix and length #264

miesi opened this issue Sep 6, 2023 · 2 comments

Comments

@miesi
Copy link
Contributor

miesi commented Sep 6, 2023

Now a days /24 prefixes/allocations are quiet common and configured as /24 on router interfaces.

currently there are two bad options:

  • do two /25 subnets in a /24 container (but this breaks "document in DIM what is configured on the irb")
  • do a /23 container with a comment that it is just a /24 and do a /24 subnet in it (breaks "document reality")

write tests
change the database constraint
modify code to allow this only for containers and subnets

@TheRealBecks
Copy link

I found the exception in this line

@miesi What do you think we want to achieve? Do we want to be able to...:

  1. Always be able to create subnets of the same size as the parent container?
  2. Only be able to create a subnet of the same size as the parent container if the parent container has the attribute ORIGIN-LIR?

@miesi
Copy link
Contributor Author

miesi commented Oct 26, 2023

having two objects at the same prefix/length breaks the show command which shall only display one object e.g. show ipblock
breaks also the api.

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

2 participants