<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Ulogd on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/ulogd/</link>
    <description>Recent content in Ulogd on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Fri, 07 Mar 2014 23:19:37 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/ulogd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Suricata and Ulogd meet Logstash and Splunk</title>
      <link>https://home.regit.org/2014/03/suricata-ulogd-splunk-logstash/</link>
      <pubDate>Fri, 07 Mar 2014 23:19:37 +0000</pubDate>
      <guid>https://home.regit.org/2014/03/suricata-ulogd-splunk-logstash/</guid>
      <description>&lt;h4 id=&#34;some-progress-on-the-json-side&#34;&gt;Some progress on the JSON side&lt;/h4&gt;
&lt;p&gt;Suricata 2.0-rc2 is out and it brings some progress on the JSON side. The logging of SSH protocol has been added:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021.png&#34; alt=&#34;Screenshot from 2014-03-07 18:50:21&#34; width=&#34;629&#34; height=&#34;357&#34; class=&#34;aligncenter size-large wp-image-2051&#34; srcset=&#34;https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021.png 629w, https://home.regit.org/uploads/2014/03/Screenshot-from-2014-03-07-185021-300x170.png 300w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;and the &lt;a href=&#34;https://github.com/inliniac/suricata/commit/6c3c234ca5583f420371bc706716e8ae1b0c5a61&#34;&gt;format of timestamp has been updated&lt;/a&gt; to be ISO 8601 compliant and it is now named &lt;code&gt;timestamp&lt;/code&gt; instead of &lt;code&gt;time&lt;/code&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Nftables and the Netfilter logging framework</title>
      <link>https://home.regit.org/2014/02/nftables-and-netfilter-logging-framework/</link>
      <pubDate>Mon, 24 Feb 2014 22:17:22 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/nftables-and-netfilter-logging-framework/</guid>
      <description>&lt;h4 id=&#34;nftables-logging&#34;&gt;Nftables logging&lt;/h4&gt;
&lt;p&gt;If nftables is bringing a lot of changes on user side, this is also true in the logging area.&lt;br&gt;
There is now only one single keyword for logging: &lt;code&gt;log&lt;/code&gt; and this target is using the Netfilter logging framework.&lt;br&gt;
A corollary of that is that why you may not see any log messages even if a rule with &lt;code&gt;log&lt;/code&gt; is matching because the Netfilter logging framework has to be configured.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using ulogd and JSON output</title>
      <link>https://home.regit.org/2014/02/using-ulogd-and-json-output/</link>
      <pubDate>Sun, 02 Feb 2014 16:39:34 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/using-ulogd-and-json-output/</guid>
      <description>&lt;h4 id=&#34;ulogd-and-json-output&#34;&gt;Ulogd and JSON output&lt;/h4&gt;
&lt;p&gt;In February 2014, I’ve &lt;a href=&#34;http://git.netfilter.org/ulogd2/commit/?id=e0ae1870e5b15138c12071d9d96522a2720bf44a&#34;&gt;commited a new output plugin&lt;/a&gt; to &lt;a href=&#34;http://www.netfilter.org/projects/ulogd/index.html&#34;&gt;ulogd&lt;/a&gt;, the userspace logging daemon for Netfilter. This is a &lt;a href=&#34;http://en.wikipedia.org/wiki/JSON&#34;&gt;JSON&lt;/a&gt; output plugin which output logs into a file in JSON format. The interest of the JSON format is that it is easily parsed by software just as logstash. And once data are understood by &lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt;, you can get some nice and useful dashboard in &lt;a href=&#34;http://www.elasticsearch.org/overview/kibana/&#34;&gt;Kibana&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png&#34; alt=&#34;Screenshot from 2014-02-02 13:22:34&#34; width=&#34;695&#34; height=&#34;329&#34; class=&#34;aligncenter size-large wp-image-1896&#34; srcset=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png 1024w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-300x142.png 300w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png 1898w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Investigation on an attack tool used in China</title>
      <link>https://home.regit.org/2014/02/chinese-scanner/</link>
      <pubDate>Sun, 02 Feb 2014 15:28:32 +0000</pubDate>
      <guid>https://home.regit.org/2014/02/chinese-scanner/</guid>
      <description>&lt;h4 id=&#34;log-analysis-experiment&#34;&gt;Log analysis experiment&lt;/h4&gt;
&lt;p&gt;I’ve been playing lately with &lt;a href=&#34;http://logstash.net/&#34;&gt;logstash&lt;/a&gt; using data from the &lt;a href=&#34;http://git.netfilter.org/ulogd2/commit/?id=e0ae1870e5b15138c12071d9d96522a2720bf44a&#34;&gt;ulogd JSON output plugin&lt;/a&gt; and the &lt;a href=&#34;http://pevma.blogspot.fr/2014/02/suricata-idps-and-common-information.html&#34;&gt;Suricata full JSON output&lt;/a&gt; as well as standard system logs.&lt;/p&gt;
&lt;p&gt;&lt;a href=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png&#34; alt=&#34;Screenshot from 2014-02-02 13:22:34&#34; width=&#34;695&#34; height=&#34;329&#34; class=&#34;aligncenter size-large wp-image-1896&#34; srcset=&#34;https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-1024x486.png 1024w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234-300x142.png 300w, https://home.regit.org/uploads/2014/02/Screenshot-from-2014-02-02-132234.png 1898w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Ulogd is getting Netfilter firewall logs from Linux kernel and is writing them in JSON format. Suricata is doing the same with alert and other traces. Logstash is getting both log as well as sytem log. This allows to create some dashboard with information coming from multiple sources. If you want to know how to configure ulogd for JSON output check &lt;a href=&#34;https://home.regit.org/2014/02/using-ulogd-and-json-output/&#34;&gt;this post&lt;/a&gt;. For suricata, you can have a look at &lt;a href=&#34;https://home.regit.org/2014/01/a-bit-of-logstash-cooking/&#34;&gt;this one&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some ulogd db improvements</title>
      <link>https://home.regit.org/2013/05/some-ulogd-db-improvements/</link>
      <pubDate>Tue, 21 May 2013 21:42:57 +0000</pubDate>
      <guid>https://home.regit.org/2013/05/some-ulogd-db-improvements/</guid>
      <description>&lt;h4 id=&#34;some-new-features&#34;&gt;Some new features&lt;/h4&gt;
&lt;p&gt;I’ve just pushed to &lt;a href=&#34;http://git.netfilter.org/ulogd2/&#34;&gt;ulogd tree&lt;/a&gt; a series of patches. They bring two major improvements to database handling:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Backlog system: temporary store SQL query in memory if database is down.&lt;/li&gt;
&lt;li&gt;Ring buffer system: a special mode with a thread to read data from kernel and a thread to do the SQL query.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The first mode is attended for preventing data loss when database is temporary down. The second one is an attempt to improve performance and the resistance to netlink buffer overrun problem.&lt;br&gt;
The modification has been done in the database abstraction layer and it is thus available in MySQL, PostgreSQL and DBI.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Visualize Netfilter accounting in Graphite</title>
      <link>https://home.regit.org/2012/12/visualize-netfilter-accounting-in-graphite/</link>
      <pubDate>Sat, 22 Dec 2012 11:27:09 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/visualize-netfilter-accounting-in-graphite/</guid>
      <description>&lt;h4 id=&#34;ulogd-graphite-output-plugin&#34;&gt;Ulogd Graphite output plugin&lt;/h4&gt;
&lt;p&gt;I’m committed a &lt;a href=&#34;http://git.netfilter.org/cgi-bin/gitweb.cgi?p=ulogd2.git;a=commit;h=8cbeaed5c9b78c8c63f4fb98866722135f46ab86&#34;&gt;new output plugin&lt;/a&gt; for &lt;a href=&#34;http://www.netfilter.org/projects/ulogd/&#34;&gt;ulogd&lt;/a&gt;. The idea is to send &lt;a href=&#34;https://home.regit.org/2012/07/flow-accounting-with-netfilter-and-ulogd2/&#34;&gt;NFACCT accounting data&lt;/a&gt; to a &lt;a href=&#34;http://graphite.wikidot.com/&#34;&gt;graphite server&lt;/a&gt; to be able to display the received data. Graphite is a web application which provide real-time visualization and storage of numeric time-series data.&lt;/p&gt;
&lt;p&gt;Once data are sent to the graphite server, it is possible to use the web interface to setup different dashboard and graphs (including combination and mathematical operation):&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2012/12/graphite.png&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2012/12/graphite-1024x372.png&#34; alt=&#34;&#34; title=&#34;Example Dashboard&#34; width=&#34;695&#34; height=&#34;252&#34; class=&#34;aligncenter size-large wp-image-1388&#34; srcset=&#34;https://home.regit.org/uploads/2012/12/graphite-1024x372.png 1024w, https://home.regit.org/uploads/2012/12/graphite-300x109.png 300w, https://home.regit.org/uploads/2012/12/graphite.png 1920w&#34; sizes=&#34;auto, (max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
