From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] fw_mark [was HTB: Filtering flat out not working :(]
Date: Fri, 01 Mar 2002 08:03:30 +0000 [thread overview]
Message-ID: <marc-lartc-101496987919316@msgid-missing> (raw)
By the way, you can attach fw_mark classifier WITHOUT specifying
any marks and then it will try to directly map mark to class numbers.
You can then specify class numbers directly in ip{chains,tables} ;)
devik
On Fri, 1 Mar 2002, Stef Coene wrote:
> On Thursday 28 February 2002 20:45, you wrote:
> > Absolutely, but you'll notice in my follow up post that nowhere does it
> > tell you how to use 'tc' to throw the MARKed packets into a certain flow.
> > The HOWTO tells you how to route marked packets, not how to shape them...
> > ideas? do you happen to know the TC command sytax? All i need is one
> > example....
> I use the fw filter all the time. I have a lot of examples on docum.org.
> The idea is simple. You mark a packet and you use that mark to catch the
> packets with the fw filter.
> The number of the mark is not important and has nothing to do with the class.
> The handle keyword is to say wich mark the filter has to use. So handle 10
> will catch all packets with mark 10.
>
>
> Stef
>
> --
>
> stef.coene@docum.org
> More QOS info : http://www.docum.org/
> Title : "Using Linux as bandwidth manager"
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-03-01 8:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 8:03 Martin Devera [this message]
2002-03-01 8:09 ` [LARTC] fw_mark [was HTB: Filtering flat out not working :(] Stef Coene
2002-03-01 19:30 ` Michael T. Babcock
2002-03-01 22:03 ` Martin Devera
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-101496987919316@msgid-missing \
--to=devik@cdi.cz \
--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.