<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Inliniac &#187; Traffic Shaping</title>
	<atom:link href="http://www.inliniac.net/blog/tag/traffic-shaping/feed" rel="self" type="application/rss+xml" />
	<link>http://www.inliniac.net/blog</link>
	<description>Everything inline.</description>
	<lastBuildDate>Thu, 29 Jul 2010 19:38:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>GUI part of Vuurmuur traffic shaping done</title>
		<link>http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html</link>
		<comments>http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html#comments</comments>
		<pubDate>Thu, 01 Nov 2007 23:03:18 +0000</pubDate>
		<dc:creator>Victor Julien</dc:creator>
				<category><![CDATA[Traffic Shaping]]></category>
		<category><![CDATA[Vuurmuur]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[vuurmuur-conf]]></category>

		<guid isPermaLink="false">http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html</guid>
		<description><![CDATA[The GUI part of Vuurmuur&#8217;s traffic shaping is done. That means it&#8217;s in a usable state. It&#8217;s probably rough around the edges, but anyone is invited to give it a try. Below two screens. The per rule shaping settings. The per interface settings for the shaping. Expect an alpha release soon!]]></description>
			<content:encoded><![CDATA[<p>The GUI part of Vuurmuur&#8217;s traffic shaping is done. That means it&#8217;s in a usable state. It&#8217;s probably rough around the edges, but anyone is invited to give it a try. Below two screens.</p>
<p><a href="http://www.inliniac.net/blog/wp-content/uploads/2007/11/vuurmuur-shape-rule.png" title="Vuurmuur shape rule settings."></a></p>
<p style="text-align: center"><a href="http://www.inliniac.net/blog/wp-content/uploads/2007/11/vuurmuur-shape-rule.png" title="Vuurmuur shape rule settings."><img src="http://www.inliniac.net/blog/wp-content/uploads/2007/11/vuurmuur-shape-rule.png" alt="Vuurmuur shape rule settings." /></a></p>
<p align="center">The per rule shaping settings.</p>
<p><a href="http://www.inliniac.net/blog/wp-content/uploads/2007/11/vuurmuur-shape-iface.png" title="Vuurmuur shape interface settings."></a></p>
<p style="text-align: center"><a href="http://www.inliniac.net/blog/wp-content/uploads/2007/11/vuurmuur-shape-iface.png" title="Vuurmuur shape interface settings."><img src="http://www.inliniac.net/blog/wp-content/uploads/2007/11/vuurmuur-shape-iface.png" alt="Vuurmuur shape interface settings." /></a></p>
<p align="center">The per interface settings for the shaping.</p>
<p>Expect an alpha release soon! <img src='http://www.inliniac.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.inliniac.net/blog/2007/11/02/gui-part-of-vuurmuur-traffic-shaping-done.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Vuurmuur gets traffic shaping</title>
		<link>http://www.inliniac.net/blog/2007/10/02/vuurmuur-gets-traffic-shaping.html</link>
		<comments>http://www.inliniac.net/blog/2007/10/02/vuurmuur-gets-traffic-shaping.html#comments</comments>
		<pubDate>Tue, 02 Oct 2007 19:11:12 +0000</pubDate>
		<dc:creator>Victor Julien</dc:creator>
				<category><![CDATA[Traffic Shaping]]></category>
		<category><![CDATA[Vuurmuur]]></category>
		<category><![CDATA[svn]]></category>

		<guid isPermaLink="false">http://www.inliniac.net/blog/2007/10/02/vuurmuur-gets-traffic-shaping.html</guid>
		<description><![CDATA[The last weeks I&#8217;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&#8217;ve written before about my shaping ideas here. The support currently focuses on three different options: 1. Limiting [...]]]></description>
			<content:encoded><![CDATA[<p>The last weeks I&#8217;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&#8217;ve written before about my shaping ideas <a href="http://www.inliniac.net/blog/2006/08/16/vuurmuur-first-baby-steps-in-traffic-shaping.html">here</a>.</p>
<p>The support currently focuses on three different options:</p>
<p>1. Limiting bandwidth usage by rules.</p>
<p>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.</p>
<p>2. Guaranteeing bandwidth to rules.</p>
<p>Again per rule a guaranteed minimum of available bandwidth can be configured. This way you can for example make sure your VoIP calls get enough. It&#8217;s important to not over commit the bandwidth. If you do that Vuurmuur will issue a warning but will still work because HTB, the used scheduler, accepts it as well. In this case the minimal bandwidth can not be guaranteed. To use this option add the in_min and out_min options. The syntax is the same as with in_max/out_max.</p>
<p>3. Prioritizing rules.</p>
<p>Like the first two options the priority can be set per rule. It&#8217;s a number where 1 is the highest prio. The default prio is 3. The syntax is prio=1. The lowest prio possible is 255.</p>
<p>For each interface, Vuurmuur needs to know the maximal bandwidth. Also, the shaping can be enabled and disabled on a per interface basis. Because shaping is attached to interfaces, rules using source and/or destination &#8216;any&#8217; or &#8216;firewall(any)&#8217; won&#8217;t be able to shape. Also, only outgoing shaping is supported, which is no problem in a gateway setup because then all traffic is outgoing on one of the interfaces, but on traffic from and to the firewall, this can be a limitation.</p>
<p>For example, to set the bandwidth in the interface &#8216;inet-nic&#8217; which has a bandwidth of 3072kbit/512kbit, use the following vuurmuur_script commands:</p>
<blockquote><p> vuurmuur_script -M -i inet-nic -V SHAPE -S Yes<br />
vuurmuur_script -M -i inet-nic -V BW_IN -S 3<br />
vuurmuur_script -M -i inet-nic -V BW_IN_UNIT -S mbit<br />
vuurmuur_script -M -i inet-nic -V BW_OUT -S 512<br />
vuurmuur_script -M -i inet-nic -V BW_OUT_UNIT -S kbit</p></blockquote>
<p>Using vuurmuur_conf, it&#8217;s already possible to set the location of the tc binary. Look at &#8216;Vuurmuur Config -&gt; General&#8217;.</p>
<p>An example of what a full rule using shaping can look like:</p>
<blockquote><p> accept service ftp from local.lan to world.inet options prio=2, in_max=200kbps, out_max=15kbps</p></blockquote>
<p>This example limits HTTP downloading to a speed of 200kb/s and uploading to 15kb/s.</p>
<p>The coming days and weeks I&#8217;ll finish the GUI support and release a test version.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.inliniac.net/blog/2007/10/02/vuurmuur-gets-traffic-shaping.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
