<?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: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249347#M48695</link>
    <description>&lt;P class=""&gt;Hi,&lt;/P&gt;&lt;P class=""&gt;Thanks for the suggestions. I’ve followed the recommendation to exclude BGP (TCP 179) from the VPN community and reinstalled policy, but I still see the same log:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P class=""&gt;&lt;STRONG&gt;"According to the policy the packet should not have been decrypted"&lt;/STRONG&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P class=""&gt;The traffic is still being dropped,&lt;/P&gt;&lt;P class=""&gt;I added &lt;STRONG&gt;TCP 179 (BGP)&lt;/STRONG&gt; under &lt;STRONG&gt;“Excluded Services”&lt;/STRONG&gt; in the VPN community and pushed policy.&lt;/P&gt;&lt;P class=""&gt;I allowd bgp in policy rule.&lt;/P&gt;&lt;P class=""&gt;I see traffic BGP going out interface vpnt1, but traffic arrive to interface eth0,&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 19 May 2025 21:45:05 GMT</pubDate>
    <dc:creator>vanhieuptit4</dc:creator>
    <dc:date>2025-05-19T21:45:05Z</dc:date>
    <item>
      <title>Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249256#M48685</link>
      <description>&lt;P class=""&gt;Hi all,&lt;/P&gt;&lt;P class=""&gt;I’ve successfully established a VTI-based VPN tunnel between my Check Point firewall and AWS. Phase1 up, phase2 down beacause&amp;nbsp; rule block&amp;nbsp;for connect ip 169.254.x.11 (AWS point) --&amp;gt; 169.254.x.10 (Onprem point) service bgp tcp/179. I’m seeing logs that say:&lt;/P&gt;&lt;P class=""&gt;"According to the policy the packet should not have been decrypted"&amp;nbsp;&lt;/P&gt;&lt;P class=""&gt;I have already:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P class=""&gt;Set VPN domains to 0.0.0.0/0 (Empty Group) on both ends.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P class=""&gt;Enabled "VPN Directional Match in VPN Column" and configured the VPN column accordingly.&amp;nbsp;"Choose "Add" to add directional match rules as follows:&lt;BR /&gt;a. internal_clear --&amp;gt; vpn-02f8b875e8179c57b&lt;BR /&gt;b. vpn-02f8b875e8179c57b --&amp;gt; vpn-02f8b875e8179c57b&lt;BR /&gt;c. vpn-02f8b875e8179c57b --&amp;gt; internal_clear"&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P class=""&gt;Created rules to allow communication between AWS and on-prem subnets.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;Still, the traffic for BGP (port 179) seems to get blocked — and the log shows it's being dropped on the external interface (eth0), not on the VTI interface (vpnt1). I suspect the stealth rule might be affecting this traffic.&lt;/P&gt;&lt;P class=""&gt;Thanks in advance for any help!&lt;/P&gt;</description>
      <pubDate>Sun, 18 May 2025 06:47:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249256#M48685</guid>
      <dc:creator>vanhieuptit4</dc:creator>
      <dc:date>2025-05-18T06:47:06Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249285#M48687</link>
      <description>&lt;P&gt;According to your VPN settings, all traffic between the GWs should be encrypted, yet BGP is sent in clear text. You may want to tackle this by excluding BGP form the VPN and reinstalling policy&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 07:25:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249285#M48687</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2025-05-19T07:25:05Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249345#M48694</link>
      <description>&lt;P&gt;Apart from great point&amp;nbsp;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/181"&gt;@_Val_&lt;/a&gt;&amp;nbsp; made, which tells you that packet should have been encrypted, you can also try zdebug and see if same failure occurs.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 20:24:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249345#M48694</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-05-19T20:24:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249347#M48695</link>
      <description>&lt;P class=""&gt;Hi,&lt;/P&gt;&lt;P class=""&gt;Thanks for the suggestions. I’ve followed the recommendation to exclude BGP (TCP 179) from the VPN community and reinstalled policy, but I still see the same log:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P class=""&gt;&lt;STRONG&gt;"According to the policy the packet should not have been decrypted"&lt;/STRONG&gt;&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P class=""&gt;The traffic is still being dropped,&lt;/P&gt;&lt;P class=""&gt;I added &lt;STRONG&gt;TCP 179 (BGP)&lt;/STRONG&gt; under &lt;STRONG&gt;“Excluded Services”&lt;/STRONG&gt; in the VPN community and pushed policy.&lt;/P&gt;&lt;P class=""&gt;I allowd bgp in policy rule.&lt;/P&gt;&lt;P class=""&gt;I see traffic BGP going out interface vpnt1, but traffic arrive to interface eth0,&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 19 May 2025 21:45:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249347#M48695</guid>
      <dc:creator>vanhieuptit4</dc:creator>
      <dc:date>2025-05-19T21:45:05Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249349#M48696</link>
      <description>&lt;P&gt;K, one sec...now that I think about it, seems as if BGP range should be in vpn domain, since it should be encrypted, according to the message.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Technically, CP domain does not need to be empty group, only AWS one.&lt;/P&gt;
&lt;P&gt;Maybe change that and test.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 00:15:26 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249349#M48696</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-05-20T00:15:26Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249350#M48697</link>
      <description>&lt;P&gt;Also, if you think stealth rule might be the culprit, just try disable it temporarily and test. FWIW, I always found BGP works way better when using unnumbered VTIs.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 00:31:49 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249350#M48697</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-05-20T00:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249353#M48698</link>
      <description>&lt;P&gt;I believe 'should not have been decrypted' means that it came in encrypted, the gateway decrypted it to see what was inside, then thinks 'hey this should have been sent in the clear'. BGP in this case should be encrypted, so don't exclude it from the tunnel.&lt;/P&gt;
&lt;P&gt;Have you checked this:&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk106627" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk106627&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 03:22:33 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249353#M48698</guid>
      <dc:creator>emmap</dc:creator>
      <dc:date>2025-05-20T03:22:33Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249354#M48699</link>
      <description>&lt;P&gt;That was my thinking as well.&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 03:25:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249354#M48699</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-05-20T03:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249362#M48701</link>
      <description>&lt;P&gt;Yes, It's work when set vpnt1 to peer name&lt;/P&gt;&lt;P&gt;Thanks for solution&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 07:30:58 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249362#M48701</guid>
      <dc:creator>vanhieuptit4</dc:creator>
      <dc:date>2025-05-20T07:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: Why is my BGP (TCP 179) traffic getting blocked by Check Point when set up vpn to AWS</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249390#M48707</link>
      <description>&lt;P&gt;I assumed you had that already. Glad you got it now!&lt;/P&gt;</description>
      <pubDate>Tue, 20 May 2025 12:06:23 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/Why-is-my-BGP-TCP-179-traffic-getting-blocked-by-Check-Point/m-p/249390#M48707</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-05-20T12:06:23Z</dc:date>
    </item>
  </channel>
</rss>

