netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: PRIO qdisc + iptables TOS target
       [not found] <4bd150a7.0aaa660a.1872.ffffde4c@mx.google.com>
@ 2010-04-23  7:53 ` Salatiel Filho
  0 siblings, 0 replies; only message in thread
From: Salatiel Filho @ 2010-04-23  7:53 UTC (permalink / raw)
  To: arimus.uk, netfilter-devel, lartc

Why ? Isn't the mapping done automatically based on the packet TOS ?

At least accoding to http://www.opalsoft.net/qos/DS-23.htm

   	"If you do not provide tc filters to classify traffic", the PRIO
qdisc looks at the TC_PRIO
priority to decide how to enqueue traffic. The kernel assigns each
packet a TC_PRIO priority,
based on TOS flags or socket options passed by the application.
  	The TC_PRIO is decided based on the TOS, and mapped as follows:"


[]'s
Salatiel

"O maior prazer do inteligente é bancar o  idiota
   diante de um  idiota que banca o inteligente".




On Fri, Apr 23, 2010 at 04:47,  <arimus.uk@googlemail.com> wrote:
> You need a filter (tc) to direct traffic with a tos field of 0x10 to the prio queue.
> --- Original Message ---
> From: Salatiel Filho <salatiel.filho@gmail.com>
> Sent: Thu, 22 Apr 2010 21:46:25 Localtime
> To: netfilter@vger.kernel.org,
>        lartc@mailman.ds9a.nl
> Subject: PRIO qdisc + iptables TOS target
>
> i am trying to do some traffic classification using the PRIO qdisc and
> i am having a few problems.
>
> I have a root htb class:
>
> tc qdisc add dev imq0 root handle 1: htb  default 255 r2q 1
> tc class add dev imq0 parent 1:  classid 1:1 htb rate 768kbit
>
> and a child PRIO
> tc class add dev imq0 parent 1:1 classid  1:99 htb rate 96kbit ceil
> 600kbit prio 0
> tc qdisc add dev imq0 parent 1:99 prio
> tc filter add dev imq0 parent 1: protocol ip  prio 7 u32 match ip dst
> 192.168.1.99 flowid 1:99
>
>
>
>
> the result is:
>
> # tc - s class ls dev imq0
>
> class htb 1:1 root rate 768000bit ceil 768000bit burst 1599b cburst 1599b
>  Sent 2451 bytes 22 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 1016bit 1pps backlog 0b 0p requeues 0
>  lended: 0 borrowed: 0 giants: 0
>  tokens: 250000 ctokens: 250000
>
> class htb 1:129 parent 1:1 leaf 816c: prio 0 rate 96000bit ceil
> 600000bit burst 1599b cburst 1599b
>  Sent 7269 bytes 50 pkt (dropped 0, overlimits 0 requeues 0)
>  rate 1416bit 1pps backlog 0b 0p requeues 0
>
> class prio 816c:1 parent 816c:
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> class prio 816c:2 parent 816c:
>  Sent 7269 bytes 50 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
> class prio 816c:3 parent 816c:
>  Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
>  backlog 0b 0p requeues 0
>
>
>
> The problem is that when i want to give a higher priority for some
> ports the packets keep going to 816:2 instead of 816:1
>
> my iptables rules:
>
>
> iptables -t mangle -I PREROUTING  -p tcp -m multiport --ports 22,80 -j
> TOS  --set-tos 0x10
>
> Shouldn't this rule make all packets from/to port 22 and 80 go through
> 816c:1 PRIO class ?
>
>
> Any help is very welcome.
>
>
> []'s
> Salatiel
>
> "O maior prazer do inteligente é bancar o  idiota
>   diante de um  idiota que banca o inteligente".
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2010-04-23  7:54 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <4bd150a7.0aaa660a.1872.ffffde4c@mx.google.com>
2010-04-23  7:53 ` PRIO qdisc + iptables TOS target Salatiel Filho

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).