[Olsr-users] How to prioritize OLSR UDP packets.

[Markus Kittenberger]

in the first two tests i did put them into the same flow with different
prios

and in the third test i put in in different flows

regards Markus

p.s. the qdiscs of my previous tests were:

tc qdisc add dev $DEV root handle 1: prio
tc qdisc add dev $DEV parent 1:1 handle 10: sfq perturb 10
tc qdisc add dev $DEV parent 1:2 handle 20: sfq perturb 10
tc qdisc add dev $DEV parent 1:3 handle 30: sfq perturb 10

and there were some other filter priorizing different traffic (olsr, dns,
...), but this should not have interfered with my tests as there was nearly
no other traffic on this link

On Thu, Jan 14, 2010 at 1:25 PM, <(spam-protected)> wrote:

> On 01/13/2010 10:24 PM, Markus Kittenberger wrote:
> > i just testet my own scripts now,..  and they do work mostly as
> expected,..
> >
> > i also had some problems, to get a working setup where i can test if
> > traffix X gets priorized or not
> > (especially as i tried to create the 2 test udp stream on the same host,
> > but i did not investigate further)
> >
> > my test setup
> > a ... b --- c
> >
> > ... is a 100mbit link
> > --- an 5.5mbit 801.11b wireless link capable of (somewhat stable) 2 to
> > 4.5mbit useable udp throughput (in olsr terms its a rock solit ETX 1.0
> > link (20meter but outoor *g))
> >
> > priorization was made on b
> >
> > traffic was created on a (udp port 5001) and b (udp port 5002)
> >
> > tc filter $1 dev $DEV protocol ip parent 1: prio 3 u32 match ip protocol
> > 17 0xff match ip dport 5001 0xffff flowid 1:1
> > tc filter $1 dev $DEV protocol ip parent 1: prio 4 u32 match ip protocol
> > 17 0xff match ip dport 5002 0xffff flowid 1:1
> >
> > 5001: 1.8mbit
> > 5002: 1.2mbit
> >
> > tc filter $1 dev $DEV protocol ip parent 1: prio 19 u32 match ip
> > protocol 17 0xff match ip dport 5001 0xffff flowid 1:1
> > tc filter $1 dev $DEV protocol ip parent 1: prio 3 u32 match ip protocol
> > 17 0xff match ip dport 5002 0xffff flowid 1:1
> >
> > 5001:0.1mbit
> > 5002:1.8mbit
> >
> > tc filter $1 dev $DEV protocol ip parent 1: prio 4 u32 match ip protocol
> > 17 0xff match ip dport 5001 0xffff flowid 1:1
> > tc filter $1 dev $DEV protocol ip parent 1: prio 3 u32 match ip protocol
> > 17 0xff match ip dport 5002 0xffff flowid 1:2
> >
> > 5001 4.0mbit
> > 5002 0.0mbit (so no chance for traffic on port 5002, or infact for any
> > traffic on flowid 1:2 or 1:3)
>
> Hello.
> You did three tests and just changed the value of the "prio" parameter
> in each test, right? In the first two tests do you classify the two
> flows into the same class (1:1), or it's a typo?
>
> Clauz
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20100114/3ef93e4c/attachment.html>