Re: [liblo] liblo and IPv6

Luis,

Okay that explains it a little better.  So if I understand correctly,
taking the case of a DSSI GUI for example, the problem is that the
DSSI starts up a server which gets bound to an IPv6 local socket, and
the host tries sending to "localhost" but this resolves to IPv4 so
they don't find each other.

This sounds to me like the DSSI needs to be able to tell the host what
type of socket it opened, and then the host could send to localhost or
localhost6 accordingly.  LibLo does allow setting the address to
anything you want, so it's a matter of the DSSI host doing the right
thing.  One change I can imagine is that I guess there's no way
currently to ask LibLo what IP version it is serving, or in fact to
ask liblo to use one or the other when starting a server.  Perhaps
there needs to be a way.

One simple solution for local connections that I can imagine would be
to use UNIX sockets instead of IP sockets...

Steve

On Thu, Apr 7, 2011 at 6:27 PM, Luis Garrido
<lui...@us...> wrote:
> Hi, Stephen.
>
> Upon further investigation, the problem appears when NetworkManager
> modifies /etc/hosts so the machine name is both associated to an IP
> and an IPv6 address, like in the following example:
>
> $ cat /etc/hosts
> 192.168.0.128   advent
> 127.0.0.1       localhost.localdomain   localhost       localhost4
> ::1     advent  localhost6.localdomain6 localhost6
>
> In this situation both DSSI host and GUI can't communicate: the host
> launches the GUI process, but the startup protocol never progresses to
> the point the GUI is displayed on the screen. I don't know enough of
> the internals of name resolution as to hazard a guess about why a
> configuration like that is a problem.
>
> Apparently this causes problems with other software too, notably kerberos.
>
> As of 01/2011, NM developers seem to have given up on updating
> /etc/hosts automatically.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=648725
>
> Once the machine name is not associated to the IPv6 loopback address
> anymore the problem disappears.
>
> $ cat /etc/hosts
> 192.168.0.128   advent
> 127.0.0.1       localhost.localdomain   localhost       localhost4
> ::1     localhost6.localdomain6 localhost6
>
> I am not sure if there is something that can be done on liblo's side
> to make it more resilient to situations like this or not.
>
> Regards,
>
> Luis
>
> ------------------------------------------------------------------------------
> Xperia(TM) PLAY
> It's a major breakthrough. An authentic gaming
> smartphone on the nation's most reliable network.
> And it wants your games.
> http://p.sf.net/sfu/verizon-sfdev
> _______________________________________________
> liblo-devel mailing list
> lib...@li...
> https://lists.sourceforge.net/lists/listinfo/liblo-devel
>