It would be nice if the IP addresses from assets were automatically added to the IP address list. Currently, for example, the technician has to enter the IP address of a new device into the “Network devices” asset and then into the IP address list. This is often forgotten, especially when changes are made. This would be a really great function if the fields could be linked in this way and also updated dynamically.

The other requested functions, such as VLAN, DNS and DHCP servers and ranges, gateways, etc. are also absolutely essential.

I hope that this can be implemented soon :-)

Networks was a great concept but completely lacks function. Adding VLAN Number would start making it functional, integrating with IPs on configurations/assets in the system (ability to turn on or off) would bring continuity to this.

Adding other things like DNS/DHCP Default gateway are nice in theory but are things that don't get updated as servers get replaced or things change.

Subnet (already have) and VLAN (need) are the core items that rarely change and would make this a valuable concept

Gateway would also be handy.

Also being able to reference these fields within an Asset Layout to appear on the front search table would be good so you don't have to click into each individual asset.

Being able to so set a DHCP range on a network would be ideal and we really need to be able to add VLAN. Working around it now with roles but that's not ideals.

And for IP addresses, add MAC, Switch and Port

Ability to customize the table properties/fields would be ideal. This would eliminate the need to create a separate LAN network page to include these items.

Absolutely! And for DHCP configuration would be nice to have a sort of "Bulk add" to add a bunch of IP addresses for DHCP pools.

Definitely need VLAN ID. Base port/network would be nice (Parent Network is kind of that, but seems more for routed subnets). A generic 'Zone' type/field (or custom field) as well

Please also add a field for zones and check it against the VLAN ID.

In every zone (for example: Datacenter, Inside, Outside, DMZ,...) a VLAN ID should only be allowed once. But users should be able to reuse ID's on other zones.

Zones would be also a great way to structure sites with many networks.

Example:

DATACENTER ZONE:

1-MANAGEMENT

5-SERVER-DC

6-SERVER-FILE

7-SERVER-ERP

8-SERVER-TERMINAL

10-BACKUP

IT-ZONE:

1-MANAGEMENT

5-LAN-CLIENT

6-LAN-PRINTER

8-LAN-VOIP

OT-ZONE:

1-MANAGEMENT

5-MACHINES-A

6-MACHINES-B

7-MACHINES-C

DMZ-ZONE:

1-MANAGEMENT

5-SERVER-FRONTENT

6-SERVER-BACKEND

7-SERVER-RAS

Agree!