[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111216.132012.625460188266025260.davem@davemloft.net>
Date: Fri, 16 Dec 2011 13:20:12 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: romieu@...zoreil.com
Cc: bernat@...fy.cx, zenczykowski@...il.com, netdev@...r.kernel.org,
yoshfuji@...ux-ipv6.org
Subject: Re: nonlocal_bind and IPv6
From: Francois Romieu <romieu@...zoreil.com>
Date: Fri, 16 Dec 2011 12:10:27 +0100
> Vincent Bernat <bernat@...fy.cx> :
>> On Fri, 16 Dec 2011 02:06:00 -0500 (EST), David Miller wrote:
>> >>04:58, Maciej Żenczykowski <zenczykowski@...il.com> disait :
> [...]
>> >>>why not simply use the IP_TRANSPARENT or IP_FREEBIND socket
>> >>>options?
>> >>
>> >>Because this requires modifying each affected software. This
>> >>can be difficult if you don't have the source code available.
>> >
>> >But it means that it would work on every single kernel verion out
>> >there.
> [...]
>> Moreover, I am just adding the IPv6 version of this setting. The
>> IPv4 version already exists.
>
> For IPv6 this is adding a system-scope function which will have to be
> maintained and available for ages. It will compete with the existing,
> per-application answer. The "fix you application / design" argument
> is thus stronger than with IPv4.
Another excellent point.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists