Is it possible to specify the network adapter for multicast?

All other topics about Ventuz here.

Moderator: Support

Post Reply
User avatar
squiggle
Posts: 31
Joined: 18 Jan 2012, 17:54

Is it possible to specify the network adapter for multicast?

Post by squiggle » 04 Dec 2013, 17:14

Is it possible to specify which network adapter is used / being listened to by Ventuz? For the OSC-nodes I can set the Multicast IP and the Port but can't find any setting as to which network adapter is actually being used.

What I'm trying to achieve is using the Loopback Adapter for certain events.

Thanks,
sq.

User avatar
Karol
Posts: 560
Joined: 10 Jan 2012, 12:07

Re: Is it possible to specify the network adapter for multic

Post by Karol » 05 Dec 2013, 12:46

Hi!

This is not possible from within Ventuz. Afaik this has to be configured in the Network Setting of Windows.

Best Regards

Karol

User avatar
Götz_B
Posts: 180
Joined: 21 May 2013, 13:01

Re: Is it possible to specify the network adapter for multic

Post by Götz_B » 05 Dec 2013, 14:04

Hi,

i don't know exactly what you are trying, but if you want to send OSC Commands to the local Machine, you can leave the property MulticastIP of the OSC Input Node empty. This way it listens to the localhost. In the OSC Output Node, type the IP of your machine (like 192.168.0.1 ) OR a loopback address ( like 127.0.0.3 ).

But maybe you try to do sth different!? Why you want to send certain event to the loopback?

Regards,

Götz

User avatar
Daniel Willer
Posts: 309
Joined: 06 Jan 2012, 18:12

Re: Is it possible to specify the network adapter for multic

Post by Daniel Willer » 16 Dec 2013, 12:40

You need to use the route command in windows to route the messages to the desired interface.

Code: Select all

route  change 224.0.0.0 mask 240.0.0.0 <IP of network card here> metric 25

User avatar
squiggle
Posts: 31
Joined: 18 Jan 2012, 17:54

Re: Is it possible to specify the network adapter for multic

Post by squiggle » 16 Dec 2013, 22:13

Hi guys,

thanks for the answers, I learned a lot!

sq

P.S.: As to what we were initially trying to achieve... we had a 3rd party "black box" program giving out OSC-messages we could not edit so we tried to "filter" by listening on different adapters. In the end we decided it was easier (and more reliable) to write a new tool with the functionality of the "black box" ourselves.

Post Reply