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

EMule upload traffic shows up in qwanacks.

Traffic Shaping
2
3
3.3k
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.
  • G
    gd
    last edited by Sep 2, 2006, 6:36 AM

    Hi.

    I tried to assign emule traffic a lower priority using the EZ Shaper wizard (I only had to change a few ports because I don't use emule's default ones). I tested the rules with amule under linux but the result was not what I expected.
    I had amule running with a (limited) constant upload rate of 10 kByte/s, no downloads and no other traffic on the local net. But the upload traffic neither showed up in qP2PUp nor in qwandef, but in qwanacks with a rate of 80-90 Kb/s  :o

    No, I didn't set the wrong queue in the shaper rules. A closer look at the traffic showed that amule sets the ACK flag for all outgoing payload packages (do all emule clients behave this way?)

    Any idea how this problem could be solved? I mean, this situation is worse than having no shaper at all.
    What about removing the priority queue for P2P traffic (changing "… queue (qP2PUp, qwanacks) ..." to "... queue (qP2PUp) ...")?

    bye.

    1 Reply Last reply Reply Quote 0
    • B
      billm
      last edited by Sep 2, 2006, 4:50 PM

      @gd:

      Hi.

      I tried to assign emule traffic a lower priority using the EZ Shaper wizard (I only had to change a few ports because I don't use emule's default ones). I tested the rules with amule under linux but the result was not what I expected.
      I had amule running with a (limited) constant upload rate of 10 kByte/s, no downloads and no other traffic on the local net. But the upload traffic neither showed up in qP2PUp nor in qwandef, but in qwanacks with a rate of 80-90 Kb/s  :o

      No, I didn't set the wrong queue in the shaper rules. A closer look at the traffic showed that amule sets the ACK flag for all outgoing payload packages (do all emule clients behave this way?)

      Any idea how this problem could be solved? I mean, this situation is worse than having no shaper at all.
      What about removing the priority queue for P2P traffic (changing "… queue (qP2PUp, qwanacks) ..." to "... queue (qP2PUp) ...")?

      bye.

      Only empty acks should be hitting that queue.  We've talked about this.  Concensus is that the shaper needs to be rewritten (again), feel free to start on this as I'm not likely to get to it any time soon.

      –Bill

      pfSense core developer
      blog - http://www.ucsecurity.com/
      twitter - billmarquette

      1 Reply Last reply Reply Quote 0
      • B
        billm
        last edited by Sep 2, 2006, 4:51 PM

        BTW, priority doesn't really mean much in the shaper anyway.

        –Bill

        pfSense core developer
        blog - http://www.ucsecurity.com/
        twitter - billmarquette

        1 Reply Last reply Reply Quote 0
        1 out of 3
        • First post
          1/3
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.