<?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 Using cluster object in access policy in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105777#M20266</link>
    <description>&lt;P&gt;When using a cluster object in the access policy, what exactly does it represent?&amp;nbsp; Does it represent all IPs on all interfaces of both cluster members plus virtual IPs for the cluster itself?&amp;nbsp; Or does it only represent a subset of these?&lt;/P&gt;&lt;P&gt;For example, if I had a firewall cluster with member A and member B configured with the following IPs:&lt;/P&gt;&lt;P&gt;Member A: eth1: 1.1.1.1, eth2: 2.2.2.1&lt;BR /&gt;Member B: eth1: 1.1.1.2, eth2: 2.2.2.2&lt;BR /&gt;Virtual IP: eth1: 1.1.1.3, eth2: 2.2.2.3&lt;/P&gt;&lt;P&gt;If I configured a rule allowing 10.1.1.1 --&amp;gt; Cluster_Object, ICMP&lt;/P&gt;&lt;P&gt;What would 10.1.1.1 be allowed to ping?&lt;/P&gt;&lt;P&gt;(Note: I am assuming that implied rules are not interfering with any of this)&lt;/P&gt;</description>
    <pubDate>Thu, 17 Dec 2020 19:27:52 GMT</pubDate>
    <dc:creator>phlrnnr</dc:creator>
    <dc:date>2020-12-17T19:27:52Z</dc:date>
    <item>
      <title>Using cluster object in access policy</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105777#M20266</link>
      <description>&lt;P&gt;When using a cluster object in the access policy, what exactly does it represent?&amp;nbsp; Does it represent all IPs on all interfaces of both cluster members plus virtual IPs for the cluster itself?&amp;nbsp; Or does it only represent a subset of these?&lt;/P&gt;&lt;P&gt;For example, if I had a firewall cluster with member A and member B configured with the following IPs:&lt;/P&gt;&lt;P&gt;Member A: eth1: 1.1.1.1, eth2: 2.2.2.1&lt;BR /&gt;Member B: eth1: 1.1.1.2, eth2: 2.2.2.2&lt;BR /&gt;Virtual IP: eth1: 1.1.1.3, eth2: 2.2.2.3&lt;/P&gt;&lt;P&gt;If I configured a rule allowing 10.1.1.1 --&amp;gt; Cluster_Object, ICMP&lt;/P&gt;&lt;P&gt;What would 10.1.1.1 be allowed to ping?&lt;/P&gt;&lt;P&gt;(Note: I am assuming that implied rules are not interfering with any of this)&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 19:27:52 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105777#M20266</guid>
      <dc:creator>phlrnnr</dc:creator>
      <dc:date>2020-12-17T19:27:52Z</dc:date>
    </item>
    <item>
      <title>Re: Using cluster object in access policy</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105911#M20290</link>
      <description>&lt;P&gt;I believe it’s just the main IP of the object (on general tab).&lt;/P&gt;</description>
      <pubDate>Sat, 19 Dec 2020 05:34:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105911#M20290</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2020-12-19T05:34:18Z</dc:date>
    </item>
    <item>
      <title>Re: Using cluster object in access policy</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105959#M20301</link>
      <description>&lt;P&gt;In R77.30 all VIPs were matched.&lt;/P&gt;
&lt;P&gt;In R80.30 only Main IP in Cluster Object is matched. If you need some interface VIP to be used, create host object.&lt;/P&gt;</description>
      <pubDate>Sun, 20 Dec 2020 07:35:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Using-cluster-object-in-access-policy/m-p/105959#M20301</guid>
      <dc:creator>JozkoMrkvicka</dc:creator>
      <dc:date>2020-12-20T07:35:33Z</dc:date>
    </item>
  </channel>
</rss>

