<?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 Spark 1600 bridge mode can not work in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175134#M29221</link>
    <description>&lt;P&gt;Hi Guys&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; My environment have one checkpoint 1600 appliance , It is setting bridge mode Lan1 &amp;amp; Lan2&amp;nbsp; &amp;amp; checkpoint 1600 using Central management to SMS&lt;/P&gt;&lt;P&gt;architecture is :&lt;/P&gt;&lt;P&gt;(internel)&amp;lt;----&amp;gt;(fortigate) &amp;lt; -----&amp;gt;(dlink_L2_swithch)&amp;lt;--------LAN2-&amp;gt;( Checpoint_1600)&amp;lt;-LAN1---&amp;gt;(core_switch)&lt;/P&gt;&lt;P&gt;But. bridge port link up to switch after , internal core switch can not ping external fortigate . On the contrary fortigate can not ping core switch .&lt;/P&gt;&lt;P&gt;I try to fw monitor &amp;amp; zdebug + dorp display:&lt;/P&gt;&lt;P&gt;192.168.100.254 : is core switch IP&lt;BR /&gt;192.168.100.246 : is fortigat IP&lt;/P&gt;&lt;P&gt;1. fw monitor&lt;/P&gt;&lt;P&gt;[vs_0][fw_0] LAN1:o[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52099&lt;BR /&gt;ICMP: type=8 code=0 echo request id=3328 seq=3&lt;BR /&gt;[vs_0][fw_0] LAN1:O[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52099&lt;BR /&gt;ICMP: type=8 code=0 echo request id=3328 seq=3&lt;BR /&gt;[vs_0][fw_0] LAN2:i[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52100&lt;BR /&gt;ICMP: type=8 code=0 echo request id=3328 seq=4&lt;BR /&gt;[vs_0][fw_0] LAN2:I[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52100&lt;/P&gt;&lt;P&gt;2. zdebug + dorp : no drop info log&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any other solution?&lt;/P&gt;</description>
    <pubDate>Thu, 16 Mar 2023 16:40:13 GMT</pubDate>
    <dc:creator>oscar790806</dc:creator>
    <dc:date>2023-03-16T16:40:13Z</dc:date>
    <item>
      <title>Spark 1600 bridge mode can not work</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175134#M29221</link>
      <description>&lt;P&gt;Hi Guys&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; My environment have one checkpoint 1600 appliance , It is setting bridge mode Lan1 &amp;amp; Lan2&amp;nbsp; &amp;amp; checkpoint 1600 using Central management to SMS&lt;/P&gt;&lt;P&gt;architecture is :&lt;/P&gt;&lt;P&gt;(internel)&amp;lt;----&amp;gt;(fortigate) &amp;lt; -----&amp;gt;(dlink_L2_swithch)&amp;lt;--------LAN2-&amp;gt;( Checpoint_1600)&amp;lt;-LAN1---&amp;gt;(core_switch)&lt;/P&gt;&lt;P&gt;But. bridge port link up to switch after , internal core switch can not ping external fortigate . On the contrary fortigate can not ping core switch .&lt;/P&gt;&lt;P&gt;I try to fw monitor &amp;amp; zdebug + dorp display:&lt;/P&gt;&lt;P&gt;192.168.100.254 : is core switch IP&lt;BR /&gt;192.168.100.246 : is fortigat IP&lt;/P&gt;&lt;P&gt;1. fw monitor&lt;/P&gt;&lt;P&gt;[vs_0][fw_0] LAN1:o[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52099&lt;BR /&gt;ICMP: type=8 code=0 echo request id=3328 seq=3&lt;BR /&gt;[vs_0][fw_0] LAN1:O[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52099&lt;BR /&gt;ICMP: type=8 code=0 echo request id=3328 seq=3&lt;BR /&gt;[vs_0][fw_0] LAN2:i[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52100&lt;BR /&gt;ICMP: type=8 code=0 echo request id=3328 seq=4&lt;BR /&gt;[vs_0][fw_0] LAN2:I[44]: 192.168.100.246 -&amp;gt; 192.168.100.254 (ICMP) len=84 id=52100&lt;/P&gt;&lt;P&gt;2. zdebug + dorp : no drop info log&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there any other solution?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 16:40:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175134#M29221</guid>
      <dc:creator>oscar790806</dc:creator>
      <dc:date>2023-03-16T16:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: Spark 1600 bridge mode can not work</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175158#M29223</link>
      <description>&lt;P&gt;I would involve TAC here !&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 20:17:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175158#M29223</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-03-16T20:17:18Z</dc:date>
    </item>
    <item>
      <title>Re: Spark 1600 bridge mode can not work</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175162#M29224</link>
      <description>&lt;P&gt;Im no SMB expert by any means, but just to confirm 100%, the connection from 192.168.100.246 is supposed to come to LAN2 and then leaves on LAN1 going to 192.168.100.254?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 20:47:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175162#M29224</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2023-03-16T20:47:51Z</dc:date>
    </item>
    <item>
      <title>Re: Spark 1600 bridge mode can not work</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175165#M29225</link>
      <description>&lt;P&gt;Which firmware/build is used on the 1600 appliance and how is the interface topology / anti-spoofing defined?&lt;/P&gt;</description>
      <pubDate>Thu, 16 Mar 2023 22:17:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Spark-1600-bridge-mode-can-not-work/m-p/175165#M29225</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-03-16T22:17:31Z</dc:date>
    </item>
  </channel>
</rss>

