By factory default the netX controller chip is loaded with PROFINET slave software. And if noone (your application) configures it the LED is indeed red or is flashing red if you simple connect an Ethernet cable to any of the two RTE ports.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
You need to load the container
https://github.com/HilscherAutomation/ne...hernet-lan. This turns the netX controller chip into a standard TCP/IP controller. Then you can configure this interface named cifx0 like your primary port eth0.
Look to this post for example
https://forum.hilscher.com/Thread-RTE3-U...-interface
or this post
https://forum.hilscher.com/Thread-Modbus...ernet-Port
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
I just have seen that I posted a wrong link. This is the container you have to load.
https://hub.docker.com/r/hilschernetpi/n...ernet-lan/
For a very easy configuration I recommend to run it in "Host" mode always. This is the easiest way to get the netX running as TCP/IP network interface.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)