From: Werner Almesberger <wa@almesberger.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] can anyone help me to solve this problem?
Date: Sat, 26 Oct 2002 16:49:44 +0000 [thread overview]
Message-ID: <marc-lartc-103565105516150@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103555834517971@msgid-missing>
Folke Aeon wrote:
> it works currently, but wonder whether there will be
> any negative influence or not. would you please give
> some comment on this ?
It should work. You just have to be aware that your kernel
is doing some odd things ...
> another thing, i noticed that since the dsmark dequeue
> function does not support mpls protocol, so when a mpls
> packet arrives, it complains "unsupported protocol".
Only if you try to change the DS field.
> Although the tcindex value is still there, it just cannot
> use it . i think this is where the problem lies in.
No. tc_index does not have to equal the DSCP or DS field.
In dsmark, tc_index is an index to a table with DS field
changes. All you need to do is to reserve a tc_index value
for non-IP traffic, and only mark IP traffic with other
values than that.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-10-26 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 15:04 [LARTC] can anyone help me to solve this problem? Folke Aeon
2002-10-25 17:39 ` Werner Almesberger
2002-10-26 1:39 ` Folke Aeon
2002-10-26 2:27 ` Folke Aeon
2002-10-26 2:37 ` Werner Almesberger
2002-10-26 3:34 ` Werner Almesberger
2002-10-26 4:05 ` Folke Aeon
2002-10-26 13:57 ` Folke Aeon
2002-10-26 16:37 ` Werner Almesberger
2002-10-26 16:49 ` Werner Almesberger [this message]
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-103565105516150@msgid-missing \
--to=wa@almesberger.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox