[zeromq-dev] [PATCH] IPv6 changes to 4.0

Martin Sustrik sustrik at 250bpm.com
Tue Aug 23 08:45:09 CEST 2011

On 08/23/2011 03:17 AM, Steven McCoy wrote:

> 1)  Fail on NIC names resolving to multiple adapters.  I take this
> approach in OpenPGM.

That would be pretty annoying to the users IMO.

> 2)  Bind to everything.  This is what the patch does with IPv6 enabled
> and without CAP_NET_RAW.
> 3)  Bind to the adapter.  This requires CAP_NET_RAW.

Too big an administrative hurdle to implement a minor feature.

> 4)  Bind to the first IPv6 interface on the adapter.  The ordering tends
> to be completely bogus.

Not knowing what address you are going to bind to makes the whole thing 
completely useless.

> 5)  Re-implement the IPv6 RFC sorting rules and picked the preferred
> address.

RFC3484, right? That's probably the way to go. However, at the moment, 
why not simply choose the global address and let those that want to use 
local scopes specify a literal address.

It's not nice but it will at laest work in some way.

> I cannot think of a way to defer the sorting to getaddrinfo(), and it's
> beyond the design to create multiple sockets for each interface.

That's an alternative. Creating multiple listening sockets is not a big 
deal. I can do that.

However, let's first think about whether to proceed this way or the 
RFC3484 way.


More information about the zeromq-dev mailing list