Skip to main content

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 should have a static IP address, which ensures consistent communication.
    • You’ll need to configure the subnet and gateway appropriately to allow traffic flow.

  2. Collector Functionality:

    • The collector reads, decodes, and processes data 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, over-the-air updates are pushed to the collector device.
    • Your technical team requires secure full remote access to manage and troubleshoot the collector.

  4. 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.

  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).

It’s crucial to avoid conflicts and ensure smooth communication within your collector’s virtual interfaces and networks. Let’s summarize the network ranges to avoid:

  1. Onsite Config Network:

    • Network Range: 192.168.150.0/24
    • Purpose: Used for onsite configuration.
    • Ensure that other devices or networks do not overlap with this range.

  2. Watchguard VPN Network:

    • Network Range: 10.8.0.0/24
    • Purpose: Used for Watchguard VPN connections.
    • Prevent any IP address conflicts with this range.

  3. Docker Network:

    • Network Range: 172.0.17.0/16
    • Purpose: Used by Docker containers.
    • Be cautious not to use IP addresses within this range elsewhere.

To enable communication between mobile devices on different subnets and your collector, you’ll need to set up proper routing. Here are the steps to achieve this:

  • In the Home Manage page of the cloud platform, navigate to the routing configuration.
  • Add an entry for the mobile subnet (the one where your mobile devices reside).
  • Specify the appropriate gateway IP address for the mobile subnet.
  • Ensure that the routing configuration allows traffic between the mobile subnet and the collector’s subnet.

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

Back to top