Hello dear community,
we are trying to connect to a cRIO 9066 running Linux RT which is in a different subnet. We want to run an FPGA VI from a host in our subnet with interactive execution and also run a python script with nifpga.
This all works fine when all ports are open in the firewall, but we are not allowed to continue that way. The administrator asked us for a list of ports to open and this is where things get complicated.
As far as I understand, the connections we need are done via the RIO-server, which uses a random port which can be found through the NI Service Locator on port 3580. So we opened all ports on this list: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000001DdxbSAC&l=en-US and followed the instruction to create the nirio.ini on the cRIO to make the port for the RIO-server static. It contains the following lines:
[General]
RpcServerPort=<yourPortNumber>
After restarting we checked through the browser on http://yourPortNumber:3580/dumpinfo and confirmed that the RIO server is now on the intended port. Once we do this however, we cannot reach the RIO server at all. Not with all ports open and not even when taking the device back into our subnet. When running the VI, we only get the error message stating that the RIO server cannot be found. Same for the script or tools like RIO Device Setup. I can only find the Device in MAX and do basic stuff like rebooting. I can also get an SCP connection to place the nirio.ini on the device. These seem to work without the RIO server.
Afterwards I found this document which suggested that we also have to specify access rights: https://www.ni.com/pdf/manuals/378684a.html. So we changed our nirio.ini to
[General] RpcServerPort=<portnumber> DeviceAccess="-*;+<my_ip>"
It turned out that this line as it is gets ignored and the port is random again. Adding a new line after [General] makes the RIO server not start at all and adding another one after the port number takes us back to the situation where the port is correct in http://yourPortNumber:3580/dumpinfo but we cannot reach the RIO server.
We have been trying around with this for days now and we are out of ideas, but there must be a way to use this device without just taking down the entire firewall.
Thanks in advance for your help and best regards.
