I see. I thought the mask is for the second IP. Now I understand why you prefer making the mask 255.255.255.255.
Indeed setup an OPC UA on PC1 can solve all the issues. Just that configuration and tag-making need to be done in the OPC UA.
If I am not mistaken the example you given to me in this reply is when an OPC UA is installed in PC1 right? The switch in my diagram will be at Layer 3.
Cause I was thinking to make it without the OPC UA, the setup in my mind currently is as below.
PLC:
IP 192.168.2.5
Mask 255.255.255.0
PC 1 NIC 1:
IP 192.168.2.1
Mask 255.255.255.0
PC 1 NIC 2:
10.148.1.2
Mask 255.255.255.0
Gateway: 10.148.1.254
route -p add 192.168.2.0 mask 255.255.255.0 192.168.2.1 (Cmd run in PC1)
Ignition Server
10.148.1.3
Mask 255.255.255.0
Gateway: 10.148.1.2
I would recommend looking into using Ignition Edge, as that seems to be a good fit for applications like this. You could put the OPC-UA server and accompanying module to make the connection to the PLC, and connect the main gateway to the OPC-UA server on the Edge. There are other methods, but this would be the simplest in my opinion.
There are a lot of good Ignition Onboard partners, I can recommend the Opto 22 groov EPIC, and I will admit that I am biased, as it is the only Onboard platform I have used.
A couple other reasons to use an onboard partner such as the EPIC, is that you remove the use of a windows PC on the plant floor. Using the groov EPIC you can still make use of port forwarding to directly communicate with the PLC, but you do not have to use any command prompts, everything is accomplished via a built in webserver, or with the use of a REST API interface.
Feel free to message me if you want more information, or if you would like to see these features in action.