Skip to main content

DFS Hardware - IT Prerequisites

Checks that must be completed prior to installing any Navitas Equipment

Written by Navitas Team

DFS Hardware - IT Prerequisites

Please note that the following prerequisites must be checked and approved before the installation takes place:

1. HUBS

  • The Hub(s) will each need to have a dedicated power socket and they should not be powered down at any time. This must be located close to the appliances (fridges/freezers).

  • There will need to be a network available onsite with internet connection and an SSID and Password will need to be available. Please note that the network:

    • Must not utilise splash screens/captive portals as the Navitas solution does not support this.

    • Must not include an Enterprise SSID as the Navitas solution also does not support this.

  • Alternatively, a wired connection could be used to connect the Hub(s).

  • The Wi-Fi must provide a strong signal for where the Hub(s) and Probe(s) are to be utilised/installed.

  • The Wi-Fi must support 2.4Ghz. 5Ghz is not supported.

Hub Firewall Rules

While the IP addresses are provided, we would strongly recommend that any firewall rules are configured based on the CNAME rather than the IP address.

CNAME

IP

Protocol

Port

Reason

chirp.navitas.eu.com

46.101.87.7

UDP

1700

Supports Pods using the EU868 plan

chirpus.navitas.eu.com

178.62.67.161

UDP

1700

Supports Pods using the US915 plan

chirp915au.navitas.eu.com

165.227.234.233

UDP

1700

Supports Pods using the AU915 plan

chirp923.navitas.eu.com

178.128.36.104

UDP

1700

Supports Pods using the AS923-1 plan

Note: While the IP addresses are provided, we would strongly recommend that any firewall rules are configured based on the CNAME rather than the IP address. As we evolve and improve our IOT platform it is likely that the IP addresses will change.

CNAME

IP

Protocol

Port

Reason

apps.navitas.eu.com

35.195.27.57

TCP

443 (HTTPS)

Allows access to the Navitas Login Server

dfs.navitas.eu.com

35.227.247.204

TCP

443 (HTTPS)

Allows access to the Digital Food Safety platform

CNAME

IP

Protocol

Port

Reason

Not applicable

8.8.8.8

ICMP

Not applicable

Used to validate that the hub has a valid internet connection

8.8.4.4

ICMP

1.1.1.1

ICMP

139.130.4.5

ICMP

Not applicable

8.8.8.8

TCP

53 (DNS)

DNS resolution for CNAMEs

8.8.4.4

TCP

53 (DNS)

ntp.ubuntu.com

Not applicable

UDP

123 (NTP)

Time Synchronization (NTP)

0.ubuntu.pool.ntp.org

UDP

123 (NTP)

1.ubuntu.pool.ntp.org

UDP

123 (NTP)

2.ubuntu.pool.ntp.org

UDP

123 (NTP)

0.openwrt.pool.ntp.org

UDP

123 (NTP)

1.openwrt.pool.ntp.org

UDP

123 (NTP)

2.openwrt.pool.ntp.org

UDP

123 (NTP)

3.openwrt.pool.ntp.org

UDP

123 (NTP)

chirp.navitas.eu.com

46.101.87.7

UDP

1700

Connectivity to the Navitas IOT platform.

Only the correct regional address is required, but all can safely be added

chirpus.navitas.eu.com

178.62.67.161

UDP

1700

chirp915au.navitas.eu.com

165.227.234.233

UDP

1700

chirp923.navitas.eu.com

178.128.36.104

UDP

1700

apps.navitas.eu.com

35.195.27.57

TCP

443 (HTTPS)

(OPTIONAL) Access to the Navitas Platform via the wireless Access Point.

dfs.navitas.eu.com

35.227.247.204

TCP

443 (HTTPS)

2. TABLETS

If Samsung Tablets are being used, the client will need to ensure that the Samsung keyboard is not set as default due to the fact that the numerical keyboard does not include a '-' sign for inputting negative numbers which is required for manually adding temperatures.

  • There must be spare power sockets available in the Food Prep areas for charging the other devices.

3. SMARTPROBES

Probe Firewall Rules

Where a CNAME is provided we strongly recommend that any firewall rules are based on the CNAME and not the IP address as the exact IP address may change over time.

Note: that these represent ‘forward’ DNS rules suitable for rulesets, and not ‘reverse’ DNS mappings that might appear in device logs. This is most applicable to Google-related endpoints where reverse DNS may show as subdomains under 1e100.net

Destination Host

IP

Protocol

Port

Reason

apps.navitas.eu.com

35.195.27.57

TCP

443 (HTTPS)

Navitas Login Server

dfs.navitas.eu.com

smartprobes.dfs.navitas.eu.com

35.227.247.204

TCP

443 (HTTPS)

Required for access to the Digital Food Safety platform and SmartProbe APIs

*.anydesk.com

*.net.anydesk.com

TCP

6568

AnyDesk Network (Primary)

*.anydesk.com

*.net.anydesk.com

TCP

80, 443

AnyDesk (Fallback)

o<number>.ingest.sentry.io o<number>.<location>.ingest.sentry.io

34.120.195.249/32

34.120.62.213/32

34.160.81.0/32

34.102.210.18/32

2600:1901:0:5e8a::/64

2600:1901:0:7edb::/64

TCP

443

Transmission of application telemetry from the Navitas SmartProbe Application to Sentry for remote analysis and alerting

fcm.googleapis.com

gcm-http.googleapis.com

TCP

443

Notification Service (Primary)

(No specific host. A port-based rule is required)

TCP / UDP

5228-5230

Persistent Notification Connection

connectivitycheck.android.com

connectivitycheck.gstatic.com

www.google.com (for /generate_204)

TCP

443

Internet Connectivity Check

time.google.com

time.android.com

(Or a local NTP server)

UDP

123 (NTP)

Time Synchronization (NTP)

(Customer's configured DNS server)

TCP / UDP

53

Domain Name System (DNS)

play.google.com

*.gvt1.com

dl.google.com

dl-ssl.google.com

TCP

443

Google Play Store & App Downloads

*.googleapis.com

*.googleusercontent.com

*.gstatic.com

TCP

443

General Google APIs & Content

accounts.google.com

TCP

443

Account Authentication

Did this answer your question?