From: Thorsten Glaser <t.glaser@tarent.de>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: 966459@bugs.debian.org, netdev <netdev@vger.kernel.org>
Subject: Re: Bug#966459: linux: traffic class socket options (both IPv4/IPv6) inconsistent with docs/standards
Date: Mon, 3 Aug 2020 18:58:47 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.23.453.2008031733520.11571@tglase-nb.lan.tarent.de> (raw)
In-Reply-To: <db7d2f4dde6db2af82c880756d76af1b7c1e41e8.camel@decadent.org.uk>
Hi Ben,
> For what it's worth, FreeBSD/Darwin and Windows also put 4 bytes of
> data in a IPV6_TCLASS cmsg. So whether or not it's "right", it's
> consistent between three independent implementations.
oh, thank you, I don’t have any of these systems around at the
moment, so checking them was tricky for me.
So basically I should read an int in host endianness then (or
keep the code I currently have that compares byte 0 and 3, using
the one that’s not 0, if any). Great, thank you!
After some minor porting work, it turns out that the current code
does work on MidnightBSD (equivalent to FreeBSD 10.4) for IPv6.
I guess I’ll keep ints then.
bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
prev parent reply other threads:[~2020-08-03 16:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <159596111771.2639.6929056987566441726.reportbug@tglase-nb.lan.tarent.de>
2020-08-02 17:49 ` Bug#966459: linux: traffic class socket options (both IPv4/IPv6) inconsistent with docs/standards Ben Hutchings
2020-08-02 19:29 ` Thorsten Glaser
2020-08-02 20:29 ` Ben Hutchings
2020-08-02 20:44 ` Thorsten Glaser
2020-08-03 3:32 ` Ben Hutchings
2020-08-03 16:58 ` Thorsten Glaser [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=alpine.DEB.2.23.453.2008031733520.11571@tglase-nb.lan.tarent.de \
--to=t.glaser@tarent.de \
--cc=966459@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=netdev@vger.kernel.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).