mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steve G <linux_4ever@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.18+IPv6+IPV6_ADDRFORM
Date: Tue, 1 Oct 2002 09:32:21 -0700 (PDT)	[thread overview]
Message-ID: <20021001163221.73061.qmail@web9607.mail.yahoo.com> (raw)

Hello,

I am using a 2.4.18 kernel and ran across something I
thought was odd and need to understand better. I'm
writing a test suite to verify xinetd and I'm trying
to check a socket via getsockopt() to see if the
IPV6_ADDRFORM socket option has been set. I cannot
find IPV6_ADDRFORM in the Single Unix Standard or man
pages, so I am going by what is in Richard Steven's
book, Network Programming vol 1.

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?

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.

Thanks,
Steve Grubb

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

             reply	other threads:[~2002-10-01 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 16:32 Steve G [this message]
2002-10-02  9:20 ` 2.4.18+IPv6+IPV6_ADDRFORM YOSHIFUJI Hideaki / 吉藤英明
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=20021001163221.73061.qmail@web9607.mail.yahoo.com \
    --to=linux_4ever@yahoo.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®