[Feature Request]: Get list of all network addresses used in controller

[dsm150]

🚀 Feature Summary

Get list of all network addresses used in controller

📝 Detailed Description

As I was able to understand, when creating a new network, the controller does not take into account the addresses of previously created networks, and can create another network with the same address as the existing one.
It would be ideal if each time the controller creates a new network, it would not give out the addresses of the previously created networks.

If this is labor-intensive to implement, it would be sufficient to at least be able to view the list of currently used network addresses.

If there is such a possibility and I have not found it, please help 🙏🏻

🎯 Use Case

No response

💡 Willing to Contribute

None

[sinamics]

you are correct. ztnet is selecting a random address when creating network.
one way to solve this is to use the network index and select a address based on that.

Example:

• Network 1 => 10.121.15.0
• Network 2 => 10.121.16.0
  ...

[dsm150]

That's understandable.
But how to view already issued addresses for existing networks in one list?
When assigning new ones, I would like to see which ones have already been issued.

[sinamics]

for that we need to store the address in db for each network and then do a lookup to get a list of used addresses.

[dsm150]

So now the addresses are not stored in the database?
If they are, how can I query the database?
It would be great if clicking on "Total networks" would display a list of networks and their addresses.

[sinamics]

network ip is not stored in db.

ztnet/prisma/schema.prisma

Line 93 in 52bd328

model network {

[dsm150]

At the moment, to find out the addresses of all networks, you have to manually go through each network and write in notepad...
With hundreds of networks, this will become impossible....

Is it possible to do something about this in the future?

[sinamics]

Yes, i will add a list of used ip`s in the controller page and the "Ip Assignment" section for each network.
Another nice feature would be to inform users that X network uses the same address as a notification.

[dsm150]

Looking forward to the update. It will be excellent!

[sinamics]

@dsm150 would this be sufficient enough?

[sinamics]

merged these changes.
I will add more notifications in the network ip assignement section later on when i get time.

[dsm150]

@dsm150 would this be sufficient enough?

This is already good, but yes, it would be much more convenient if a unique range was generated when creating a new network, or if you could select a range given the existing ones.