Network Management

It’s essential to configure your collector device properly for seamless communication within your LAN and beyond. Let’s break down the network requirements for Nexus Care:

1. Collector Deployment Considerations:

   • The collector device communicatesshould acrosshave a LANstatic IP address, which ensures consistent communication.
   • You’ll need to configure the subnet and thereforegateway considerationappropriately museto beallow giventraffic flow.

2. Collector Functionality:

   • The collector reads, decodes, and processes data from various sensors and services within the care home.
   • All routing logic occurs within the collector, and it uses a local socket connection to relay alerts to mobile devices.

3. Over-the-Air Updates and Remote Access:

   • To maintain an ever-evolving product and provide efficient support, you issue over-the-air updates to your collector appliances.
   • Your technical team requires secure full remote access to manage and troubleshoot the collector.

4. Outbound Rules (Collector Connecting to the deployment.Internet):

   • The following ports must be opened for outbound communication:
     • Port 22 (TCP): Secure Shell (SSH) for remote access.
     • Port 53 (UDP): DNS resolution.
     • Port 80 (TCP): HTTP for web traffic.
     • Port 443 (TCP): HTTPS for secure web traffic.
     • Port 51820 (TCP/UDP): Used by WireGuard VPN.
     • Port 51820 (UDP): Additional WireGuard VPN traffic.

5. Internal LAN Rules (Handsets Accessing the Collector):

   • Handsets using the mobile app should have unrestricted access via the LAN to the collector on the following ports:
     • Port 80 (TCP): HTTP for local communication.
     • Port 5557 (TCP): Custom port (ensure it’s not blocked).
     • Port 5559 (TCP): Another custom port (verify accessibility).
     • Port 8083 (TCP): Yet another custom port (check availability).

Remember to configure your firewall rules and network settings accordingly to ensure smooth operation of your Nexus Care system!