So, the ask is for all assigned IPs in a Network Container, regardless of how they're used, returned from a single query. For example, we may have 16 Class Cs in a /20 assigned to a particular location, which is then broken up into a combination of nested containers and leaf networks. There's a combination of types of objects, such as DHCP, hosts, A records (created outside hosts), reserved, and fixed addresses.
An example table is shown below, but the actual /20 contains over 100 networks and containers.
| 10.0.160.0/20 | Container |
| 10.0.160.0/21 | Container |
| 10.0.160.0/24 | Leaf |
| 10.0.161.0/24 | Container |
| 10.0.161.0/30 | Leaf |
| 10.0.161.104/29 | Leaf |
| 10.0.161.112/29 | Leaf |
| 10.0.161.12/30 | Leaf |
| 10.0.162.0/24 | Leaf |
| 10.0.174.0/24 | Container |
| 10.0.175.0/24 | Leaf |
The closest I've come is the following search, but it would require a lot of clean up to be useable.
https://10.250.8.12/wapi/v2.10/search?objtype=IPAMObjects&search_string~=209.182.1(6[0-9]|7[0-5])&_max_results=2000&_return_type=json-pretty
I mean, that's better than trying to create multiple requests or exporting each page from the GUI at a time, but what I really want is something like this (that actually works):
https://<GM>/wapi/v2.10/ipv4address?ip_address>=10.0.160.1&ip_address<=10.0.175.254&status=USED
This actually only ends up returning what's in the first leaf network, 10.0.160.0/24.
