netdev
[Top] [All Lists]

Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port

To: yoshfuji@xxxxxxxxxxxxxx
Subject: Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Thu, 03 Oct 2002 07:10:58 -0700 (PDT)
Cc: kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, usagi@xxxxxxxxxxxxxx
In-reply-to: <20021003.231534.83777766.yoshfuji@linux-ipv6.org>
References: <20021003.121350.119660876.yoshfuji@linux-ipv6.org> <200210031301.RAA29267@sex.inr.ac.ru> <20021003.231534.83777766.yoshfuji@linux-ipv6.org>
Sender: netdev-bounce@xxxxxxxxxxx
   From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
   Date: Thu, 03 Oct 2002 23:15:34 +0900 (JST)

   In article <200210031301.RAA29267@xxxxxxxxxxxxx> (at Thu, 3 Oct 2002 
17:01:11 +0400 (MSD)), kuznet@xxxxxxxxxxxxx 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.


<Prev in Thread] Current Thread [Next in Thread>