From: nicholas black <dank@trellisinc.com>
To: linux-kernel@vger.kernel.org
Cc: Vinolin <vinolin@nodeinfotech.com>
Subject: Re: ip_options.c
Date: Thu, 21 Mar 2002 11:31:51 -0500 (EST) [thread overview]
Message-ID: <20020321163151.53841A3C21@fancypants.trellisinc.com> (raw)
In-Reply-To: <02032116405005.00890@Vinolin>
In article <02032116405005.00890@Vinolin> you wrote:
> Can i get the summary of what exactly ip_options.c is doing ?
> Through any web page or documents ...
it deals with ip options (see rfc's 791 and 1122).
ip_options_build is called while putting together the headers, but
prior to checksumming from numerous places in net/ipv4/ip_output.c.
ip_options_fragment does special handling for options in fragmented
datagrams (again, ip_output.c).
ip_options_echo is used to setup the options used in a reply; see
net/ipv4/icmp.c et al.
ip_options_compile and ip_options_get both seem to be used to extract raw
options from an skb.
ip_options_forward handles setting up source-routed packets, while
ip_options_rcv_srr handles their receipt.
i am by not any mean at all an authority on these matters, so take this with
a grain of salt :).
--
nicholas black (dank@trellisinc.com)
"c has types for a reason. c++ improved the type system for a reason. perl
and php programs have run-time failures for a reason." - lkml
prev parent reply other threads:[~2002-03-21 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 11:10 ip_options.c Vinolin
2002-03-21 16:31 ` nicholas black [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=20020321163151.53841A3C21@fancypants.trellisinc.com \
--to=dank@trellisinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinolin@nodeinfotech.com \
/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
all inboxes | Powered by JetHome®