I assume you mean to expland or join network blocks,
example:
current 10.0.0.0/24
expand 10.0.0.0/24 to 10.0.0.0/22
This would move all networks from 10.0.0.0/24 to 10.0.0.0/22.
Is this what you are looking for?
Thanks,
mearls
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2007-03-19
Logged In: YES
user_id=1586624
Originator: YES
Yes that should in theory do the trick.
here is how i describe it
Consider though, that one can make a CIDR 192.168.0.0/22
add prefix 192.168.0
add prefix 192.168.1
add prefix 192.168.2
add prefix 192.168.3
then one day your network grew, and you realized you planned the ip database poorly, and you have no place to put prefix 192.168.4
So you create CIDR 192.168.0.0/16
add prefix 192.168.4
This results in having two trees. 192.168.0.0/22 with 4 prefixes, and 192.168.0.0/16 with one prefix that "could" hold the prefixes from 192.168.0.0/22. You can even create a matching prefix in 192.168.0.0/16 with the same prefixes in 192.168.0.0/22. That is what we have done and then just start manually moving data from one CIDR to the other CIDR. Once done, we delete the empty CIDR that was to small.
If it was possible to just "move" the prefix to its neighboring compatiable CIDR, that is how I would imagine it to work. However what you described may work as well, but might take some thinking ahead on what the result will be when you try to expand or join as you say.
i realize all of the above may or may not be realistic to the coding. all i am trying to do is just describe the situation as best as i can. even if it can not be realistically done, that's all i'd really want to know as long as you understand what the main question is.
love the program. it's helped out our isp tons.
-Kreg
-Kreg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=386949
Originator: NO
Hi Kreg,
I assume you mean to expland or join network blocks,
example:
current 10.0.0.0/24
expand 10.0.0.0/24 to 10.0.0.0/22
This would move all networks from 10.0.0.0/24 to 10.0.0.0/22.
Is this what you are looking for?
Thanks,
mearls
Logged In: YES
user_id=1586624
Originator: YES
Yes that should in theory do the trick.
here is how i describe it
Consider though, that one can make a CIDR 192.168.0.0/22
add prefix 192.168.0
add prefix 192.168.1
add prefix 192.168.2
add prefix 192.168.3
then one day your network grew, and you realized you planned the ip database poorly, and you have no place to put prefix 192.168.4
So you create CIDR 192.168.0.0/16
add prefix 192.168.4
This results in having two trees. 192.168.0.0/22 with 4 prefixes, and 192.168.0.0/16 with one prefix that "could" hold the prefixes from 192.168.0.0/22. You can even create a matching prefix in 192.168.0.0/16 with the same prefixes in 192.168.0.0/22. That is what we have done and then just start manually moving data from one CIDR to the other CIDR. Once done, we delete the empty CIDR that was to small.
If it was possible to just "move" the prefix to its neighboring compatiable CIDR, that is how I would imagine it to work. However what you described may work as well, but might take some thinking ahead on what the result will be when you try to expand or join as you say.
i realize all of the above may or may not be realistic to the coding. all i am trying to do is just describe the situation as best as i can. even if it can not be realistically done, that's all i'd really want to know as long as you understand what the main question is.
love the program. it's helped out our isp tons.
-Kreg
-Kreg