This page describes the flow matrix of the ORS
The table below describes incoming traffic (from outside to ORS):
| SlapOS Service |
From |
Destination IP |
Destination Port |
Traffic Type |
Purpose |
| RAN |
frontend |
RAN-IPv6 |
8035 |
https |
web server of the monitoring |
| frontend |
RAN-IPv6 |
6080 |
https+websocket |
websocket of the RAN |
CORE
(optional) |
frontend |
CORE-IPv6 |
8035 |
https |
web server of the monitoring |
| frontend |
CORE-IPv6 |
6081 |
https+websocket |
websocket of the core network |
| frontend |
CORE-IPv6 |
6082 |
https+websocket |
websocket of the IMS |
| enb |
CORE-IPv6 |
2152 |
UDP |
GTP-U packets |
| other mme |
CORE-IPv6 |
2123 |
UDP |
GTP-C |
| |
CORE-IPv6 |
[6666-6667] |
TCP |
interfaces Nf of 5C |
| |
CORE-IPv6 |
[5555-5563] |
TCP |
interfaces Nf of 5C |
| |
CORE-IPv6 |
5571 |
TCP |
interfaces Nf of 5C |
| |
CORE-IPv6 |
5592 |
TCP |
interfaces Nf of 5C |
| MONITOR |
frontend |
MONITOR-IPv6 |
8196 |
https |
web server of the monitoring |
SSH
(optional) |
anywhere |
SSH-IPv6 |
2222 |
ssh |
ssh debugging |
The list below describes outgoing traffic (from ORS to outside):
- SlapOS client:
- https traffic to frontend (to reach the NMS)
- https traffic to frontend (to reach the shacache for sotfware release upgrades)
- RAN service:
- S1AP traffic from enb (only is internal core is not used, source IP is configurable)
- fluentd traffic to Wendelin
- OS upgrades : https traffic to package repositories
- NTP
- DNS