Rob, if you'll tell me which subnet that has "children" should be removed and which of those "children" should be kept, I'll make a note of the "children", delete them, delete the erroneous subnet, and add the "children" back in. Annoying, but it should take only a few minutes, less time and more productive than arguing about it on the mailing list.

It is the 44.137.24.0/22 subnet as I mentioned before. But be careful: those children are IPIP gateways and have that subnet registered in their gateway system. I'm sure when you delete them through the UI, the subnet will be deleted from their gateway as well. That is not good.

I wonder what the database structure is and if you could maybe just delete the record from the database without affecting the children. When there are all kinds of pointers back and forth between parent and child records, that would be something that needs to be fixed. It should be easy to add and delete subnet levels between existing ones, e.g. a new regional subnet between a country subnet and users. We are re-arranging things all the time as the network develops. Probably the subnets should just be stored neutrally, and the parent/child relationship should only be established at the time the records are retrieved for display. And deleting a subnet should not infer deleting everything that is in it, the contents should just be promoted to the next higher level.

Rob