From: David Astua <dastuam@gmail.com>
To: Randi <nightdecoder@gmail.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: UDP data
Date: Thu, 10 Feb 2011 12:43:38 -0600 [thread overview]
Message-ID: <AANLkTik7CDfK1XbNccb9=Gb_18d1bLP+ZaZiPNLWP6hN@mail.gmail.com> (raw)
In-Reply-To: <19796.1824.862218.276072@cerise.gclements.plus.com>
On Thu, Feb 10, 2011 at 9:41 AM, Glynn Clements
<glynn@gclements.plus.com> wrote:
>
> Randi wrote:
>
>> > Yes the checksum is for the header and data.
>> > Keep in mind that the checksum value is optional in ipv4, but required in ipv6.
>>
>> Chris, optional means it can be enable or not, how to enable it and get
>> the headehttps://mail.google.com/mail/?shva=1#inbox/12e0da8d716c914er to verify the checksum.
>
> Checksums are enabled by default. You can disable checksums when
> sending using the SO_NO_CHECK option. On receipt, the kernel will
> verify the checksum if it's present, and discard the packet if there
> is an error.
>
> --
> Glynn Clements <glynn@gclements.plus.com>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Also keep in mind that the check is for individual frames, even
checking that there's no certainty that all frames will arrive.
-- David A.
--
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-10 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimck7ar6JPzSnNZo_baTz1usHLeUFxkL8GaqriV@mail.gmail.com>
2011-02-03 14:50 ` dynamic shared library ratheesh k
2011-02-03 14:59 ` Michal Nazarewicz
2011-02-10 3:41 ` UDP data Randi
2011-02-10 4:14 ` Chris Donovan
2011-02-10 5:14 ` Randi
2011-02-10 15:41 ` Glynn Clements
2011-02-10 18:43 ` David Astua [this message]
2011-02-10 20:49 ` Chris Donovan
2011-03-19 21:57 ` dynamic shared library Hendrik Visage
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='AANLkTik7CDfK1XbNccb9=Gb_18d1bLP+ZaZiPNLWP6hN@mail.gmail.com' \
--to=dastuam@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=nightdecoder@gmail.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;
as well as URLs for NNTP newsgroup(s).