Change multicast address and port
Posted: Mon Mar 22, 2010 4:00 am
Hello,
could it be possible that Tracking Tools or Arena could have an additional option to set the multicast address and port for streaming?
I have made a few changes to the PacketClient example in NatNet 2.1 SDK to having it work under Linux. The command part works fine, but the data streaming gets nothing. I did some research and found that the default address that TT or Arena are using, 224.0.0.1 has a special meaning among the multicast address space. In fact, it seems that belongs to a reserved range: http://www.tcpipguide.com/free/t_IPMult ... m#Table_48 , so maybe this is the reason why the packets aren't received.
It would also be very helpful to being able to change the port because ports under 1024 are usually system reserved, so a program listening to port 1001 must have administrative privileges in order to be allowed to bind that port.
Thank you,
could it be possible that Tracking Tools or Arena could have an additional option to set the multicast address and port for streaming?
I have made a few changes to the PacketClient example in NatNet 2.1 SDK to having it work under Linux. The command part works fine, but the data streaming gets nothing. I did some research and found that the default address that TT or Arena are using, 224.0.0.1 has a special meaning among the multicast address space. In fact, it seems that belongs to a reserved range: http://www.tcpipguide.com/free/t_IPMult ... m#Table_48 , so maybe this is the reason why the packets aren't received.
It would also be very helpful to being able to change the port because ports under 1024 are usually system reserved, so a program listening to port 1001 must have administrative privileges in order to be allowed to bind that port.
Thank you,