You say "it's pretty simple": it is simple for someone who has Linux experience working with networking and generally troubleshooting on a Linux system when something is not working correctly, but for someone who does not have this experience it's going to take some time, reading, experimenting, and learning. I encourage this but realize that not everyone wants to learn about working with embedded Linux systems, they have more important things occupying their time.
IMHO, the problem is that these boxes are basicly sold als (blackbox) PLC, that ought to be programmed via LabView - the fact that they're Linux boxes that just happen to be shipped with some homebrewn distro w/ some runtime for the LV stuff is more a side node.
You should turn that around and tell clearly that these are just microcomputers running Linux, that come with the PLC stuff preinstalled. That would make it clear for everybody that they're coping w/ a usual Linux system, and the PLC stuff is just yet another programming environment ontop (same layer as, lets say, a python or jee environment).
We're here, again, at the point that marketing often is far away from reality and just tries to tell people what they (supposedly) wanna hear, instead of what really *is*.
We both know better, but the common customer out there does not - so we gotta tell 'em clearly - so they know what to expect and where to get proper documentation for what. (basicly it's communication and education problem, not a technical one)
Apropos marketing vs. reality: NI officially claims to provide Linux supports. Actually, hat's just wrong - there's only support for certain *specific* (binary) Distros (in specific versions) and even just specific kernel *images*. The forum is full with troubles that root back to exactly that root problem. Binary kernel drivers (as well as binary libraries) are just unusable for any serious industrial application.
Finally, just to clarify, there aren't "expensive eth cards" NI sells for a Compact RIO: it's either the ports that are built-in (usually 2, including on the 9035 that the OP is using) or a USB-based network adapter.
Assuming these devices run with the shipped kernel out-of-the-box (which I wouldn't rely on).
Otherwise all hell breaks loose, eg. due proprietary kernel drivers.
(you don't expect people to backport drivers and bugfixes to your old vendor kernel, do you ? 🐵
Linux Embedded / Kernel Hacker / BSP / Driver development / Systems engineering
