All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jim Fleming" <JimFleming@ameritech.net>
To: Antony Stone <Antony@Soft-Solutions.co.uk>,
	netfilter@lists.netfilter.org
Subject: Re: Setting and Routing on the TOS Source (SRC) and Destination (DST) Bits
Date: Sun, 22 Sep 2002 09:39:35 -0500	[thread overview]
Message-ID: <0c8101c26245$dfe72c50$c6b22543@repligate> (raw)
In-Reply-To: 20020922134852.PSNX6699.mta01-svc.ntlworld.com@there

----- Original Message ----- 
From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
> On Sunday 22 September 2002 2:35 pm, Jim Fleming wrote:
> 
> > Have you ever calculated how much bandwidth is wasted each year
> > with 4 of the 160 bits in every packet as useless ?
> 
> Actually, it's 4 of every 160 bits in the *header* - there's up to another 
> 1500 *bytes* (on ethernet) of body in the packet as well, so the wasted 
> bandwidth varies from 4/160 = 2.5% for empty packets, to 4/12160 = 0.03% for 
> full ones.
> 

Are there also 4 bits in each 320 bit header, when the value is 0110 ?

Is that an improvement ?....with 4/320 = 1.25%

Can routing be done on the values 0100 and 0110 ?

Are those 4 bits included in your count of useless routing bits ?

From: "Antony Stone" <Antony@Soft-Solutions.co.uk>
"I still say that 83 of them make sense, 28 are doubtful, and 49 are useless.
=============================

Moving to the next 4 bits....do you agree they are almost always 0101 (5) ?

IF one assumed they did not care about "options", could those bits be assumed ?...and dropped ?
Is that another 2.5% savings ?

If the 0100 and the 0101 are tossed, is that a 5% savings ?

...or, could the 0100.0101 be considered an 8 bit "version" number ?
do people want or need 256 versions ?
==========

Going back to the mention of the *header*....could the 4-bits really be a header ?
...are all 16 values valid ?....what is 0000 and 0001 ?
Does the 4-bit "Version Header" describe the "Next Header" which follows ?

0000 = 0 bit header
0001 = ??
...
0100 = 160 bit header
...
0110 = 320 bit header

===========

Does NetFilter route based on the first 4 bits ?
http://www.netfilter.org/




  parent reply	other threads:[~2002-09-22 14:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-20 12:23 Iptables bandwidth limit Rob Sterenborg
2002-09-20 12:35 ` Andrei Ivanov
2002-09-20 19:46   ` Oskar Andreasson
2002-09-21 13:25     ` Setting and Routing on the TOS Source (SRC) and Destination (DST) Bits Jim Fleming
2002-09-21 13:38       ` Andrei Ivanov
2002-09-21 13:52       ` Antony Stone
2002-09-21 21:53         ` Jim Fleming
2002-09-21 21:59           ` Antony Stone
2002-09-21 23:15             ` Jim Fleming
2002-09-22  8:21               ` Antony Stone
2002-09-22 10:25                 ` Sascha Reissner
2002-09-22 10:35                   ` Antony Stone
2002-09-22 13:54                   ` Jim Fleming
2002-09-22 13:35                 ` Jim Fleming
2002-09-22 13:48                   ` Antony Stone
2002-09-22 14:15                     ` Sascha Reissner
2002-09-22 14:20                       ` Antony Stone
2002-09-22 15:18                         ` Jim Fleming
2002-09-22 14:39                     ` Jim Fleming [this message]
2002-09-21 21:56         ` Jim Fleming
2002-09-21 22:01           ` Antony Stone
2002-09-21 22:57         ` Jim Fleming

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='0c8101c26245$dfe72c50$c6b22543@repligate' \
    --to=jimfleming@ameritech.net \
    --cc=Antony@Soft-Solutions.co.uk \
    --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 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.