PACEdge User Manual
Section 5
GFK-3178B
Nov 2020
PACEdge Architecture Details
11
5.2
PACEdge Communication and Data Flow
Considering that most of the services in PACEdge are implemented using Docker Containers main
communication between them is implemented using network interfaces. For security reasons and
traffic segregation PACEdge is using an internal user-defined bridge network, with IP subdomain
address 172.18.0.0/16. Each of the Docker containers is connected to this network and can access
external services, such as the Internet, but are not directly accessible from outside. Some services,
such as Traefik and external MQTT broker do have open ports (80, 443, 1883) which enable these
services to be reached from the outside.
External Ethernet ports and their IP addresses can be easily managed via Cockpit or other standard
Linux tools.
Figure 7: PACEdge Network Communication Paths
External Network
ex: 192.168.2.0/24
Cockpit
Node Red
Grafana
InfluxDB
Portainer
Chronograf
MQTT int
MySQL
Traefik
P: 80, 443
Nginx
PHP
User
Container 1
Internal user-defined bridge
network:
emersonedgestack_internal
172.18.0.0/16
MQTT ext
P: 1883
Eth 1
(enp1s0)
(eth0)
Eth 2
(enp2s0)
(eth1)
Linux native
applications
Linux with PACEdge Software