Clearing up some confusion (re NSM)

[mxmilkiib]

Hello. I'm trying to clear up some apparently long running potential confusion regarding liblo in relation to NSM (new-sm being a fork of older non-sm, a fork that is orientated to the needs of LA community NSM users and developers).

With the now much wider adoption of the NSM system, some of the previous understandings and assumptions are in apparent need of revising. Note of prior issues can be found on https://github.com/linuxaudio/new-session-manager/issues/54

I'm wondering which of these statements/assumptions (from the above thread) are still accurate, which were historically correct but not true now, which might be wrong, and which would be worth opening a specific issue about the possibility of resolving;

• "libo-server started with ipv6 will only listen on ipv6"
• "liblo OSC server cannot be instructed to bind to a specific hostname or network interface. It binds to all available interfaces."
• "you cannot get nsmd to only listen on/to localhost, only 0.0.0.0 etc."
• How might liblo be with TCP in nowadays?

Thanks for any feedback on this!

[radarsat1]

Hi,

"libo-server started with ipv6 will only listen on ipv6"

I don't think that's the case, but I haven't tested it.  I consider ipv6 support broken and it is disabled by default. Please see issue #57, which to date no one has answered.

 "liblo OSC server cannot be instructed to bind to a specific hostname or network interface. It binds to all available interfaces."

I think this is correct, except in the case of joining a multicast group. Suggestions/pull requests welcome.

"you cannot get nsmd to only listen on/to localhost, only 0.0.0.0 etc."

I'm afraid this is the first I've heard of NSM so I can't answer this question. If it uses liblo then I guess the previous question answers it.

 How might liblo be with TCP in nowadays?

I think it works fine as far as I know, but I hear very little about its usage so I can't give a confident answer.

 Thanks for any feedback on this!

cheers, Steve

[malloch]

On this topic, PR #135 addresses the remaining issues with TCP I encountered while using liblo for session management on the libmapper project.

-joe

[radarsat1]

Closing due to inactivity.