If something does not work, it may be due to a firewall blocking a particular communication channel and / or poor network configuration. Here you can find all ports and communication protocols across all FLOW devices. For better clarity, the list is divided into three sections, i.e.:
FLOW framework specific ports - contains ports related to the FLOW framework
FLOW device service ports - contains ports used for servicing the FLOW devices
General purpose ports - common ports needed for camera streams, NTP, or when the device is remotely configured or installed
FLOW remote installation (TrafficEnterprise) - necessary ports if remote installation is required
FLOW framework specific ports:
These ports and protocols are critical to making the FLOW framework fully functional. Blocking some ports may cause some features/functions to stop working.
Description | Port and protocol | Input/Output |
FLOW REST API & communication between FLOW Insights and FLOW Block | 8088/TCP | Input |
Communication between FLOW Insights and FLOW Node | 5556/TCP | Input |
Necessary for the update of TrafficXRoads and TrafficEmbedded units via FLOW Insights | 8089 | Input |
FLOW video server | 8090/TCP | Input |
FLOW UDP server | 55570/UDP (configurable) | Input |
FLOW webhook outputs | ?/TCP (port is defined by receiving part) | Output |
FLOW mDNS | 5353/UDP | Input |
Note that it is possible to connect to multiple FLOW devices with a single IP using port forwarding. It is necessary to specify two ports when accessing the devices this way, the FLOW Block - 8088 (for transfer of traffic data) and FLOW Node - 5556 (for image data transfer). When logging into the device in FLOW Insights, type your IP address and ports in the following format [IP]:[PORT BLOCK]:[PORT NODE] as shown in the example below.
FLOW device service ports:
These ports are required for services related to the following products: T.Enterprise, T.XRoads, and T.Embedded systems. Get datasheets and manuals for the products here.
Description | Port and protocol | Input/Output |
Web admin console | 8000/TCP | Input |
DataFromSky service VPN - 172.105.65.31 | 31228/UDP | Output |
General-purpose ports:
The RTSP for receiving video feed from the camera is critical for running FLOW. The rest depends on the specific cases.
Description | Port and protocol | Input/Output |
Web data download | 443 and 80/TCP | Output |
DNS service | 53/UDP | Output |
SMTP service | 495, 993 and others/TCP | Output |
NTP time synchronization | 123/UDP | Output |
RTSP camera stream | port depends on camera configuration/TCP and UDP | Output |
FLOW remote installation:
Min. network settings for remote installation in the case of TrafficEnterprise.
Description | Port and protocol | Input/Output |
Web data download | 443 and 80/TCP | Output |
DNS service | 53/UDP | Output |
RTSP camera stream *** | port depends on camera configuration/TCP and UDP | Output |
FLOW REST API & communication between FLOW Insights and FLOW Block *** | 8088/TCP | Input |
Communication between FLOW Insights and FLOW Node *** | 5556/TCP | Input |
DataFromSky service VPN - 172.105.65.31 | 31228/UDP | Output |
*** These ports are not required for installation, but are recommended for basic testing after installation is complete.
Port taxonomy:
output = FLOW device creates a connection to the target port
input = FLOW device listens for a connection on this particular port
Learn about FLOW's settings: Block settings, Analytics settings
Learn about FLOW's API
Read more about how to connect your device to FLOW here.