<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Agent Connectivity picking up EVERY IP on the server. in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/agent-connectivity-picking-up-every-ip-on-the-server/m-p/1419501#M528</link>
    <description>Folks, why does the Venafi agent pick up and put every IP found on the server into the TPP server for the registered agent? We use CIDR ranges to separate the Client Groups in Aperture, but this becomes impossible when you have backup and private networks that span multiple datacenters. Why cant Venafi get only the IP that is associated to the hostname of the server?.</description>
    <pubDate>Mon, 05 Dec 2022 14:57:46 GMT</pubDate>
    <dc:creator>DPrice</dc:creator>
    <dc:date>2022-12-05T14:57:46Z</dc:date>
    <item>
      <title>Agent Connectivity picking up EVERY IP on the server.</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/agent-connectivity-picking-up-every-ip-on-the-server/m-p/1419501#M528</link>
      <description>Folks, why does the Venafi agent pick up and put every IP found on the server into the TPP server for the registered agent? We use CIDR ranges to separate the Client Groups in Aperture, but this becomes impossible when you have backup and private networks that span multiple datacenters. Why cant Venafi get only the IP that is associated to the hostname of the server?.</description>
      <pubDate>Mon, 05 Dec 2022 14:57:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/agent-connectivity-picking-up-every-ip-on-the-server/m-p/1419501#M528</guid>
      <dc:creator>DPrice</dc:creator>
      <dc:date>2022-12-05T14:57:46Z</dc:date>
    </item>
  </channel>
</rss>

