<?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: cli logs in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242194#M40464</link>
    <description>&lt;P&gt;Pretty sure you can only provide up to five -F flags. Also, I'm not aware of any way to do partial matches (e.g, to match a source network), only an exact value or a whole-field wildcard, so it's easy to burn through those five when troubleshooting all but the most trivial flows.&lt;/P&gt;</description>
    <pubDate>Mon, 24 Feb 2025 21:35:38 GMT</pubDate>
    <dc:creator>Bob_Zimmerman</dc:creator>
    <dc:date>2025-02-24T21:35:38Z</dc:date>
    <item>
      <title>cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242168#M40459</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need syntax of the command , which provide complete details of traffic flow including details of tcp state, inbound and outbound,rule name, service , conn module details on checkpoint firewall live logs for tcpdump or Fw monitor.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 18:59:13 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242168#M40459</guid>
      <dc:creator>ebinva</dc:creator>
      <dc:date>2025-02-24T18:59:13Z</dc:date>
    </item>
    <item>
      <title>Re: cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242181#M40460</link>
      <description>&lt;P&gt;This is probably more than a single command. Also, logs are usually sent to the management and handled there.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Can you elaborate on your usecase?&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 20:07:22 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242181#M40460</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2025-02-24T20:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242186#M40461</link>
      <description>&lt;P&gt;As Val said, definitely more than a single command.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 20:50:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242186#M40461</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-02-24T20:50:53Z</dc:date>
    </item>
    <item>
      <title>Re: cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242187#M40462</link>
      <description>&lt;P&gt;there is a traffic between particular source and destination on specific port, we need to check inbound and outbound traffic flow of packet with details of tcp details, connect status ,rule for accepting or rejecting etc.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 20:57:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242187#M40462</guid>
      <dc:creator>ebinva</dc:creator>
      <dc:date>2025-02-24T20:57:15Z</dc:date>
    </item>
    <item>
      <title>Re: cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242188#M40463</link>
      <description>&lt;P&gt;So for rule accepting, you can use below examples:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_CLI_ReferenceGuide/Topics-CLIG/FWG/fw-up_execute.htm" target="_blank"&gt;https://sc1.checkpoint.com/documents/R81/WebAdminGuides/EN/CP_R81_CLI_ReferenceGuide/Topics-CLIG/FWG/fw-up_execute.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;For traffic itself, try something like below and -F flag can be used as many times as you like.&lt;/P&gt;
&lt;P&gt;fw monitor -F "1.1.1.1,0,2.2.2.2,4434,0" -F "2.2.2.2,0,1.1.1.1,4434,0"&lt;/P&gt;
&lt;P&gt;In that example, 1.1.1.1 is src, 2.2.2.2 is dst and logic is like this:&lt;/P&gt;
&lt;P&gt;src ip, src port, dst ip, dst port, protocol&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 21:00:09 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242188#M40463</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-02-24T21:00:09Z</dc:date>
    </item>
    <item>
      <title>Re: cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242194#M40464</link>
      <description>&lt;P&gt;Pretty sure you can only provide up to five -F flags. Also, I'm not aware of any way to do partial matches (e.g, to match a source network), only an exact value or a whole-field wildcard, so it's easy to burn through those five when troubleshooting all but the most trivial flows.&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 21:35:38 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242194#M40464</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2025-02-24T21:35:38Z</dc:date>
    </item>
    <item>
      <title>Re: cli logs</title>
      <link>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242197#M40465</link>
      <description>&lt;P&gt;Thanks Bob, thats good to know. I thought it was as many -F flags as you needed.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2025 21:52:45 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/cli-logs/m-p/242197#M40465</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-02-24T21:52:45Z</dc:date>
    </item>
  </channel>
</rss>

