<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Svn on Inliniac</title>
    <link>https://inliniac.net/blog/tag/svn/</link>
    <description>Recent content in Svn on Inliniac</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 02 Oct 2007 19:11:12 +0000</lastBuildDate>
    <atom:link href="https://inliniac.net/blog/tag/svn/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vuurmuur gets traffic shaping</title>
      <link>https://inliniac.net/blog/2007/10/02/vuurmuur-gets-traffic-shaping/</link>
      <pubDate>Tue, 02 Oct 2007 19:11:12 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/10/02/vuurmuur-gets-traffic-shaping/</guid>
      <description>&lt;p&gt;The last weeks I&amp;rsquo;ve been working on adding traffic shaping support to Vuurmuur. The work is largely done, only the GUI part is still missing. But using vuurmuur_script it is already usable in the current SVN trunk. I&amp;rsquo;ve written before about my shaping ideas &lt;a href=&#34;http://www.inliniac.net/blog/2006/08/16/vuurmuur-first-baby-steps-in-traffic-shaping.html&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The support currently focuses on three different options:&lt;/p&gt;&#xA;&lt;p&gt;1. Limiting bandwidth usage by rules.&lt;/p&gt;&#xA;&lt;p&gt;Per rule a limit can be set for the maximum amount of bandwidth all traffic from this rule uses. Both directions of a connection have different limits. The in_max and out_max options can be added to existing rules for this. The syntax of the in_max and out_max is simple: out_max=15kbps means that traffic in the source to destination direction of a rule can at max use 15 kb/s.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vuurmuur NFQUEUE support</title>
      <link>https://inliniac.net/blog/2007/05/22/vuurmuur-nfqueue-support/</link>
      <pubDate>Tue, 22 May 2007 13:21:23 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/05/22/vuurmuur-nfqueue-support/</guid>
      <description>&lt;p&gt;Vuurmuur supported the QUEUE target for a while already, even though it needed a little bit of a hack to handle the &lt;em&gt;state&lt;/em&gt;. This is because the iptables ruleset Vuurmuur creates is quite simple: after a few general protection rules it starts by accepting traffic with the state &lt;em&gt;established&lt;/em&gt;. Since there is no way to say &amp;lsquo;queue established traffic that was queued before&amp;rsquo; in iptables I decided to use traffic marking to distinguish between traffic to be queued or accepted. But there was a problem with this approach. I didn&amp;rsquo;t want to cripple the marking of traffic for other purposes, such as traffic shaping and routing, so I decided to use mark-ranges to either queue or accept:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline updated to 2.6.1.5 in SVN</title>
      <link>https://inliniac.net/blog/2007/05/14/snort_inline-updated-to-2615-in-svn/</link>
      <pubDate>Mon, 14 May 2007 20:02:12 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/05/14/snort_inline-updated-to-2615-in-svn/</guid>
      <description>&lt;p&gt;SourceFire just released Snort 2.6.1.5 so I have updated our patch to that. You can get it by checking out SVN with the following command:&lt;/p&gt;&#xA;&lt;p&gt;svn co &lt;a href=&#34;https://snort-inline.svn.sourceforge.net/svnroot/snort-inline/trunk&#34;&gt;https://snort-inline.svn.sourceforge.net/svnroot/snort-inline/trunk&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;Check it out! :)&lt;/p&gt;</description>
    </item>
    <item>
      <title>Vuurmuur SVN now open</title>
      <link>https://inliniac.net/blog/2007/05/14/vuurmuur-svn-now-open/</link>
      <pubDate>Mon, 14 May 2007 16:57:09 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/05/14/vuurmuur-svn-now-open/</guid>
      <description>&lt;p&gt;For version control for Vuurmuur development I have been using Bazaar and Bazaar-NG. I&amp;rsquo;ve never really gotten used to Bazaar-NG. I admit that this is mostly due to lack of trying. For the Snort_inline project I have gotten used to Subversion, for which I even bought a book (Practical Subversion by Garrett Rooney, great book!). So recently I decided to move Vuurmuur also to SVN, for these three reasons:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;this way I need to work with only one tool&lt;/li&gt;&#xA;&lt;li&gt;people in the OSS community are more used to SVN so it&amp;rsquo;s easier for users and people interested in contributing&lt;/li&gt;&#xA;&lt;li&gt;Bazaar-NG doesn&amp;rsquo;t support SVN-style tags, except (I think) for the latest version which is not in my distro&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;So the SVN repository is now open. It is hosted at SourceForge at:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Snort_inline updated to 2.6.1.4 in SVN</title>
      <link>https://inliniac.net/blog/2007/04/20/snort_inline-updated-to-2614-in-svn/</link>
      <pubDate>Fri, 20 Apr 2007 16:47:33 +0000</pubDate>
      <guid>https://inliniac.net/blog/2007/04/20/snort_inline-updated-to-2614-in-svn/</guid>
      <description>&lt;p&gt;After moving, which went fine, I now finally have some real coding time again. The last week I have been updating and fixing various parts of Snort_inline. The most important change was the update to Snort version 2.6.1.4, which contains security fixes. William also found an issue with the Stream4inline code. The issue was that the memcap that the admin sets to limit the amount of memory used by stream4 wasn&amp;rsquo;t properly enforced.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
