Stop public/home IP addresses from populating CI's IP

shembop
Tera Contributor

‎06-21-2024 05:37 AM - edited ‎06-24-2024 05:16 AM

I have an issue with discovery. It sometimes populates the public (or home) IP address of a VPN client onto the CI record. See attached. How can I define what IP address gets populated, or at least avoid populating these addresses.

Preview file
64 KB
0 Helpfuls
  • 410 Views
3 REPLIES 3

Mark Manders
Mega Patron

‎06-21-2024 06:25 AM

Can you share the attachment as well? That helps in making it clear what is happening.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
0 Helpfuls

shembop
Tera Contributor
In response to Mark Manders

‎06-24-2024 05:18 AM

I just attached an example.

0 Helpfuls

BozhidarNizamov
Tera Contributor

‎06-24-2024 03:20 AM

I am facing something similar - discovery of servers using their public or private IPv4 address ends up populating the CIs with IPv6 addresses - which aren't even supposed to be available. I literally don't have a single IPv6 address in my GCP.. 

BozhidarNizamov_0-1719224337087.png

yet in the Server CIs I see IPv6 addresses along with the private IPv4. No public IPv4 tho. 

0 Helpfuls