Ion network isolation and iRFR wireless routing

I recently put an Ion in a local college and during training indicated to the owner that he could get the iRFR ap to connect, but that to do so he should request a dedicated wireless router for the lighting network.  Of course, IT came back with "why do you need a dedicated router when we've got dozens of WAPs in that building?"  The Ion is running only DMX outputs (for now) and I noted on http://www.etcconnect.com/Community/wikis/products/irfr-how-to-setup-your-wireless-network.aspx the "do not allow your lighting network to be directly connected to the internet", but not being an IT/networks guru...

Am I wrong and there isn't any problem with having them use the same wireless router as other network devices - assuming they can within the 10.100 ETC address scheme?  If I'm not wrong, is there a doc out there that can explain, in IT, why its a bad idea to put the lighting network in contact with either the LAN and/or the internet?

Parents
  • Short answer is simply that you want to minimize the traffic on the lighting network and eliminate the possibility of unwanted access to the lighting computers. If you put the lighting network on the internet you are greatly increasing the traffic on your lighting network which can cause all sorts of problems with console to console traffic and you are also opening your network up to outside access and attacks. do you really want a virus on your lighting console? It doesn't have any kind of virus protection and you don't want to run any antivirus on it because of the resources that software will take up. It is best to keep your lighting system isolated from all non essential computers and networks.
  • The irfr interface has no security to speak of. If you know it IP address and name of the console then you can control the show if RFR traffic is enabled. Anybody with a little money can wreck a performance either wilfully or by accident. 

     

Reply Children
No Data
Related