Skip to content

Default port ranges

Dominik Roos edited this page Mar 16, 2021 · 28 revisions

SCION infrastucture elements use assorted well-known ports for communication, either directly on the host's IP stack (e.g. Prometheus monitoring) or via the dispatcher (SCION control plane traffic). To make things more consistent, actual deployments should default to the ports below.

The scheme uses 300XX ports for data-plane, 302XX for control-plane, and 304XX for monitoring. For example, to get the dispatcher's monitoring port, add 400 to its data-plane port (30041), giving 30441.

Dispatcher

Purpose Protocol Port
Data plane UDP 30041
Monitoring TCP 30441

The dispatcher is unusual in that it has no control-plane functionality.

Control service

Purpose Protocol Control Plane
Control plane (inter-AS) SCION/UDP 30252
Control plane (intra-AS) TCP 30252
Monitoring TCP 30452

SCIOND

Purpose Protocol Port
Control Plane TCP 30255
Monitoring TCP 30455

Border Routers

Border routers are more complex, in that they have control plane ports, data plane ports internally and ports for talking to other Border routers. Also, in some cases, more than one BR may be running on a given machine, so BRs use port ranges for different purposes. Deployments should always start with the lowest ports and use them in sequence (no gaps).

Purpose Protocol Port Range
Monitoring TCP 30442 - 30451
Data Plane* UDP 30042 - 30051

* This includes both links to other BRs as well as the AS-internal listening port

SIG

Purpose Protocol Port
Control Plane SCION/UDP 30256
Monitoring TCP 30456
Data Plane* SCION/UDP 30056

* This is the encapsulated traffic between SIGs.

Clone this wiki locally