All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nedko Nedev" <nedco@unacs.bg>
To: "Jim Fleming" <JimFleming@ameritech.net>
Cc: <netfilter-devel@lists.netfilter.org>
Subject: Re: "...packets with TOS 0x0  also packets with TOS 0x10..."
Date: Wed, 5 Mar 2003 23:31:05 +0200	[thread overview]
Message-ID: <000401c2e35e$89d65030$8268493e@coldunacs> (raw)
In-Reply-To: 069401c2e34e$64aae1f0$8500a8c0@repligate




Hi,
i read several times your response but still can't understand why
iptables rule
1    36142    16M ACCEPT     all  --  *      *       0.0.0.0/0 0.0.0.0/0
TOS match 0x00
2     168K    54M ACCEPT     all  --  *      *       0.0.0.0/0 0.0.0.0/0
TOS match 0x10
not ACCEPT some packets with TOS 0x00 ( Normal-Service  )  also packets with
TOS 0x10 (Minimize-Delay)
and they go respectively to next rule
3       27       1782 LOG            all  --  *      *       0.0.0.0/0
0.0.0.0/0         LOG  flags 0 level 4
and loged
Mar  5 04:32:10 proliant kernel: IN=eth0 OUT=eth1 SRC=62.176.73.4
DST=62.176.105.30 LEN=76 TOS=0x00 PREC=0xC0


----- Original Message -----
From: "Jim Fleming" <JimFleming@ameritech.net>
To: "Nedko Nedev" <nedco@unacs.bg>; <netfilter-devel@lists.netfilter.org>
Sent: Wednesday, March 05, 2003 9:35 PM
Subject: "...packets with TOS 0x0 also packets with TOS 0x10..."


>
>
>
> ----- Original Message -----
> From: "Nedko Nedev" <nedco@unacs.bg>
> >
> > in log we can see packets with TOS 0x0  also packets with TOS 0x10
> >
>
> The TOS field is divided into two 4-bit fields. 0x0* and 0x*0 are legacy
values.
> The other values help to expand the address spaces by adding 15 more flows
or layers.
> The Identification Field is also used to add 14 more bits of addressing,
in two 7-bit fields.
> The 7 plus 4 is 11 and when added to the 32-bits of addressing provide a
43 bit address space.
> The extra AM/FM bit is common to all of the address spaces.
>
> http://IPv8.no-ip.com
> http://www.go-mono.com/
> http://www.knoppix.com
> http://www.netfilter.org
> http://www.digium.com
> http://www.asterisk.org
> http://www.openss7.org
> http://www.zapatatelephony.org
> http://www.new.net
> http://IPv8.dyn.ee
>
> Jim Fleming
> Inter.C@T.Inter.NAT Consultant
> http://www.Unir.NET
> http://www.Unir.com
> http://www.Uni%ae.com
> http://www.UniR.com
>
>
>

      reply	other threads:[~2003-03-05 21:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 17:56 iptables dropping wrong packets Nedko Nedev
2003-03-05 19:35 ` "...packets with TOS 0x0 also packets with TOS 0x10..." Jim Fleming
2003-03-05 21:31   ` Nedko Nedev [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='000401c2e35e$89d65030$8268493e@coldunacs' \
    --to=nedco@unacs.bg \
    --cc=JimFleming@ameritech.net \
    --cc=netfilter-devel@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 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.