Connecting EOS board to the internet

I've heard a variety of anecdotes around here, but never really an official sentiment - is it safe to connect EOS boards to the internet? As far as I can tell, it really shouldn't have an effect on anything, since the board shouldn't be trying to connect to the internet to begin with, but I'm not sure if this is actually the case. Also, I'm purely asking about giving the board internet access - I understand the importance of (properly configured) firewalls and flow control and whatnot on networks, and we should be able to handle setting all that up correctly.

Parents
  • Just to add, that beyond the "internet" is basically the question of what all should a lighting console be connected to. For most of us, it is going to be an isolated network just for lighting, but of course, as of the last 6 years or so there has been 2 network ports available on even the consoles. So for that, often what I think people do is they've got an isolated lighting control network (sACN, Net2/Net3, ArtNet, etc) for control over production rig equipment -- that should never actually route or connect with any other network (e.g. no network gateway)... And then on the other hand, there might be a second network that is used a bit more broadly for console controls to other production equipment (OSC, RFR, focus apps, etc), but again, that generally should be an isolated network.

    Here is the thing to remember, almost all production lighting equipment carries no authentication or security measures. If you're connected to that network then you can control said systems. For example, if the console and sACN is on the same building network (that provides internet access), but some music director (non-tech) downloads some music software that can output sACN, they can unknowingly start contributing to the output to the rig. When I go into other venues, you'd be surprised how often on the guest wireless network I can use iRFR and now control the lighting console. 

    The last point about isolation is network congestion -- we want to avoid co-mingling of different real-time network protocols on the same logical (or sometimes even logical -- vlan) networks. For example, everything is going well, and then al of the sudden, without your knowledge, a security contractor comes and installs a bunch of streaming video cameras, that are all nice 4k NDI based cameras, on the same network as your lighting network. Regardless of the "internet" itself question, that can have a meaningful impact on your ability to control your lighting rig if you used network DMX like sACN or ArtNet -- where a 10/100 wired network was just fine for your two universes, the video cameras will crush the network and you'll just walk in one day to a rig that has random control issues.

    All that to say, beyond the question of actual connecting to the internet itself, there is also a network stability & security question of even within the 4-walls of the building. 

Reply
  • Just to add, that beyond the "internet" is basically the question of what all should a lighting console be connected to. For most of us, it is going to be an isolated network just for lighting, but of course, as of the last 6 years or so there has been 2 network ports available on even the consoles. So for that, often what I think people do is they've got an isolated lighting control network (sACN, Net2/Net3, ArtNet, etc) for control over production rig equipment -- that should never actually route or connect with any other network (e.g. no network gateway)... And then on the other hand, there might be a second network that is used a bit more broadly for console controls to other production equipment (OSC, RFR, focus apps, etc), but again, that generally should be an isolated network.

    Here is the thing to remember, almost all production lighting equipment carries no authentication or security measures. If you're connected to that network then you can control said systems. For example, if the console and sACN is on the same building network (that provides internet access), but some music director (non-tech) downloads some music software that can output sACN, they can unknowingly start contributing to the output to the rig. When I go into other venues, you'd be surprised how often on the guest wireless network I can use iRFR and now control the lighting console. 

    The last point about isolation is network congestion -- we want to avoid co-mingling of different real-time network protocols on the same logical (or sometimes even logical -- vlan) networks. For example, everything is going well, and then al of the sudden, without your knowledge, a security contractor comes and installs a bunch of streaming video cameras, that are all nice 4k NDI based cameras, on the same network as your lighting network. Regardless of the "internet" itself question, that can have a meaningful impact on your ability to control your lighting rig if you used network DMX like sACN or ArtNet -- where a 10/100 wired network was just fine for your two universes, the video cameras will crush the network and you'll just walk in one day to a rig that has random control issues.

    All that to say, beyond the question of actual connecting to the internet itself, there is also a network stability & security question of even within the 4-walls of the building. 

Children
No Data
Related