September-30th-2020, 10:17 AM
Dear Armin,
The followings are results:
>1. You can ping cifX0 over the RTE ports if you connect a standard PC with correct IP settings like 192.100.50.170 to RTE port. And call ping 192.100.50.169
Destination host unreachable (1_Console_on_mypc.png)
>2. You can ping the modus slave over netX-ethernet-lan container using docker web UI and go into the container console and then call ping 192.100.50.250
Destination host unreachable (2_Console_on_mynetX_container.png)
I don't understand why a response is coming from 163.139.152.1???
>3. You can call now complete netPI web UI also now over cifX0 RTE ports. So the same as you do over eth0 port today. So connect a PC to the RTE ports and give it a correct IP address like 192.100.50.170 and then open your browser and call https://192.100.50.169 and now also the netPI web UI will pop up
Unable to access (3_Browser_from_mypc.png)
I have no idea what the problem is, so far.
Best regards,
The followings are results:
>1. You can ping cifX0 over the RTE ports if you connect a standard PC with correct IP settings like 192.100.50.170 to RTE port. And call ping 192.100.50.169
Destination host unreachable (1_Console_on_mypc.png)
>2. You can ping the modus slave over netX-ethernet-lan container using docker web UI and go into the container console and then call ping 192.100.50.250
Destination host unreachable (2_Console_on_mynetX_container.png)
I don't understand why a response is coming from 163.139.152.1???
>3. You can call now complete netPI web UI also now over cifX0 RTE ports. So the same as you do over eth0 port today. So connect a PC to the RTE ports and give it a correct IP address like 192.100.50.170 and then open your browser and call https://192.100.50.169 and now also the netPI web UI will pop up
Unable to access (3_Browser_from_mypc.png)
I have no idea what the problem is, so far.
Best regards,