Network and firewall requirements for Neat

Last updated on April 9, 2021

This article describes the network and firewall requirements for all Neat devices.

DHCP

Neat devices obtain their IP address and other network parameter configurations (e.g. Default Gateway, DNS etc.) via DHCP. The network should also allow IP multicast packets within the same subnet or VLAN.

Please note, when pairing a Neat Bar and Neat Pad, both devices must be connected to the same subnet (or VLAN), such that multicast packets are allowed to travel between the two devices. This is because Neat relies on mDNS protocol, which uses multicast packets.

IMPORTANT: Although in most cases network devices will allow mDNS service to run in the same subnet, some networks can restrict such services. In that case, you may need to manually add the mDNS service string to your network device. Neat devices register with the service string: _neat._tcp.

NTP server

Neat devices require NTP (Network Time Protocol) server for a variety of functions, and therefore a valid NTP server is a requirement when setting up and operating the devices. Neat uses the standard UDP port 123 to reach out to the following NTP server (default):

time.neat.no (IP address: 34.91.253.47)
Location: The Netherlands*

Newer firmware also supports two additional methods of providing NTP to the system; either the network can provide an NTP server address via DHCP option 42, or a user can manually enter an NTP server address during setup.

Cloud storage

Neat devices are required to access Neat’s cloud storage to download latest firmware. This is done over HTTPS (TCP port 443) and the server address is:

https://ota.neat.no (IP address: 34.107.186.64)
Location: The USA*

*Disclaimer: Please note that both NTP service and Cloud storage services are hosted by Google cloud services and therefore their respective IP addresses and locations may change.

Zoom room software requirements

After Neat firmware is installed, Neat devices will run Zoom Room software provided by Zoom, and connect to the Zoom backend. For ongoing operation, ensure all Zoom resources are available via your firewall as described in the following articles provided by Zoom on this topic.

https://support.zoom.us/hc/en-us/articles/201362683-Network-firewall-or-proxy-server-settings-for-Zoom

https://support.zoom.us/hc/en-us/articles/203680389-Firewall-Configuration-for-Zoom-Rooms

Summary

ProductProtocolPortsFirewall rulesDescription
NeatDHCPUDP 67, 68None requiredObtain IP address, default gateway, DNS etc.
NeatmDNSMulticast packets to
224.0.0.251
UDP 5353
None required (multicast traffic remains local to the subnet)Discovery and pairing
Neat NTPUDP 123Open UDP 123 on firewall to:
time.neat.no (default) 
NTP time server for various operations
NeatHTTPSTCP 443Open TCP 443 to: https://ota.neat.no Access cloud storage for software downloads
ZoomVariousVariousFollow Zoom’s advice on Zoom and Zoom RoomsTo allow Zoom Room software to connect to Zoom cloud
Table: Neat’s Network and Firewall requirements

IMPORTANT NOTE

The firewall requirements on Neat Bar and Neat Pad* differ depending on the software version running on these devices. Until April 2020, Neat software versions required multiple network resources to be accessible for the initial configuration process. After April 2020, Neat simplified its network requirements. When Neat devices are shipped out from manufacturing locations, some may be running pre-April 2020 firmware. For simplicity and to avoid any confusion, this article only describes the network requirements for newer (post April 2020) software releases. All Neat devices will upgrade to the latest software version once connected to the network.
If you continue to encounter issues after opening the network ports above, please reach out to Neat’s technical support team at
support@neat.no.
*All Neat Boards were manufactured after April 2020 and therefore this article (with newer firewall requirements) applies to them.