IP range object

Hello,

Do you think adding the fields you've listed to the existing IP Address List entry would be a good solution for your scenario? I feel like adding a new type of entry would make it more difficult for users to store their required information, as they would have to split it between two different entries.

> This could then be auto filled with objects within a pre-defined folder? (like a customer or company site)
Could you describe what you're looking for with this? Maybe showing pictures of how you are currently organising your folders and entries, and how this would come into it, would help me understand.

Regards,

Hello,

Do you think adding the fields you've listed to the existing IP Address List entry would be a good solution for your scenario? I feel like adding a new type of entry would make it more difficult for users to store their required information, as they would have to split it between two different entries.

If you can give me the option to customize the columns then I would also be content with that.

> This could then be auto filled with objects within a pre-defined folder? (like a customer or company site)
Could you describe what you're looking for with this? Maybe showing pictures of how you are currently organising your folders and entries, and how this would come into it, would help me understand.

Regards,

If we could fill the IP host list asset with all IP's found within folder es_santbois then it would satisfy our need for automation on site level.
It would create a good overview of what IP's are already assigned. (static)
Folder structure looks something like this:

Hello,

Have also been looking for a way to transfer IP/VLAN info from a bunch of wiki pages into RDM. Currently in Wiki there is a parent list of VLAN's with their associated ID, subnet, gateway, DHCP enabled, comments etc. Each VLAN also has a dedicated child/sub-page that contains a list of all the hosts and IP's within a specific VLAN/subnet. With this setup it is very convenient to be able browse, search. navigate via hyperlinks to the subpages.

In order to replicate this into RDM, the following may be required.
1) A customizable list/table type entry in RDM that can be used for multiple sets of data (i.e. one for VLAN's and another for IP's)
2) Support for linking other entries within a list. For example, if row1 in a table/list is for VLAN1, there is a clickable link that will open up another list entry containing the associated IP's/hosts.
3) Ability to reference attributes of other entries in a list. For example, populating a list with links to other host (or system inventory) entries in RDM, and having the list display a customizable set of attributes from each linked entry such its IP address. There is sort of a round about way to do this allready using a custom report entry that references an IP Address list entry to get a list of host (or system inventory) entries to query attributes from. It would be simpler and easier to manage if there was a list type entry that contained host objects, and then displayed specific attributes from each.
4) When referencing attributes of other entries, an ability to filter the returned data when there are multiple values. For example, a system inventory report entry of a multi-homed host would contain muliple IP addresses in different VLANs. When viewing an IP Address list for a specific VLAN, only the IP address pertaining to that VLAN should be listed.
5) PowerShell support to modify the contents of the lists. This would allow enumerating existing entries within RDM and dynamically populating the lists with references to other entries and/or asset/inventory data

Another use case for customizable lists, maybe mapping network switch ports to IP's/hosts. If it were possible to create a custom list/table of switch ports in RDM, then in theory a dump of the arp table from the switch could be used to reconcile which hosts/ip's/mac's are connected to which port/s, and that info could be conveniently presented as an entry in RDM.

Please let me know if you would like more info.

Thanks
Joe

Hello,

Thank you both for the additional information. We will have to give some thought as to how we want to implement these suggestions in RDM, as this is something bigger than I first thought. We appreciate your feedback!

Regards,

Hello,

With our 2025.1 release, we've added a bunch of new fields for the IP Address List object as well as any entry's Asset -> Network section. You can download it here: https://devolutions.net/remote-desktop-manager/download/
Let us know if you have any additional feedback regarding this addition.

Regards,

Hello Hubert,

Thank you for the enhancements to the IP address list entry type. After experimenting with the new capability, the following feedback comes to mind:
1) The import/synchronize capability is very convenient
2) With RDM 2025.1.34 the synchronizer doesn't seem to pulling values from an entries Asset properties. For example, if IP address and VLAN are defined on a host entries 'asset page', the sync only retrieves the hostname from the entries 'general page'
3) The duplicate detection could be improved to automatically exclude entries where the 'hostname' attribute is set to inherited, because such entries infer a parent entry already has a unique hostname defined
4) A single table for all the network address related attributes may not scale well, along with data duplication and redundant/empty fields for many line items. For example, 'DHCP Server' and 'IP Range' attributes are not really relevant to an entry whose host uses a single static IP. Perhaps an interconnected entry type model would alleviate this, for example, separate RDM entry types for IP Addresses and VLAN's which can reference/link to each other. In such a scenario, a host entry could link to an IP entry which links to a VLAN entry to which subnet/dhcp range entries are linked, each of which maintains their own relevant list of attributes/properties. It would be great to see RDM reach a point where is comparable to what NetBox can do for the granular mapping of interconnected network addressing components (i.e. IPAddress - NetBox OSS).

Please let me know if would like any additional info.

Thanks
Joe

Hey Joe, thanks for the feedback!

2) With RDM 2025.1.34 the synchronizer doesn't seem to pulling values from an entries Asset properties. For example, if IP address and VLAN are defined on a host entries 'asset page', the sync only retrieves the hostname from the entries 'general page'

How would you expect RDM to act in a situation where all three fields are filled? A way to choose which of these fields to use per found entry? A priority system where Host->IP->VLAN is taken? We'd have to figure out how to best allow this in our UI if we want to choose per-entry.

3) The duplicate detection could be improved to automatically exclude entries where the 'hostname' attribute is set to inherited, because such entries infer a parent entry already has a unique hostname defined

That's a good point. This is probably just not a scenario we took into account when implementing the feature. I'll open a bug ticket for this.

For your fourth point, we'll have to think about how to implement this kind of functionality in our products. We've had a request in the past to be able to link any entry with any other, not to enable any particular feature, but to keep a logical link between them. Maybe this is something that could help in this case.

Regards,

Hi Hubert,

Thanks.

For #2, ideally the synchronizer would populate/replicate all the network address details from an entry asset page into the different fields of a row in the Address List entry. One use case for the IP address list entry would be to identify address consumption/availability on a particular subnet/vlan, in which case a list of IP addresses would be required, as opposed to hostnames.

For #4, raising that point as the evolving asset/inventory capabilities of RDM have potential to replace other disparate systems used for documenting network infrastructure (i.e. wiki pages / spreadsheets listing addresses, cabling, vlans etc). While RDM can currently be used in that way to an extent for elementary network devices with a single IP/Nic, there are limitations when it comes to devices with multiple addresses, ports, vlans etc (i.e. a firewall /switch/gateway). These limitations can unfortunately be a blocker to consolidating network addressing inventory into RDM.

Please let me know if you would like any additional info.

Joe

Sorry about the delayed answer, it's been a busy week with the release of our 2025.2 beta.

For #2, ideally the synchronizer would populate/replicate all the network address details from an entry asset page into the different fields of a row in the Address List entry. One use case for the IP address list entry would be to identify address consumption/availability on a particular subnet/vlan, in which case a list of IP addresses would be required, as opposed to hostnames.

In your case then, would you need only the IP address when available? If that's the case then we can simply add an option when performing the sync to prioritise the IP from the Asset section over the Host. Maybe I'm not understanding your case properly. As for the VLAN, I believe it should already be imported. If it isn't, I think it's a bug, since the column is there in the IP address list entry.

Regards,

Hi Hubert,

No problem about the delay. With RDM 2025.1.38 it does now seem to be pulling the VLAN ID from the entry asset/networking page.

Regarding #2, the hostname attribute of an entry is valuable to have in the IP list, ideally there would be a separate column for the IP address retrieved the an entry's asset attributes.

Also I noticed a few other things:
5) When sub connections with the name set to $PARENT_NAME$ are synchronized to the IP address list, the variable is not resolved.
6) When $PARENT_HOST$ is being used in an entry hostname attribute, these entries should probably be automatically excluded like when the host is set to inherited.
7) Entries in the list are duplicated each time a resync is performed (even with the option to 'clear list' selected)

Please let me know if you would like any additional info.

Thanks
Joe

Thanks for the additional explanation. I'm glad the VLAN seems to be working now.

I'll open two separate tickets:

• One for points 5 through 7, which sound like bugs/minor improvements
• One for point 2, to add a field specific to the IP, so you can both have the host and IP. This ticket will probably have to wait for 2025.3 to make sure we synchronize properly with all our products and platforms

Have a nice weekend!

Regards,

sounds good, thanks Hubert

Hello,

We've fixed points 5 through 7. You can expect these changes with the release of 2025.1.40

Regards,

Hi Jafran,

Thanks, are these fixes in 2025.1.39 (released today), or the next one?

Joe

Hello Joe,

These fixes will be available in 2025.1.40.0 and above. This unfortunately did not make it into .39. We're hoping to release this version early next week.

Regards,

Hello,

We've added the IP field (to be populated from the entrie's Asset IP field) to the IP List objects. You can expect this with the upcoming 2025.3.2 version.

Regards,

That's great, thanks Jafran.

Joe

Hello,

Thank you for being so patient!

I'm letting you know that version 2025.3.17.0 of RDM is now available with this feature included.

Please let us know if this works or if you encounter any issues.

Best regards,