<?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 Re: Filtering interfaces from VM ( VMware vcenter Integration) in Cloud Firewall</title>
    <link>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68893#M2621</link>
    <description>&lt;P&gt;Understandable, but I think this is one of those situations that automatically created objects would not work.&lt;/P&gt;
&lt;P&gt;Consider: vCenter provides the data about the object, but it is unaware about its routing properties.&lt;/P&gt;
&lt;P&gt;If you are to edit the object's properties in CP, the data between CP and vCenter gets out of sync.&lt;/P&gt;</description>
    <pubDate>Fri, 29 Nov 2019 14:55:18 GMT</pubDate>
    <dc:creator>Vladimir</dc:creator>
    <dc:date>2019-11-29T14:55:18Z</dc:date>
    <item>
      <title>Filtering interfaces from VM ( VMware vcenter Integration)</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68854#M2618</link>
      <description>&lt;P&gt;Hello CheckMates,&lt;/P&gt;&lt;P&gt;I had a question regarding the integration with VMware vcenter.&amp;nbsp;&lt;BR /&gt;If an imported virtual machine has more then one interface, all of the IP addresses of this VM are learned and traffic regarding these IPs is allowed or blocked.&lt;/P&gt;&lt;P&gt;Is it possible to use this imported object and allow only one of the interfaces? If I add a datacenter object I had no chance to filter something like this. The whole object is imported and used with all existing IPs.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Wolfgang&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 20:45:16 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68854#M2618</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2019-11-28T20:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering interfaces from VM ( VMware vcenter Integration)</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68858#M2619</link>
      <description>&lt;P&gt;I did not experience this scenario myself, but it sounds like you may have to create a dummy object with single IP if you want to use it in the policy.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Nov 2019 22:37:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68858#M2619</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2019-11-28T22:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering interfaces from VM ( VMware vcenter Integration)</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68873#M2620</link>
      <description>&lt;P&gt;Vladimir,&lt;/P&gt;
&lt;P&gt;that's what I don't want todo, creating an extra object is more work todo. It simplifies the configuration using the original datacenter object.&lt;/P&gt;
&lt;P&gt;Wolfgang&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2019 09:05:12 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68873#M2620</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2019-11-29T09:05:12Z</dc:date>
    </item>
    <item>
      <title>Re: Filtering interfaces from VM ( VMware vcenter Integration)</title>
      <link>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68893#M2621</link>
      <description>&lt;P&gt;Understandable, but I think this is one of those situations that automatically created objects would not work.&lt;/P&gt;
&lt;P&gt;Consider: vCenter provides the data about the object, but it is unaware about its routing properties.&lt;/P&gt;
&lt;P&gt;If you are to edit the object's properties in CP, the data between CP and vCenter gets out of sync.&lt;/P&gt;</description>
      <pubDate>Fri, 29 Nov 2019 14:55:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Cloud-Firewall/Filtering-interfaces-from-VM-VMware-vcenter-Integration/m-p/68893#M2621</guid>
      <dc:creator>Vladimir</dc:creator>
      <dc:date>2019-11-29T14:55:18Z</dc:date>
    </item>
  </channel>
</rss>

