From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port
Date: Thu, 03 Oct 2002 07:10:58 -0700 (PDT) [thread overview]
Message-ID: <20021003.071058.89246593.davem@redhat.com> (raw)
In-Reply-To: <20021003.231534.83777766.yoshfuji@linux-ipv6.org>
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
Date: Thu, 03 Oct 2002 23:15:34 +0900 (JST)
In article <200210031301.RAA29267@sex.inr.ac.ru> (at Thu, 3 Oct 2002 17:01:11 +0400 (MSD)), kuznet@ms2.inr.ac.ru says:
> What's about the problem, it cannot be a problem for TCP, connection
> uniqueness is verified by tcp_*_check_established() not depending
> on value of SO_REUSEADDR. What's about UDP, the problem really might
> be a real problem, let's defer the issue, it looks absoluteky unrelated.
Hmm, but I'm afraid that different behavior between TCP and UDP would
confuse users.
He is saying we should do the TCP part first to make the patch simpler
and easier to verify.
Then we can investigate the UDP side seperately.
> BTW the question: why is bindv6only in device configuration directory?
Because I thought that net.ipv6.conf is the place for all
configuration...
It is for interface level configuration.
Do you propose to move it to parent directory (net.ipv6.bindv6only),
and put other general settings there?
Yes.
next prev parent reply other threads:[~2002-10-03 14:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 3:13 [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port Number (IPV6_V6ONLY Support) YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 3:53 ` acme
2002-10-03 3:55 ` acme
2002-10-03 7:00 ` Pekka Savola
2002-10-03 8:29 ` David S. Miller
2002-10-03 8:55 ` Brad Hards
2002-10-03 8:58 ` David S. Miller
2002-10-03 13:06 ` [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same kuznet
2002-10-03 13:02 ` David S. Miller
2002-10-03 13:18 ` Pekka Savola
2002-10-03 13:13 ` David S. Miller
2002-10-03 13:01 ` [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port kuznet
2002-10-03 14:15 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 14:10 ` David S. Miller [this message]
2002-10-03 15:06 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 15:04 ` David S. Miller
2002-10-03 15:19 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 15:52 ` kuznet
2002-10-23 7:24 ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port) YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 7:23 ` David S. Miller
2002-10-23 7:58 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 8:06 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 8:02 ` David S. Miller
2002-10-23 7:36 ` Pekka Savola
2002-10-23 10:01 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 10:15 ` Pekka Savola
2002-10-23 10:12 ` David S. Miller
2002-10-24 16:24 ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both kuznet
2002-10-25 7:46 ` Pekka Savola
2002-10-23 15:53 ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port) Kyle C Quest
2002-10-23 16:06 ` Pekka Savola
2002-10-23 16:09 ` Kyle C Quest
2002-10-24 10:24 ` David S. Miller
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=20021003.071058.89246593.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=usagi@linux-ipv6.org \
--cc=yoshfuji@linux-ipv6.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).