<?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>Kernel on To Linux and beyond !</title>
    <link>https://home.regit.org/tags/kernel/</link>
    <description>Recent content in Kernel on To Linux and beyond !</description>
    <generator>Hugo</generator>
    <language>fr</language>
    <lastBuildDate>Tue, 26 Mar 2013 15:24:45 +0000</lastBuildDate>
    <atom:link href="https://home.regit.org/feed/tags/kernel/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>WiFi interface and suricata AF_PACKET IPS mode</title>
      <link>https://home.regit.org/2013/03/wifi-interface-and-suricata-af_packet-ips-mode/</link>
      <pubDate>Tue, 26 Mar 2013 15:24:45 +0000</pubDate>
      <guid>https://home.regit.org/2013/03/wifi-interface-and-suricata-af_packet-ips-mode/</guid>
      <description>&lt;h4 id=&#34;not-usual-setup-can-lead-to-surprise&#34;&gt;Not usual setup can lead to surprise&lt;/h4&gt;
&lt;p&gt;The 5th of December 2012, I’ve setup suricata in AF_PACKET IPS mode between a WiFi interface and an Ethernet interface. The result was surprising as it was leading to a crash after some time:&lt;br&gt;
&lt;a href=&#34;https://home.regit.org/uploads/2013/03/IMG_20130326_150421.jpg&#34;&gt;&lt;img loading=&#34;lazy&#34; decoding=&#34;async&#34; src=&#34;https://home.regit.org/uploads/2013/03/IMG_20130326_150421-300x225.jpg&#34; alt=&#34;&#34; title=&#34;IMG_20130326_150421&#34; width=&#34;300&#34; height=&#34;225&#34; class=&#34;aligncenter size-medium wp-image-1613&#34; srcset=&#34;https://home.regit.org/uploads/2013/03/IMG_20130326_150421-300x225.jpg 300w, https://home.regit.org/uploads/2013/03/IMG_20130326_150421-1024x768.jpg 1024w&#34; sizes=&#34;auto, (max-width: 300px) 85vw, 300px&#34; /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The issue was linked with the defrag option of AF_PACKEt fanout. I’ve proposed a &lt;a href=&#34;http://comments.gmane.org/gmane.linux.network/251955&#34;&gt;patch the 7th Dec 2012&lt;/a&gt; and after a discussion with David Miller and Johannes Berg, Johannes has proposed a &lt;a href=&#34;https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1bf3751ec90cc3174e01f0d701e8449ce163d113&#34;&gt;better patch which was included in official tree&lt;/a&gt;. So the problem is fixed for kernel superior or equal to 3.7.&lt;/p&gt;</description>
    </item>
    <item>
      <title>About Suricata and a kernel oops in AF_PACKET</title>
      <link>https://home.regit.org/2012/12/af-packet-oops/</link>
      <pubDate>Wed, 05 Dec 2012 10:38:19 +0000</pubDate>
      <guid>https://home.regit.org/2012/12/af-packet-oops/</guid>
      <description>&lt;h4 id=&#34;introduction&#34;&gt;Introduction&lt;/h4&gt;
&lt;p&gt;Kernel oops have been reported by some users running Suricata with AF_PACKET multiple thread capture activated. This is due to a bug I’ve introduced in AF_PACKET when fixing an other bug.&lt;/p&gt;
&lt;h4 id=&#34;which-kernel-not-to-use-with-suricata-in-af_packet-mode&#34;&gt;Which kernel not to use with Suricata in AF_PACKET mode&lt;/h4&gt;
&lt;p&gt;The following kernel version will surely crash if Suricata or any other program is used with &lt;strong&gt;AF_PACKET&lt;/strong&gt; capture &lt;strong&gt;with multiple capture threads&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Linux 3.2.30 to 3.2.33&lt;/li&gt;
&lt;li&gt;Linux 3.4.12 to 3.4.18&lt;/li&gt;
&lt;li&gt;Linux 3.5.5 to 3.5.7&lt;/li&gt;
&lt;li&gt;Linux 3.6.0 to 3.6.6&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If only one capture thread is used there is no risk of crash. If you are running a vulnerable kernel, your configuration should looks like:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Minimal linux kernel config for Virtualbox</title>
      <link>https://home.regit.org/2012/08/minimal-linux-kernel-config-for-virtualbox/</link>
      <pubDate>Fri, 17 Aug 2012 08:23:28 +0000</pubDate>
      <guid>https://home.regit.org/2012/08/minimal-linux-kernel-config-for-virtualbox/</guid>
      <description>&lt;p&gt;I was looking for some minimal Linux kernel configuration for Virtualbox guest and did only find some old one. I thus decide to build one and to publish them.&lt;br&gt;
They are available on github: &lt;a href=&#34;https://github.com/regit/regit-config&#34;&gt;regit-config&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For now, the only published configuration are for Linux kernel 3.5:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/regit/regit-config/raw/master/virtualbox/config-3.5-vbox&#34;&gt;config-3.5-vbox&lt;/a&gt;: A minimal Linux kernel config for Virtualbox&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://github.com/regit/regit-config/raw/master/virtualbox/config-3.5-vbox-no-netfilter&#34;&gt;config-3.5-vbox-no-netfilter&lt;/a&gt;: Same as previous config with Netfilter disabled&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</description>
    </item>
  </channel>
</rss>
