Background:
Because there are many components in motion, we've compiled a list outlining requirements, clarifications, and areas of responsibility to ensure the seamless integration between Inlet and the lock system.
Read more about the security principles for Inlet and the connections to locks here.
Practical and Technical Requirements:
To enable Inlet to communicate with NOX Central(s) you need to enable SSH in the NOX Config, and first you need to generate an SSH Private Key (.ppk) to import into the NOX SSH Server, we recommend using PuTTYgen (PuTTY Key Generator) please use the SSH Guide from ARASWiki https://araswiki.com/da/01_general/02_configurationmanual/trix/ssh/start?s[]=ssh
Optionally, you can buy the SSH configuration + installation help from ARAS, in this case ARAS will provide a Private Key and online help with import and configuration as required when using SSH Server in NOX.
You need to allow inbound TCP connections from the Public IP to the NOX Central LAN IP on SSH standard port 22 (this can be changed if required)
The SSH feature requires a T30 CPU or newer (NOX Corporate), it will not run on a NOX One, unless you replace the original VF50 CPU with a T30 CPU or newer.
- NOX door areas are installed and fully commissioned in the usual manner by the installer.
- The NOX Central needs to be online and configured correctly according to manufacturer.
- Make sure inbound TCP traffic is allowed to the NOX Central.
- To set up SSH in NOX Config, you need to enable it in General settings -> SSH secure shell.
- Create a new user for Inlet in SSH.
- Make sure the Inlet user has the rights to read Access Rights and control doors and users in the system.
- Inlet needs to receive the following information by mail to support@inlet.tech:
- Customer Name
- Information on what locks and lock groups Inlet should set up.
- NOX username and password
- Public URL or static IP address of the SSH server.
- Inlet retrieves IDs from the locks to configure Inlet with the locking system.
- Inlet provides information to the main system/booking system for testing.
- Inlet requires a minimum of 2 weeks of testing with the main system/booking system after the installer has completed all the steps above.
IP addresses that need to be whitelisted:
Required: 52.164.185.179
Required: 77.110.204.178
Ports that need to be mapped:
External TCP port 22 to internal TCP port 22 on the Server - (this can be changed if required).
Access System Server IP Address Configuration:
A static IP address should be assigned to prevent it from being changed during a restart, and causing downtime due to the mapping in the previous point