Custom Entry

Hello,

Thank you for reaching out regarding this matter.

If I understand correctly, you would like to add devices with multiple IP addresses. Could you please let me know which method or entry you’ve already tried? That way, I can avoid suggesting something you’ve already attempted.

Best regards,

I've tried adding a new entry using the IT asset/Firewall type. When I look at the network or hardware tabs neither of them seems to have a way to create things like eth0 = x.x.x.x/24, eth1=y.y.y.y/16, etc for each interface. The other thing that matters is ISP information. I would like to store the details of the connections and things like what the ISP support # is, contract id, circuit id, telcom room/location, term of contract, etc and associate those to the firewall entries (pref associate them to the actual interface they connect to).

Make sense?

Hello,
Thank you for your response.
I will verify with the developers whether this is possible and get back to you shortly.
Best regards,

Hello,
Thank you for your response.
I will verify with the developers whether this is possible and get back to you shortly.
Best regards,

@Tommy Sanders
Hey Tommy,

Did you get any response on this?

Hello,

Apologies for the delayed response.

There are a few options you could consider:

• Use the “Other (custom)” information entry, which supports any number of fields and allows full customization.
• Combine multiple entries such as Host, Firewall, IT Asset, and IP Address List, depending on your specific needs.

If neither of these options is suitable, please let me know. I can forward your post as a feature request — just let me know the type of entry you're looking for and what functionality is missing.

Best regards,

Thanks for the time. I think it makes sense to have an entry type that allows for adding NICs. There are all kinds of systems that have multiple addresses/nics you might want to track and manage. What I'm thinking is that there should be a type of parent object I can create that can have child entries that refer to the different management for that one host. Ex: a server might have multiple nics: eth0, eth1, eth2 and a LOM(iDrac/iLO). I might use RDP or VNC to connect to the server for specific teams or types of management and SSH for other reasons. I also might need to hit a web interface for the server OS as well as the LOM; and SSH into the LOM. That's at least 5 different IP/Port combinations eth0:3389, eth0:22, eth0:443, LOM:443, LOM:22. All related to a single host. Currently I have to create individual entries for each. Instead it would make sense to be able to create a single entry/object that contains all the relevant information, and then create children that inherit the specific properties the child is meant for, similar to how I can link the credentials in a vault but instead the drop-down pulls the possible fields from only the parent object. So the SSH child entry, instead of having only the fields for hostIP/name and port, would have a drop-down box that says "inherit from parent" and a second field that drops down listing the possible address/port combinations available on the parent. That way you would end up with a single 'master' object and wouldn't have to maintain the children much. Make sense?

Hello,

Thank you for your response.

I will forward your message as a feature request to the appropriate team.

Best regards,

Hello,

What you're describing to me seems to be what the IP address list entry is meant to do. It can store a lot of different information regarding hosts/IPs. On top of that, you can use the generic fields that entries possess, for example in the Asset tab to add more information regarding the device itself, for example. Did you look at what it's offering? If it's missing a couple fields, we could simply add them to it.

What I'm imagining is that you'd need us to add a way to select a host/IP from that entry when trying to connect to a machine. We could leverage the existing "Open with template" feature. This would allow you to create a template for the types you need (SSH, RDP, VNC, etc), fill in the bare minimum information like the port (or if it's the default you wouldn't even need to add that), and then you'd be able to connect easily to your machines while only needing to create:
- A generic set of templates of the appropriate types you need
- One IP address list entry per server which will contain all the different IPs you can connect to

Do you think this solution could work for you?

Regards,

Looking at that right now and it looks like exactly what I was talking about. Thanks for the reply!

That's great, I will open an internal ticket so we can support using IP Address List entries as a "source" for the host to connect to. I can't give you an estimate on when we'll be able to work on this for now, but we're keeping an eye out for additional feedback to help us prioritize this.

Regards,