<?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 Convert connection table to csv using windows scripting host in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Convert-connection-table-to-csv-using-windows-scripting-host/m-p/102792#M19837</link>
    <description>&lt;P&gt;Before I discovered Connstat, I created my own conversion of fields I felt were relevant from a saved connection table (fw -tab connections -u &amp;gt; file.txt).&amp;nbsp; The output is a csv file.&amp;nbsp; As an addition, I then created (and borrowed some code) to count instances of source or destination IPs.&amp;nbsp; That is in the form of basic code that can be imported as macros to run in Excel.&amp;nbsp; There are neater and more robust ways of doing it, but this helped resolve which IPs were filling the connection table.&amp;nbsp; At minimum, this gives a code level example of how to read the connection table.&lt;BR /&gt;&lt;BR /&gt;The default expected file name is connections.txt located in the same directory as the wsh, windows scripting host, file.&amp;nbsp; The default output is conntable.csv.&amp;nbsp; Error checking is minimal, so use carefully.&amp;nbsp; &amp;nbsp;Message boxes are used for selection.&lt;BR /&gt;&lt;BR /&gt;Note that some malware detection may block downloading a zip with wsh and bas files.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Nov 2020 14:40:06 GMT</pubDate>
    <dc:creator>George_Ellis</dc:creator>
    <dc:date>2020-11-20T14:40:06Z</dc:date>
    <item>
      <title>Convert connection table to csv using windows scripting host</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Convert-connection-table-to-csv-using-windows-scripting-host/m-p/102792#M19837</link>
      <description>&lt;P&gt;Before I discovered Connstat, I created my own conversion of fields I felt were relevant from a saved connection table (fw -tab connections -u &amp;gt; file.txt).&amp;nbsp; The output is a csv file.&amp;nbsp; As an addition, I then created (and borrowed some code) to count instances of source or destination IPs.&amp;nbsp; That is in the form of basic code that can be imported as macros to run in Excel.&amp;nbsp; There are neater and more robust ways of doing it, but this helped resolve which IPs were filling the connection table.&amp;nbsp; At minimum, this gives a code level example of how to read the connection table.&lt;BR /&gt;&lt;BR /&gt;The default expected file name is connections.txt located in the same directory as the wsh, windows scripting host, file.&amp;nbsp; The default output is conntable.csv.&amp;nbsp; Error checking is minimal, so use carefully.&amp;nbsp; &amp;nbsp;Message boxes are used for selection.&lt;BR /&gt;&lt;BR /&gt;Note that some malware detection may block downloading a zip with wsh and bas files.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2020 14:40:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Convert-connection-table-to-csv-using-windows-scripting-host/m-p/102792#M19837</guid>
      <dc:creator>George_Ellis</dc:creator>
      <dc:date>2020-11-20T14:40:06Z</dc:date>
    </item>
  </channel>
</rss>

