From: André Fonseca <andre.amorimfonseca_at_gmail.com>
Date: Fri, 20 Jan 2012 15:20:03 +0100

Hi again,

I've produced a patch for the gms module, extending the latter one that
Joseph sent.

This patch do not solve the problem of sending messages using a IPv6
network interface, however it improves the selection of these interfaces
based on the java.net.preferIPv6Addresses property.

In the last revision of the NetworkUtility class, even setting
the java.net.preferIPv6Addresses property to false, it is still possible to
use a IPv6 address if the first active interface is IPv6 only. I believe
that the correct behavior in this situation should be the selection of a
IPv6 address only if the java.net.preferIPv6Addresses is set to true. That
means: if a machine has two active NICs, one of them supports IPv6 only and
the second one supports both IPv4 and IPv6, if java.net.preferIPv6Addresses
is false, the selected NIC will be the one that supports IPv4 instead of
the first one active.

I don't know if is a valid improvement but anyway,the patch is attached.

On Thu, Jan 19, 2012 at 5:55 PM, André Fonseca <
andre.amorimfonseca_at_gmail.com> wrote:

> Hi,
>
> Using the version "gms-transport-modules" I've been able to configure the BIND_INTERFACE_ADDRESS
> by the name of the network interface even in a Linux environment. It kind
> solves my problem, however, still in this version I could not send/receive
> any kind of notifications using a iPv6 only interface.
>
> Anyway, thanks for the help. Also, I'll try to crawl into the code in
> order to analyze this possible problem, at least to know why, among other
> interfaces that could support IPv4, a IPv6 only interface is being selected.
>
>
>