From: Bill Chappell <bill.chappell@critical.com>
To: netfilter@lists.netfilter.org
Subject: Re: Question about -m tos option
Date: Tue, 14 Oct 2003 22:38:01 -0400 [thread overview]
Message-ID: <3F8CB309.A4713C61@critical.com> (raw)
In-Reply-To: 000801c39183$9a3fed90$2d0410d4@urbannet6ku735
> "Pavel V. Chjen" wrote:
>
> 0x60 is out of valid range in dscp matching (:
> [root@root linux]# iptables -A FORWARD -m dscp --dscp 0x60
> iptables v1.2.9rc1: DSCP `96` out of range
You only have 6 bits of the 8 bits in the ToS to work with
for DSCP,
(http://www.cisco.com/warp/public/105/dscpvalues.html#dscpandassuredforwardingclasses)
and valid values are explicitly 0 through 63 (decimal)
(http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fqos_r/qrfcmd4.htm#1098678).
Your rule used 60(hex),
which is 96(decimal) as the error message reported.
I got these references, and more, to confirm what
I thought I knew about DSCP by asking Google
for DSCP and DSCP+size, if that helps for the future.
(www.google.com)
I hope this helps and that you really do not
need 96 different values for the DSCP.
Bill
--
William Chappell, Software Engineer, Critical Technologies, Inc.
Suite 400 Technology Center, 4th Floor 1001 Broad Street, Utica, NY
13501
315-793-0248 x148 < bill.chappell@critical.com > www.critical.com
next prev parent reply other threads:[~2003-10-15 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 12:14 Re:Question about -m tos option Pavel V. Chjen
2003-10-15 2:38 ` Bill Chappell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-21 12:08 Question " Rinse Kloek
2003-06-19 17:41 Pavel V. Yanchenko
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=3F8CB309.A4713C61@critical.com \
--to=bill.chappell@critical.com \
--cc=netfilter@lists.netfilter.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