(I have much more to learn about Artnet and calculating IP addresses that work with artnet in general.)
When I don’t use the automatically generated IP addresses for EtherDMX the XNet doesn’t see each other, so joining shows doesn’t seem to work. But when I do they are all so drastically different from each other. My router only allows editing of the last two decimal points. So using TouchOSC isn’t an option when the IP address is so drastically different.
Feature request: to have the option to limit the net mask to two decimal places on automatically generated EtherDMX addresses, e.g., 255.255.0.0
For example, I started with an automatically generated IP address in the EN4 and set my router to that IP address range. Telling Onyx to automatically choose IP address on both PC’s allows them to see each other on X-Net and the Artnet works. But then TouchOSC won’t respond because of being out of range with the default gateway. The second decimal place doesn’t match with the gateway of the router.
The auto-generated IP address from the EN4 is: 2.205.71.101
So I set the router to: 2.205.71.1
The automatically generated IP address in one Onyx PC is: 2.156.46.12
The generated IP address in the other computer is: 2.216.164.1
So these generated IP addresses bear no relation to each other, other than 2. And they don’t seem to query the IP address of the router before auto generating IP addresses. Why don’t they ping the router to find out the router IP and then generate IP addresses based upon that?
If one were to choose an IP address manually, oneself, then how would one do it? Because I’ve tried a few times and X-Net doesn’t seem to work when I do.