1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Inbound Limit classifications

Discussion in 'Tomato Firmware' started by Daystrom, Apr 7, 2008.

  1. Daystrom

    Daystrom Addicted to LI Member

    I've been reading a lot about QoS and outbound limits/classifications but am a bit confused on the Inbound classifications.

    The outbound classifications are all based on destination ports, etc. The keyword is destination.

    How do these classifications work on Inbound connections? I.E. If a classification says Destination port 80 is High how does this same rule apply for incoming since the incoming port is different? Do the rules just reverse for incoming packets?

    Just trying to understand :smile:
     
  2. szfong

    szfong Network Guru Member

    Inbound traffic not easily controllable other than blocking/dropping packets.
     
  3. Daystrom

    Daystrom Addicted to LI Member

    So I've read but how do the classifications play out for incoming?

    Say WWW is set for high outgoing, how does that classification work on the incoming side?
     
  4. szfong

    szfong Network Guru Member

    If you allocate enough bandwidth for it, it accepted, or else it dropped, and a retransmission occurs. It's very inefficuent. QoS is not performed for incoming stuff.
     
  5. LLigetfa

    LLigetfa LI Guru Member

    If you throttle outgoing ACKs, it will have the effect of slowing the incoming traffic. It's the same as when you overload the upload side with torrents, it affects your download.
     
  6. Daystrom

    Daystrom Addicted to LI Member

    But what do the classifications under Inbound mean? Highest, High, Medium, etc, etc.

    If I set my inbound limit to 6800 kb/s and then set High to 90% - what is being dropped? Who or what determines what Highest, High, etc. means on the incoming side?
     
  7. Toastman

    Toastman Super Moderator Staff Member Member

    Conntrack is responsible for keeping track of incoming connections and relating them to the outgoing connections which requested a reply. QOS traffic shaping can then be done on those incoming packets, which have now been identified, by dropping them as necessary.

    On the incoming side, please don't consider them as "priorities" but rather as just "traffic bands"...

    i.e. Outgoing traffic for band "HIGH" will result in related incoming traffic being identified by Conntrack as corresponding to the HIGH band, and thus you now need to apply your traffic shaping to the *incoming* HIGH "band" .

    Is that what you needed?
     
  8. esaym

    esaym LI Guru Member

    I think that is more of a bug in the gui. Just set a global limit and then use that same limit in the highest class only. That is what I did and it worked well. I had to really kill the download though. My connection can do 7000 down but I had to set it to 6000 to get stable pings, although even at 6000 it was still downloading at 6800 :)
     

Share This Page