From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] filters not doing anything?
Date: Mon, 21 Apr 2003 09:20:12 +0000 [thread overview]
Message-ID: <marc-lartc-105091692517093@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105078585814903@msgid-missing>
On Monday 21 April 2003 00:12, Frank v Waveren wrote:
> On Sun, Apr 20, 2003 at 11:59:44PM +0200, Stef Coene wrote:
> > On Sunday 20 April 2003 23:56, Frank v Waveren wrote:
> > > Stef Coene wrote:
> > > tc filter add dev eth1 protocol ip parent 1: prio 2 u32 match u8 0 0x0
> > > at 0 flowid 2:1
> >
> > What do you want to match??????
>
> That should match anything, right? I tried not having any filter in
> the commandline as the HOWTO suggested, but tc didn't like it and
> complained:
You can specify a default class if you add the htb qdisc. So all packets not
matched by a filter ends up in that default class.
And try this if you want to have a catch all rule :
tc filter add dev eth0 parent 1: protocol ip u32 match ip src 0/0 flowid 2:1
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-21 9:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-19 20:55 [LARTC] filters not doing anything? Frank v Waveren
2003-04-19 22:38 ` Frank v Waveren
2003-04-20 21:44 ` Stef Coene
2003-04-20 21:56 ` Frank v Waveren
2003-04-20 21:59 ` Stef Coene
2003-04-20 22:12 ` Frank v Waveren
2003-04-21 9:20 ` Stef Coene [this message]
2003-04-21 14:04 ` Frank v Waveren
2003-04-21 19:33 ` Stef Coene
2003-04-21 20:19 ` Frank v Waveren
2003-04-22 14:41 ` Stef Coene
2003-04-22 17:25 ` Frank v Waveren
2003-04-22 17:55 ` Stef Coene
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-105091692517093@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.