Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Lopsch <lopsch@lopsch.com>
To: Netfilter-Mailinglist <netfilter@lists.netfilter.org>
Subject: Re: iptables and TOS 15
Date: Fri, 12 Nov 2004 17:54:11 +0100	[thread overview]
Message-ID: <4194EAB3.5040409@lopsch.com> (raw)
In-Reply-To: <1100272993.3377.9.camel@hubcap.ljm.dom>

Jason Opperisano schrieb:
> On Fri, 2004-11-12 at 03:40, tepesu@australia.edu wrote:
> 
>>    hi,
>>
>> my ISP mark packets from some internet traffic with TOS 15 and i musst
>>filter this traffic. how and where i must odified iptables to can do some
>>filtering using this marks, TOS 15.
> 
> 
> as far as i'm aware, "15" is not a valid TOS value.  as a result of the
> way the TOS bits are set in the packet header, there are only 5 possible
> TOS settings (from RFC 1349):
> 
>   1000   --   minimize delay
>   0100   --   maximize throughput
>   0010   --   maximize reliability
>   0001   --   minimize monetary cost
>   0000   --   normal service
> 

Concerning to 
http://www.lartc.org/howto/lartc.qdisc.classless.html#AEN659 the value 
15 is a combination of all possible TOS values. What would be logical 
because with a 4bit field you are able to get the max decimal value of 
15. In my opinion marking with 15 or not marking have the same effect. 
Also using the TOS values only makes sense when using for example the 
pfifo_fast queueing discipline to schedule pakets.



  reply	other threads:[~2004-11-12 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12  8:40 iptables and TOS 15 tepesu
2004-11-12  9:25 ` a.ledvinka
2004-11-12 15:23 ` Jason Opperisano
2004-11-12 16:54   ` Lopsch [this message]
2004-11-12 16:50     ` Jason Opperisano
  -- strict thread matches above, loose matches on Subject: below --
2004-11-12  9:43 tepesu

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=4194EAB3.5040409@lopsch.com \
    --to=lopsch@lopsch.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