From: Pete Heist <pete@heistp.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: flent-users <flent-users@flent.org>
Subject: Re: [Flent-users] IRTT UDP-lite support
Date: Tue, 12 Mar 2019 14:17:17 +0100 [thread overview]
Message-ID: <D5AC15C8-5C8F-4709-AA97-33AE1E5A0FE4@heistp.net> (raw)
In-Reply-To: <2639B69C-8561-4014-A567-A5F22F52A7B3@heistp.net>
[-- Attachment #1.1: Type: text/plain, Size: 1047 bytes --]
> On Mar 9, 2019, at 10:34 AM, Pete Heist <pete@heistp.net> wrote:
>>
>> It is not because of it's additional support for a partial checksum
>> that I favor trying to make UDP-lite more deployable.
>
> Aha, ok! In that case I’ll put it on the list for first just supporting UDP-lite with a regular full checksum. It should be easy (said the sailor, unawares of the kraken). The partial checksum for measuring corruption can be down the road.
Unfortunately this isn’t a one-liner in Go, as the value 0 is hardcoded for the protocol argument passed in to the socket function.
It should be possible with a raw socket and making the UDP packet myself (not hard), but that requires either root privileges or cap_net_raw and looking at all proto 136 packets, which I don’t love. I’m still asking around and either way I’ll get it done at some point or another. Maybe the Go team would take a patch to add “udplite” as a new “network” argument, but I doubt it, as OS support is limited pretty much to Linux and FreeBSD.
[-- Attachment #1.2: Type: text/html, Size: 3096 bytes --]
[-- Attachment #2: Type: text/plain, Size: 151 bytes --]
_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org
prev parent reply other threads:[~2019-03-12 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 19:25 Pete Heist
2019-03-08 20:31 ` Dave Taht
2019-03-08 21:10 ` Dave Taht
2019-03-09 9:34 ` Pete Heist
2019-03-12 13:17 ` Pete Heist [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
List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D5AC15C8-5C8F-4709-AA97-33AE1E5A0FE4@heistp.net \
--to=pete@heistp.net \
--cc=dave.taht@gmail.com \
--cc=flent-users@flent.org \
--subject='Re: [Flent-users] IRTT UDP-lite support' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox