Couple of things here…
I assume you are using Mavericks 10.9.x
The network libraries Catalyst used to use were removed from Mavericks by apple - so Bleasdale had to use a new library.
Basically, Catalyst now only looks at the IP address on network card 'en0' rather than the network interface at the top of the 'service order' in network preferences (as before). So if the IP address you have entered is not on en0, it wont appear in the top of the catalyst control window. (or you may see 0.0.0.0 if en0 is not active)
(Check the network section of system preferences or network utility to see which one is defined as 'en0' - it differs between models MacMini / MacPro / MacBook…)
However, this doesn't matter too much, depending on what you are trying to do.
For example:
If using artnet input to control catalyst from a console, simply set one of the Network ports to the artnet IP and subnet (2.0.0.x, 255.0.0.0)
Catalyst will still receive artnet, despite saying non-artnet IP address.
Also
You should setup a new location specifically for catalyst and only include he ports in use
(I notice from your picture you have almost every network port included in 'auomatic')
Name the location catalyst, and only include the ethernet port in use (preferably en0)
The Mac network setup works as a sort of bridge and many different IP addresses can co-exist.
It also seems possible to connect to the mac on unexpected addresses (ie the address for the other network port)
(worth reading about class A networks)
Let me know if you are trying to do something specific
regards
Simon
Reply With Quote