simplest shaper to deal with bufferbloat



  • Would this be sufficient for dealing with bufferbloat...

    <shaper>
    	<queue>
    		<interface>wan</interface>
    		<name>wan</name>
    		<scheduler>CODELQ</scheduler>
    		<bandwidth>15</bandwidth>
    		<bandwidthtype>Mb</bandwidthtype>
    		<enabled>on</enabled>
    	</queue>
    </shaper>
    

    Or would this be better...

    <shaper>
    	<queue>
    		<interface>wan</interface>
    		<name>wan</name>
    		<scheduler>FAIRQ</scheduler>
    		<bandwidth>15</bandwidth>
    		<bandwidthtype>Mb</bandwidthtype>
    		<enabled>on</enabled>
    		<queue>
    			<interface>wan</interface>
    			<priority>1</priority>
    			<name>wan-codel</name>
    			<bandwidth>15</bandwidth>
    			<bandwidthtype>Mb</bandwidthtype>
    			<enabled>on</enabled>
    			<default>default</default>
    			<codel>yes</codel>
    		</queue>
    	</queue>
    </shaper>
    

    Is shaping the LAN interface necessary if bufferbloat is my only real concern?


  • Netgate

    Anything that will limit sending traffic faster than the ISP can deal with it without buffering will work.

    I would just set up PRIQ on WAN with a bandwidth of about 90% of what you can send. Set up one child default queue. With just the default queue you don't have to worry about matching traffic and putting it in the queue.

    Then tweak the bandwidth up until you start to get bloat/buffering then back it off a little.

    You can do CODEL or whatever, but the ones that need to implement CODEL are the upstream ISP who is doing the buffering.

    Done.


 

© Copyright 2002 - 2018 Rubicon Communications, LLC | Privacy Policy