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:
-
Collector Deployment Considerations:
- The collector device should have a static IP address, which ensures consistent communication.
- You’ll need to configure the subnet and gateway appropriately to allow traffic flow.
-
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.
-
Over-the-Air Updates and Remote Access:
- To maintain an ever-evolving product and provide efficient support, over-the-air updates are pushed to the collector device
- Your technical team requires secure full remote access to manage and troubleshoot the collector.
-
Outbound Rules (Collector Connecting to the Internet):
- The following ports must be opened for outbound communication:
- Port 51820 (TCP/UDP): Used by WireGuard VPN.
- Port 51820 (UDP): Additional WireGuard VPN traffic.
- The following ports must be opened for outbound communication:
-
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).
- Handsets using the mobile app should have unrestricted access via the LAN to the collector on the following ports:
Remember to configure your firewall rules and network settings accordingly to ensure smooth operation of your Nexus Care system!