<?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 double vlan IP addresses in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64840#M9716</link>
    <description>&lt;P&gt;We are on R80.20 on VSX platform.&lt;BR /&gt;when we add a new vlan with specific IP 10.x.x.x it also automatically assigned a new IP 192.168.x.x to same vlan as shown below.&lt;BR /&gt;What is the purpose of those IPs 192.168.x.x ?&lt;BR /&gt;Also when firewall try to resolve DNS, why it use source IP those 192.168.x.x. addresses Not real IP (10.x.x.x) assigned to vlan .&lt;BR /&gt;How firewall can use its real IP 10.x.x.x as a source IP to resolve DNS?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1&amp;gt; show interface bond0.300&lt;BR /&gt;ipv4-address 10.10.2.1/24&lt;/P&gt;&lt;P&gt;1&amp;gt; show interface bond0.301&lt;BR /&gt;ipv4-address 10.10.3.1/24&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1&amp;gt; show interface bond0.302&lt;BR /&gt;ipv4-address 10.10.4.1/24&lt;/P&gt;&lt;P&gt;set interface bond0.300 state on&lt;BR /&gt;set interface bond0.300 mtu 1500&lt;BR /&gt;set interface bond0.300 ipv4-address 192.168.192.50 mask-length 28&lt;BR /&gt;set interface bond0.301 state on&lt;BR /&gt;set interface bond0.301 mtu 1500&lt;BR /&gt;set interface bond0.301 ipv4-address 192.168.192.34 mask-length 28&lt;BR /&gt;set interface bond0.302 state on&lt;BR /&gt;set interface bond0.302 mtu 1500&lt;BR /&gt;set interface bond0.302 ipv4-address 192.168.192.18 mask-length 28&lt;/P&gt;</description>
    <pubDate>Fri, 11 Oct 2019 20:26:55 GMT</pubDate>
    <dc:creator>CPRQ</dc:creator>
    <dc:date>2019-10-11T20:26:55Z</dc:date>
    <item>
      <title>double vlan IP addresses</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64840#M9716</link>
      <description>&lt;P&gt;We are on R80.20 on VSX platform.&lt;BR /&gt;when we add a new vlan with specific IP 10.x.x.x it also automatically assigned a new IP 192.168.x.x to same vlan as shown below.&lt;BR /&gt;What is the purpose of those IPs 192.168.x.x ?&lt;BR /&gt;Also when firewall try to resolve DNS, why it use source IP those 192.168.x.x. addresses Not real IP (10.x.x.x) assigned to vlan .&lt;BR /&gt;How firewall can use its real IP 10.x.x.x as a source IP to resolve DNS?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1&amp;gt; show interface bond0.300&lt;BR /&gt;ipv4-address 10.10.2.1/24&lt;/P&gt;&lt;P&gt;1&amp;gt; show interface bond0.301&lt;BR /&gt;ipv4-address 10.10.3.1/24&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;1&amp;gt; show interface bond0.302&lt;BR /&gt;ipv4-address 10.10.4.1/24&lt;/P&gt;&lt;P&gt;set interface bond0.300 state on&lt;BR /&gt;set interface bond0.300 mtu 1500&lt;BR /&gt;set interface bond0.300 ipv4-address 192.168.192.50 mask-length 28&lt;BR /&gt;set interface bond0.301 state on&lt;BR /&gt;set interface bond0.301 mtu 1500&lt;BR /&gt;set interface bond0.301 ipv4-address 192.168.192.34 mask-length 28&lt;BR /&gt;set interface bond0.302 state on&lt;BR /&gt;set interface bond0.302 mtu 1500&lt;BR /&gt;set interface bond0.302 ipv4-address 192.168.192.18 mask-length 28&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2019 20:26:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64840#M9716</guid>
      <dc:creator>CPRQ</dc:creator>
      <dc:date>2019-10-11T20:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: double vlan IP addresses</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64844#M9717</link>
      <description>&lt;P&gt;CPRQ,&lt;/P&gt;&lt;P&gt;adding these 192.168.xx.xx addresses are normal behaviour.&lt;/P&gt;&lt;P&gt;this the VSX internal network used for internal communication. You can see the configuration of this network here:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SmartDashboard - open VSX cluster object - go to "Cluster Members" pane - refer to section "Cluster members internal communication network"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;For outgoing connections from the VSX-cluster they should be NATed behind the configured IP of the interface. The behaviour of this NAT is described in&amp;nbsp;&lt;A href="https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&amp;amp;solutionid=sk111786" target="_self"&gt;Outgoing connections from Virtual System in VSX cluster are sent with source IP address that belongs to cluster Internal Communication Network instead of cluster Virtual IP address&lt;/A&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Wolfgang&lt;/P&gt;</description>
      <pubDate>Fri, 11 Oct 2019 21:05:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64844#M9717</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2019-10-11T21:05:14Z</dc:date>
    </item>
    <item>
      <title>Re: double vlan IP addresses</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64952#M9718</link>
      <description>Thank you. We are going through the SK, it seems exactly what we are seeing and looking answer for it. Thanks</description>
      <pubDate>Mon, 14 Oct 2019 14:41:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/double-vlan-IP-addresses/m-p/64952#M9718</guid>
      <dc:creator>CPRQ</dc:creator>
      <dc:date>2019-10-14T14:41:29Z</dc:date>
    </item>
  </channel>
</rss>

