netdev
[Top] [All Lists]

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

To: kuznet@xxxxxxxxxxxxx
Subject: Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Thu, 03 Oct 2002 23:15:34 +0900 (JST)
Cc: netdev@xxxxxxxxxxx, davem@xxxxxxxxxx, usagi@xxxxxxxxxxxxxx
In-reply-to: <200210031301.RAA29267@sex.inr.ac.ru>
Organization: USAGI Project
References: <20021003.121350.119660876.yoshfuji@linux-ipv6.org> <200210031301.RAA29267@sex.inr.ac.ru>
Sender: netdev-bounce@xxxxxxxxxxx
In article <200210031301.RAA29267@xxxxxxxxxxxxx> (at Thu, 3 Oct 2002 17:01:11 
+0400 (MSD)), kuznet@xxxxxxxxxxxxx says:

> While doing *_get_port() daddr/dport are _unknown_ and always zero,
> so it never works.
> 
> Please, remove these bits, the patch will become simpler.

Ok, I'll do that.


> 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.


> BTW the question: why is bindv6only in device configuration directory?

Because I thought that net.ipv6.conf is the place for all 
configuration...

Do you propose to move it to parent directory (net.ipv6.bindv6only),
and put other general settings there?

--yoshfuji


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