From: Michael Peddemors <michael@linuxmagic.com>
To: Jan Rekorajski <baggins@sith.mimuw.edu.pl>, Chris Wedgwood <cw@f00f.org>
Cc: "David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
waltje@uWalt.NL.Mugnet.ORG
Subject: Re: [UPDATE] zerocopy.. While working on ip.h stuff
Date: Mon, 26 Feb 2001 15:46:56 -0800 [thread overview]
Message-ID: <0102261546570H.02007@mistress> (raw)
In-Reply-To: <14998.2628.144784.585248@pizda.ninka.net> <20010225163836.A12173@metastasis.f00f.org> <20010225045420.B10281@sith.mimuw.edu.pl>
In-Reply-To: <20010225045420.B10281@sith.mimuw.edu.pl>
While doing some work on some ip options stuff, I have noticed a bunchof
unused entries in linux/include/linux/ip.h
A few things.. why is ip.h not part of the linux/include/net rather than
linux/include/linux hierachy?
Defined items that are not used anywhere in the source..
Can any of them be deleted now?
<see below>
Also, I was looking into some RFC 1812 stuff. (Thanks for nothing Dave :) and
was looking at 4.2.2.6 where it mentions that a router MUST implement the End
of Option List option.. Havent' figured out where that is implememented yet..
Also was trying to figure out some things.
I want to create a new ip_option for use in some DOS protection experiments.
I have a whole 40 bytes (+/-) to share... Now although I don't see anything
explicitly prohibiting the use of unused IP Header option space, I know that
it really was designed for use by the sending parties, and not routers in
between.. Has anyone seen any RFC that explicitly says I MUST NOT?
IPTOS_PREC_NETCONTROL
IPTOS_PREC_FLASHOVERRIDE
IPTOS_PREC_FLASH
IPTOS_PREC_IMMEDIATE
IPTOS_PREC_PRIORITY
IPTOS_PREC_ROUTINE
IPOPT_RESERVED1
IPOPT_RESERVED2
IPOPT_OPTVAL
IPOPT_OLEN
IPOPT_MINOFF
MAX_IPOPTLEN
IPOPT_EOL
> diff -urN linux/include/net/ip.h linux.fixed/include/net/ip.h
--------------------------------------------------------
Michael Peddemors - Senior Consultant
Unix Administration - WebSite Hosting
Network Services - Programming
Wizard Internet Services http://www.wizard.ca
Linux Support Specialist - http://www.linuxmagic.com
--------------------------------------------------------
(604) 589-0037 Beautiful British Columbia, Canada
--------------------------------------------------------
next prev parent reply other threads:[~2001-02-26 22:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 6:59 [UPDATE] zerocopy BETA 3 David S. Miller
2001-02-23 10:42 ` Jan Rekorajski
2001-02-25 3:38 ` Chris Wedgwood
2001-02-25 3:54 ` Jan Rekorajski
2001-02-26 23:25 ` [UPDATE] zerocopy.. While working on ip.h stuff David S. Miller
2001-02-26 23:47 ` Benjamin C.R. LaHaise
2001-02-27 0:05 ` David S. Miller
2001-02-27 0:11 ` Benjamin C.R. LaHaise
2001-02-27 3:41 ` Michael Peddemors
2001-02-27 3:24 ` Michael Peddemors
2001-02-26 23:46 ` Michael Peddemors [this message]
2001-02-26 23:23 ` Andi Kleen
2001-02-26 5:28 ` [UPDATE] zerocopy BETA 3 David S. Miller
[not found] <2137.983232656@ISI.EDU>
2001-02-27 1:53 ` [UPDATE] zerocopy.. While working on ip.h stuff Michael Peddemors
2001-02-27 2:31 ` Craig Milo Rogers
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=0102261546570H.02007@mistress \
--to=michael@linuxmagic.com \
--cc=baggins@sith.mimuw.edu.pl \
--cc=cw@f00f.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=waltje@uWalt.NL.Mugnet.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;
as well as URLs for NNTP newsgroup(s).