<?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: Bridge mode and tagged traffic in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169565#M30725</link>
    <description>&lt;P&gt;Did you contact TAC yet ?&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2023 08:59:09 GMT</pubDate>
    <dc:creator>G_W_Albrecht</dc:creator>
    <dc:date>2023-01-30T08:59:09Z</dc:date>
    <item>
      <title>Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169424#M30668</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;There is a regular L3 HA cluster (having internal, external and sync interfaces). It is not VSX.&lt;/P&gt;&lt;P&gt;There is a need to use this same cluster to do some L2 bridging. Firewall will not do any routing for L2 IP address scopes (that may change at some point, but it is not the issue here).&lt;/P&gt;&lt;P&gt;Lab topology for testing the scenario is displayed on drawing. When all switch ports are configured as access mode for vlan 100, two PCs can ping each other, bridging works OK. Policy allows any service from 10.10.100.0/24 to 10.10.100.0/24.&lt;/P&gt;&lt;P&gt;When I change switchports connecting firewalls to trunk (tagged vlans), firewall is not passing traffic anymore.&lt;/P&gt;&lt;P&gt;When PC 101 is trying to ping PC 102 traffic arrive on interface eth5, it is clear that traffic is tagged by vlan id 100, but nothing is seen on eth6:&lt;/P&gt;&lt;LI-SPOILER&gt;&lt;FONT face="courier new,courier"&gt;[Expert@gw_dc1:0]# tcpdump -enni eth5&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;tcpdump: verbose output suppressed, use -v or -vv for full protocol decode&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;listening on eth5, link-type EN10MB (Ethernet), capture size 262144 bytes&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;14:35:17.171156 00:0c:29:ac:e5:3f &amp;gt; ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 64: &lt;STRONG&gt;vlan 100&lt;/STRONG&gt;, p 0, ethertype ARP, Request who-has 10.10.100.102 tell 10.10.100.101, length 46&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;14:35:18.195079 00:0c:29:ac:e5:3f &amp;gt; ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 64: &lt;STRONG&gt;vlan 100&lt;/STRONG&gt;, p 0, ethertype ARP, Request who-has 10.10.100.102 tell 10.10.100.101, length 46&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;14:35:19.219390 00:0c:29:ac:e5:3f &amp;gt; ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 64: &lt;STRONG&gt;vlan 100&lt;/STRONG&gt;, p 0, ethertype ARP, Request who-has 10.10.100.102 tell 10.10.100.101, length 46&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;14:35:20.243128 00:0c:29:ac:e5:3f &amp;gt; ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 64: &lt;STRONG&gt;vlan 100&lt;/STRONG&gt;, p 0, ethertype ARP, Request who-has 10.10.100.102 tell 10.10.100.101, length 46&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;14:35:21.267126 00:0c:29:ac:e5:3f &amp;gt; ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 64: &lt;STRONG&gt;vlan 100&lt;/STRONG&gt;, p 0, ethertype ARP, Request who-has 10.10.100.102 tell 10.10.100.101, length 46&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;^C&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;5 packets captured&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;5 packets received by filter&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;0 packets dropped by kernel&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[Expert@gw_dc1:0]# tcpdump -enni eth6&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;tcpdump: verbose output suppressed, use -v or -vv for full protocol decode&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;listening on eth6, link-type EN10MB (Ethernet), capture size 262144 bytes&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;^C&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;0 packets captured&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;0 packets received by filter&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;0 packets dropped by kernel&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;[Expert@gw_dc1:0]#&lt;/FONT&gt;&lt;/LI-SPOILER&gt;&lt;P&gt;Firewalls are configured to use "Check Point ClusterXL for Bridge Active/Standby" to avoid loop. The above test was also done with FW2 shut down, to make sure all traffic is passing only via FW1. Gaia configuration:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-SPOILER&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;gw_dc1&amp;gt; show configuration bridging &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;add bridging group 1000 &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;add bridging group 1000 interface eth5 &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;add bridging group 1000 interface eth6 &lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT face="courier new,courier"&gt;gw_dc1&amp;gt; show configuration interface&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface br1000 state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth0 state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth0 auto-negotiation on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth0 ipv4-address 192.168.2.236 mask-length 24 &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth1 link-speed 1000M/full &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth1 state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth1 ipv4-address 10.200.200.2 mask-length 24 &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth2 link-speed 1000M/full &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth2 state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth2 ipv4-address 10.255.254.1 mask-length 30 &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth3 state off &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth4 state off &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth5 state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface eth6 state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface lo state on &lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;set interface lo ipv4-address 127.0.0.1 mask-length 8&lt;/FONT&gt;&lt;/P&gt;&lt;/LI-SPOILER&gt;&lt;P&gt;&lt;SPAN&gt;Bridge interface is not part of topology in Smart Console.&amp;nbsp;&lt;/SPAN&gt;Tested this with R80.40 and also R81 JHF take 65. Tried it with single firewall (not part of cluster) and ClusterXL described above.&lt;/P&gt;&lt;P&gt;I am out of ideas. According to &lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_Gaia_AdminGuide/Topics-GAG/VLAN-Interfaces.htm" target="_blank" rel="noopener"&gt;documentation&lt;/A&gt;, this is supported scenario but it is not working for some reason &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;If you configure the switch ports as VLAN trunk, the&amp;nbsp;Check Point&amp;nbsp;Bridge interface should&amp;nbsp;not&amp;nbsp;interfere with the VLANs.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;To configure a Bridge interface with VLAN trunk, create the Bridge interface with two physical (non-VLAN) interfaces as its subordinate interfaces&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 14:23:34 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169424#M30668</guid>
      <dc:creator>Srdjan_B</dc:creator>
      <dc:date>2023-01-27T14:23:34Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169553#M30718</link>
      <description>&lt;P&gt;Is the gateway seeing the same traffic twice?&lt;BR /&gt;Double inspection is...not supported.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 05:48:29 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169553#M30718</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2023-01-30T05:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169557#M30720</link>
      <description>&lt;P&gt;No, not really. Also, when tagging on switches is off, everything works as expected.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 06:47:20 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169557#M30720</guid>
      <dc:creator>Srdjan_B</dc:creator>
      <dc:date>2023-01-30T06:47:20Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169565#M30725</link>
      <description>&lt;P&gt;Did you contact TAC yet ?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 08:59:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169565#M30725</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-01-30T08:59:09Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169569#M30728</link>
      <description>&lt;P&gt;I did not contact TAC, this is lab environment with eval licenses and no support. When we do it on production boxes, it will have to work from day 1, so I am trying to verify the configuration and steps upfront.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 09:21:02 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169569#M30728</guid>
      <dc:creator>Srdjan_B</dc:creator>
      <dc:date>2023-01-30T09:21:02Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169572#M30729</link>
      <description>&lt;P&gt;As long as this is for a customer with valid support you only need his UC Account# - this is a common scenario...&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 09:29:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/169572#M30729</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-01-30T09:29:19Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/181877#M33286</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/20425"&gt;@Srdjan_B&lt;/a&gt;&amp;nbsp;- did you manage to get this scenario working in the end.&amp;nbsp; I'm building out a similiar solution now.&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 08:36:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/181877#M33286</guid>
      <dc:creator>Ruan_Kotze</dc:creator>
      <dc:date>2023-05-24T08:36:56Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/181879#M33287</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/9028"&gt;@Ruan_Kotze&lt;/a&gt;&amp;nbsp;. Customer decided to accept alternative design, without firewall in bridge mode, so further testing was abandoned.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 08:55:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/181879#M33287</guid>
      <dc:creator>Srdjan_B</dc:creator>
      <dc:date>2023-05-24T08:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: Bridge mode and tagged traffic</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/181883#M33288</link>
      <description>&lt;P&gt;Hi Ruan_Kotze,&lt;/P&gt;&lt;P&gt;Try the followings:&lt;/P&gt;&lt;P&gt;When the traffic does not pass the bridge: have you tried to switch off the acceleration (#fwaccel off)?&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to this article: &lt;A href="https://support.checkpoint.com/results/sk/sk105899" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk105899&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Set the relevant kernel parameters (all four)&lt;/P&gt;&lt;P&gt;Let's see what we get.&lt;/P&gt;&lt;P&gt;Akos&lt;/P&gt;</description>
      <pubDate>Wed, 24 May 2023 09:10:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Bridge-mode-and-tagged-traffic/m-p/181883#M33288</guid>
      <dc:creator>AkosBakos</dc:creator>
      <dc:date>2023-05-24T09:10:00Z</dc:date>
    </item>
  </channel>
</rss>

