From: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@wide.ad.jp>
To: linux_4ever@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.18+IPv6+IPV6_ADDRFORM
Date: Wed, 02 Oct 2002 18:20:06 +0900 (JST) [thread overview]
Message-ID: <20021002.182006.1021932192.yoshfuji@wide.ad.jp> (raw)
In-Reply-To: <20021001163221.73061.qmail@web9607.mail.yahoo.com>
In article <20021001163221.73061.qmail@web9607.mail.yahoo.com> (at Tue, 1 Oct 2002 09:32:21 -0700 (PDT)), Steve G <linux_4ever@yahoo.com> says:
> According to it, calling getsockopt() with level
> IPPROTO_IPV6 and option IPV6_ADDRFORM should get the
> option value. However, I get a socket error. I changed
> the level to IPPROTO_IP and the call goes through, but
> Richard Stevens' book states that AF_INET or AF_INET6
> should be returned rather than 0 or 1.
>
> 1) should the level really be IPPROTO_IPV6?
> 2) do other platforms use IPPROTO_IP to retrieve this
> option or said another way, is the behavior observed
> in Linux portable?
> 3) should the returned value be 0 & 1 or AF_INET &
> AF_INET6?
> 4) Is this a deprecated option and likely to be
> dropped?
IPV6_ADDRFORM is deprecated.
I believe that it should be removed.
> Also, the Sus v3, states there is a socket option:
> level IPPROTO_IPV6, option IPV6_V6ONLY...will this be
> supported in 2.4 or 2.6? A grep -r doesn't get any
> hits from /usr/include.
We, USAGI Project, have implementation for it,
and we are about to contribute it here.
--
Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
next prev parent reply other threads:[~2002-10-02 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 16:32 2.4.18+IPv6+IPV6_ADDRFORM Steve G
2002-10-02 9:20 ` YOSHIFUJI Hideaki / 吉藤英明 [this message]
2002-10-02 12:37 ` 2.4.18+IPv6+IPV6_ADDRFORM Steve G
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=20021002.182006.1021932192.yoshfuji@wide.ad.jp \
--to=yoshfuji@wide.ad.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_4ever@yahoo.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).