Open Ports (Gateway Service)

Open Ports for Gateway Service and Sensor Connect

This chapter lists the connector ports required for the proper functioning of Gateway Service. Additional ports must be opened, in addition to the basic Cisco Spaces connector ports.

Figure 1. Open Ports for Gateway Service
Open Ports for Gateway Service

To verify IP address setup details for different regions, refer to Prerequisites for Configuring Connector 3.

Table 1. Gateway Service Firewall Rules
Source IP Address Destination IP Address Direction Transport Source Port Destination Port Protocol Further Information
Access Point IP address Connector Unidirectional TCP Any 8800 HTTPS/HTTP/2 gRPC telemetry streams for BLE, UWB, and GNSS data.
Catalyst 9800 Wireless Controller IP address Connector Unidirectional TCP Any 8800 HTTPS/HTTP/2 TDL gRPC telemetry streams from Catalyst 9800 wireless controllers.
Catalyst 9800 Wireless Controller IP address Connector Unidirectional TCP Any 8810 HTTPS/HTTP/2 WLC proxy connections for control channel.
Connector Catalyst 9800 wireless controller IP address Unidirectional TCP Any 830 NETCONF/SSH Controller onboarding and configuration. If NETCONF uses the default SSH port, open TCP port 22 instead.
Connector Cisco Spaces cloud Unidirectional TCP Any 443 HTTPS/WSS Control channel and data channel connectivity to Cisco Spaces.
Region Control/Data Endpoint
US (legacy) connector.dnaspaces.io
EU (legacy) connector.dnaspaces.eu
US connect.ciscospaces.io
EU connect.ciscospaces.eu
Singapore connect.ciscospaces.sg

The Local Firehose uses a Unix Domain Socket and does not require firewall rules. The socket path is /opt/connector/gateway/data/firehose.sock.