Bridge Network Requirements for CHeKT

Bridge Network Requirements for CHeKT

When troubleshooting the connectivity of a CHeKT Bridge it is important to understand a few details. 


1. Connectivity Requirements:

  • DHCP Enabled Network: The Bridge obtains an IP address using DHCP by default. The Bridge does support a static IP address configuration.
  • Port Settings: The Bridge needs outbound access on ports 80 and 443 through the network firewall. 
  • White List Information:  If the local area network is using a web proxy service, the LAN IP address of the bridge and the following domains need to be whitelisted in your firewall.
    • *.chekt.com (General catch all allowing for furture undefined domain names.)
      • api.chekt.com
      • firmware.chekt.com
    • *.rchekt.io
    • chekt-dev.s3.amazonaws.com
    • chekt-dev-device-log.s3.amazonaws.com
    • chekt-production-tts.s3.amazonaws.com
  • The Bridge uses a "Straight Through" network cable.
Warning
Port-Forwarding: Never create port-forwarding rules for the Bridge.  The Bridge and associated cameras do not need to be port forwarded. 




2. The Bridge Network Status Light Indicators:

  1. Turned off: Network Adapter is not initiated.  Typically a power-related issue. Or could be a hardware failure.
  2. Single Slow Blink: IP Address is not assigned to the Bridge. Typically this is a bad network cable, connectivity issue between the Bridge and the LAN, or the LAN does not have a DHCP Service.
  3. Single blink: Assigned IP address, but it is not able to connect to the CHeKT cloud. Typically this happens when Bridge does not have access to the Internet or can not connect to the CHeKT cloud server.
  4. Double blink: Connected to the CHeKT cloud, but the device is not registered to a customer account.
  5. Solid on: Connected to the CHeKT cloud and it is a registered device on an account.

3. Troubleshooting Network Connection Issues:

Notes
If Bridge will not connect and shows an Offline status in the CHeKT Portal what could it be?

1.    Power or Boot Related Issue: Status Light: Off

a.    If the Bridge Status light is not blinking after about 2 minutes of powering on, the issue is power or start-up related.

b.    The CKB304 Bridge requires about 400 mAmps

c.    The CKB312 Bridge requires about 800 mAmps

d.    If you have confirmed the Bridge has ample power, power off the unit for about 1 minute and then power it back on.

e.    If the blue status light still does not blink after about 2 minutes, the unit may have a firmware or hardware failure.

f.     To factory reset the firmware, use the hardware reset button as follows:

g.    If you suspect a hardware failure, contact your sales rep.

2.    Local IP Address issue: Status Light: Single Slow Blink

a.     Make sure the Bridge can obtain an IP Address from a local DHCP service on the network. This is typically done by a route for homes and small businesses. In larger businesses, they may have a dedicated DHCP server. 

b.    Check your physical network cable. Ensure you have a link light and status light for the Bridge ethernet port and on your network switch.

c.     If a local DHCP service is not available, then a static IP Address should be set using the local Bridge Admin interface.

d.    When the Bridge is unable to obtain an IP Address locally, the Bridge Emergency IP address will be enabled. This IP Address is found on the sticker of the Bridge and in the CHeKT Dealer portal for a registered device.

Notes
Accessing Emergency IP & Bridge Local Web Admin Page Details: Bridge Network Tab

3.    Routing or Outbound Permissions Issue: Status Light: Single Blink

a.    The Bridge communicates to the CHeKT cloud on ports 80 and 443. These are standard outboard ports for most computers.

b.    If either of these ports are blocked or filtered at the gateway or router of the network, the Bridge will not have access to the CHeKT cloud.

c.    In this case, check with the network administrator about providing whitelist access for the Bridge to communicate out. 

d.    DNS – If the Bridge is unable to query 8.8.8.8 & 8.8.4.4 DNS services, then available DNS servers should be added to the Bridge settings using the local Bridge Admin interface.

e.    NTP – Network Time Service. If the Bridge is unable to set the current time with the NTP service, then it will not be able to connect to the CHeKT Cloud.


    • Related Articles

    • CHeKT AI Server Installation and Operation

      There are 2 ways the AI Server can be discovered: via MAC Address on the network using the bridge tools or the Ai server discovery tool: Link to Discovery Tool Download How to use Network Scan Tool via CHeKT Dealer Portal: The CHeKT AI Server will ...

    • Cawamo-CHeKT Integration Guide

      The Cawamo AI Server integrated with the CHeKT platform creates video AI event notifcaitons for alarm monitoring centers and customers using the CHeKT Mobile app. This integation allows sites to leverage Cawamo's advances AI as detection zones for ...

    • Enabling and Understanding Site Service Plans

      Enabling and Understanding Site Service Plans Understanding Service Plans The Following Chart and Descriptions of services can be found in the billing section, of the gear settings, of your dealer portal *1 If yes on Prorated, dealers will be charged ...

    • CHeKT Bridge Network Tab Guide

      Portal Users can access direct network configuration settings for the CKB304 directly from the dealer interface: Click on the Bridge Settings: Click on the "Network" Tab: And you will arrive at the Network Configuration Screen: 1. Main IP: On this ...

    • Integrating Unifi Protect into CHeKT

      Integrating Unifi Protect into CHeKT Starting out in the web interface of the Unifi device: * Click Protect * Click Devices * Change name of camera to desired name * If you have more than 1 bridge, we recommend adding CH1.1 > Ch1.2 to keep track of ...