So, what can it do for me?
When you make an installation of a Neets control system with web interface (e.g. Sierra II) and you’re using it in a network, there are some things you should keep in mind as the installer.
The IT administrator in a company might want to know what consequences and security issues it could have to install a new network device.
So, what do I need to know?
When a control system is connected to a LAN network, several services starts and generates traffic on the network.
- LAN lookup: On UDP port 8000 identification information is broadcasted, when our configuration software Project Designer requests them. This information is only sent when maintenance is performed to the control systems.
- Central Control Live updates: On UDP port 8001 the control system broadcasts its status
information each time one or more LED changes state.
- Central Control draws service: on TCP port 5009, Neets Central control can active connect to
the control system and get status and execute button press.
- Extension device lookup: Every 3rd sec. a look-up/keep-alive status is transmitted using multicast address 126.96.36.199 port 7979.
The control system support IGMP, so by using a switch that supports IGMP you can make sure that data is only transmitted to the Neets control system and extension devices.
- Upload/download of project: TCP port 23 (Telnet) and 20+21 (FTP). The mentioned ports are used when changing the configuration of the control system.
The ports should not be used for anything else than the Neets configuration system.
Using graphical interface
When adding a graphical interface to the control system, each graphical interface which connects to a control system will create a TCP connection on port 80 (HTTP). To make sure that this connection is always open, keep-alive data is transmitted back and forth every fifth sec.
Whenever the control system is used, the traffic between the graphical interfaces and the control
system increases on port 80.