From: "Ronan LAVIEC" <ronan.laviec@club-internet.fr>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Incomprehensive problem with tc filter & mangle...
Date: Wed, 08 Jan 2003 18:57:57 +0000 [thread overview]
Message-ID: <marc-lartc-104205237314554@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104197594226744@msgid-missing>
----- Original Message -----
From: "Stef Coene" <stef.coene@docum.org>
To: "Ronan LAVIEC" <ronan.laviec@club-internet.fr>; <lartc@mailman.ds9a.nl>
Sent: Wednesday, January 08, 2003 7:32 PM
Subject: Re: [LARTC] Incomprehensive problem with tc filter & mangle...
> > # The rules that's didn't work, and I don't now why.
> > $TC filter add dev $EXT_IFACE parent 1: protocol ip prio 15 \
> > handle 10 fw classid 1:10
> > $TC filter add dev $EXT_IFACE parent 1: protocol ip prio 20 \
> > handle 15 fw classid 1:10
> I don't think it's an issue, but you can try it without a prio parameter?
>
> Stef
>
> --
>
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> #lartc @ irc.oftc.net
>
It's always the same thing...
Only the default setting seems to work.
From yesterday, I've tried with match ip src, and this also doesn't work.
($TC filter add dev $EXT_IFACE parent 1: protocol ip prio 15 u32 match ip
src $PREFERED_IP flowid 1:10)
I've tried to use mangle mark to do the same thing, and as every time always
the default setting seems to work.
I've tried another thing :
I used some rules from a script found here :
http://www.linux-france.org/prj/inetdoc/i/net/guides/Advanced-routing-Howto/
Advanced-routing-Howto.v0.9-15.html#ss15.8
So I used :
$TC filter add dev $EXT_IFACE parent 1:0 protocol ip prio 10 u32 \
match ip tos 0x10 0xff flowid 1:10
$TC filter add dev $EXT_IFACE parent 1:0 protocol ip prio 10 u32 \
match ip protocol 1 0xff flowid 1:10
$TC filter add dev $EXT_IFACE parent 1: protocol ip prio 10 u32 \
match ip protocol 6 0xff \
match u8 0x05 0x0f at 0 \
match u16 0x0000 0xffc0 at 2 \
match u8 0x10 0xff at 33 \
flowid 1:10
In addition to my own rules.... And these three rules work, not mine.
I really understand anything. What's wrong with my rules ?
Ronan.
_______________________________________________
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-01-08 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-07 21:44 [LARTC] Incomprehensive problem with tc filter & mangle Ronan LAVIEC
2003-01-07 23:55 ` Victor Cassar
2003-01-08 10:50 ` Ronan LAVIEC
2003-01-08 18:32 ` Stef Coene
2003-01-08 18:57 ` Ronan LAVIEC [this message]
2003-01-08 19:07 ` Stef Coene
2003-01-13 6:47 ` hanhbnetfilter
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-104205237314554@msgid-missing \
--to=ronan.laviec@club-internet.fr \
--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.