• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Traffic Shaping, Floating Rules, uTorrent

Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
5 Posts 3 Posters 12.5k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    Jerubei
    last edited by Jul 30, 2009, 12:29 PM

    Hey folks,

    Quite new to shaping, so don't jump on me :) I want to shape torrent traffic and also give it lowest priority, but to achieve this, I must be able to put the torrent traffic into the P2P queues.

    I see that the Shaper Wizard created the following rules for P2P traffic:

    
    Proto  	Source  	Port  	Destination  	Port  	Gateway  	Queue  	Schedule  	Description
    TCP  	 *  	 *  	 *  	 6881 - 6999  	 * 	 qP2P  	    	 m_P2P BitTorrent outbound
    UDP 	* 	* 	* 	6881 - 6999 	* 	qP2P 	  	m_P2P BitTorrent outbound  
    
    

    The way I interpret this - all outbound traffic on port range 6881 - 6999 will by classified as P2P traffic and put in the appropriate qP2P queue, which will allow traffic shaping. Is this correct? If so, how do I limit utorrent outbound ports to 6881 - 6999 and isn't this too tight of a range?

    I also see that the "Ackqueue/Queue" is set to "None/qP2P". Shouldn't it be "qACK/qP2P"?

    1 Reply Last reply Reply Quote 0
    • E
      eri--
      last edited by Jul 30, 2009, 1:16 PM

      Use layer7 if you want more control than that.

      1 Reply Last reply Reply Quote 0
      • J
        Jerubei
        last edited by Jul 30, 2009, 10:51 PM

        @ermal:

        Use layer7 if you want more control than that.

        I'm trying to learn traffic shaping in pfsense, so I was hoping that you (or someone else) could confirm my assumptions above. I'll also try using Layer 7 (although I can't find any detailed info on its setup in pfsense either).

        1 Reply Last reply Reply Quote 0
        • S
          stompro
          last edited by Aug 19, 2009, 11:31 PM

          @Jerubei:

          I'm trying to learn traffic shaping in pfsense, so I was hoping that you (or someone else) could confirm my assumptions above. I'll also try using Layer 7 (although I can't find any detailed info on its setup in pfsense either).

          Jerubei,
          Take a look at this recent post by ermal where he goes into detail on how to use the layer 7 feature.
          http://forum.pfsense.org/index.php/topic,17347.0.html

          I'm working on the traffic shaping guide on the wiki also, that might help you with some of the setup.
          http://doc.pfsense.org/index.php/Traffic_Shaping_Guide
          Josh

          Hardware used: Alix 2D13 X 10, APU2D4 X 10, SG-2200 X 10, SG-2440 X 4

          1 Reply Last reply Reply Quote 0
          • J
            Jerubei
            last edited by Aug 25, 2009, 10:13 PM

            @stompro:

            @Jerubei:

            I'm trying to learn traffic shaping in pfsense, so I was hoping that you (or someone else) could confirm my assumptions above. I'll also try using Layer 7 (although I can't find any detailed info on its setup in pfsense either).

            Jerubei,
            Take a look at this recent post by ermal where he goes into detail on how to use the layer 7 feature.
            http://forum.pfsense.org/index.php/topic,17347.0.html

            I'm working on the traffic shaping guide on the wiki also, that might help you with some of the setup.
            http://doc.pfsense.org/index.php/Traffic_Shaping_Guide
            Josh

            Thank you, this is a very useful reply!

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received