From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc problem
Date: Thu, 03 Apr 2003 20:12:35 +0000 [thread overview]
Message-ID: <marc-lartc-104940084511205@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104939908108556@msgid-missing>
On Thursday 03 April 2003 21:43, Alexandru Coseru wrote:
> Hello..
>
> I have a linux box and I want to make priority on traffic generated by my
> LAN's computers..
> I don't have a guaranted bandwidth, so I wanna use sfq...
>
> I want to make traffic to port 80 , 443 , 25 & 110 PRIORITY 1
>
> Traffic src or dest 192.168.0.2 to make priority 2
>
> And the rest to put it in proiority 3..
>
>
> I did the following :
>
> tc qdisc add dev eth0 root handle 1: prio
>
> tc qdisc add dev eth0 parent 1:1 handle 10: sfq
> tc qdisc add dev eth0 parent 1:2 handle 20: sfq
> tc qdisc add dev eth0 parent 1:3 handle 30: sfq
>
> now , when i do :
>
> tc filter add dev eth0 protocol ip parent 10: prio 1 u32 match ip sport 80
> 0xffff flowid 10:1
>
> I get an : RTNETLINK answers: Invalid argument
>
> but , if I'm typing
>
> tc filter add dev eth0 protocol ip parent 1: prio 1 u32 match ip sport 80
> 0xffff flowid 1:1
> it's working (at least I don't have any messages..)
Euh, your first command is wrong and your second not. You have to attach the
filter to the root qdisc (parent 1:) and point it to a class (flowid 1:1)
like you did in the first filter command. That's all.
stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-04-03 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 19:43 [LARTC] tc problem Alexandru Coseru
2003-04-03 20:12 ` Stef Coene [this message]
2003-05-02 12:20 ` Alexandru Coseru
2003-05-02 17:09 ` Stef Coene
2003-05-07 12:22 ` Catalin BOIE
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=marc-lartc-104940084511205@msgid-missing \
--to=stef.coene@docum.org \
--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.