All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edgar Merino <donvodka@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Help needed with HTB
Date: Tue, 06 Mar 2007 23:03:36 +0000	[thread overview]
Message-ID: <45EDF348.4040507@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 941 bytes --]

Hello, a few days ago I sent an email asking for help with my tc htb 
rules I've got (a script), but I'm not sure if that email got to you... 
anyway, I'm sending it again along with my htb script and I'll tell you 
the problem once again:

I have a computer with ip 192.168.0.100 which is acting as a p2p server, 
so I want to shape traffic coming out from that ip, I have a linux box 
acting as a router with two NICs, server ip is 192.168.0.1. So I hope 
you can take a look at it and tell me why is it that everytime I have 
mldonkey or any other p2p software running on that computer I experience 
a lot of latency in my whole network with http traffic, maybe someone 
can help me out specify the burst and cburst parameters... and maybe 
even the quantum parameter, and some little explanation on it since I 
haven't been able to understand what the benefits of this parameters are.

Hope you can give me a hand on this,

Edgar Merino

[-- Attachment #2: layer7ru.txt --]
[-- Type: text/plain, Size: 2141 bytes --]

#!/bin/sh

### Dispositivo de upload (externo) ###
DEV=eth0

### Bajar la cola the $DEV y el MTU###
ip link set dev $DEV qlen 30
ip link set dev $DEV mtu 1000

### BORRADO DE REGLAS Y CADENAS de la tabla mangle ###
iptables -t mangle -F
iptables -t mangle -X

## BORRADO DE ROOT QDISC EN $DEV
tc qdisc del dev $DEV root

### IPTABLES RULES ###
P2P_IP=192.168.0.100
SSH_PORT=9000

iptables -t mangle -A FORWARD -s $P2P_IP -o $DEV -j MARK --set-mark 1
iptables -t mangle -A OUTPUT -o $DEV -p tcp --sport $SSH_PORT -j MARK --set-mark 2
iptables -t mangle -A POSTROUTING -o $DEV -s ! $P2P_IP -m length --length :64 -j MARK --set-mark 3

### CLASES ###
SSH=1:10
P2P=1:20
ACK=1:40
DEF=1:30

## HERE I USE $PARENT_RATE TO LIMIT BORROWING FROM P2P CLASS FROM PARENT, AND I PUT $MAX_RATE FOR LOW PRIO CLASSES SO THEY ALWAYS GET THE RATE THEY NEED (THIS TRICK SEEMS TO HELP) ##
MAX_RATE=25kbps
PARENT_RATE=10kbps
P2P_UP=10kbps

tc qdisc add dev $DEV root handle 1: htb default 30
tc class add dev $DEV parent 1: classid 1:1 htb rate $PARENT_RATE burst 6k cburst 3k
tc class add dev $DEV parent 1:1 classid $P2P htb rate $P2P_UP ceil $P2P_UP burst 1k cburst 1k prio 2
tc class add dev $DEV parent 1:1 classid $SSH htb rate 5kbps ceil 10kbps burst 6k cburst 3k prio 0
## Is this really needed?
tc class add dev $DEV parent 1:1 classid $ACK htb rate $MAX_RATE ceil $MAX_RATE burst 6k cburst 3k prio 0

## DEFAULT CLASS
tc class add dev $DEV parent 1:1 classid $DEF htb rate $MAX_RATE ceil $MAX_RATE burst 6k cburst 3k prio 1 

### Se agregan qdisc sfq para garantizar un manejo de ancho de banda justo ###
tc qdisc add dev $DEV parent $SSH handle 10: sfq perturb 10
tc qdisc add dev $DEV parent $DEF handle 30: sfq perturb 10
tc qdisc add dev $DEV parent $P2P handle 20: sfq perturb 10

### Filtros para controlar el trafico marcado (especificamente, P2P y SSH)
iptables -t mangle -A FORWARD -o $DEV -s $P2P_IP -m mark --mark 1 -j CLASSIFY --set-class $P2P
iptables -t mangle -A OUTPUT -o $DEV -s ! $P2P_IP -m mark --mark 2 -j CLASSIFY --set-class $SSH
iptables -t mangle -A POSTROUTING -o $DEV -s ! $P2P_IP -m mark --mark 3 -j CLASSIFY --set-class $ACK

[-- Attachment #3: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-03-06 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 23:03 Edgar Merino [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-03 19:44 [LARTC] Help needed with HTB Andy Furniss

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45EDF348.4040507@gmail.com \
    --to=donvodka@gmail.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.