Skip to main content

ArcNet

ArcNet is the encrypted network interface of the EmberNet fabric. It gives the central platform and every remote site plain IP reachability to each other, so agents can check in and storage can replicate between nodes.

Where Flux is an identity-based application fabric, ArcNet is a straightforward encrypted IP network.

Flux is the primary transport, and ArcNet rides it. Flux reaches out from your site over the same outbound HTTPS that any web traffic uses, which is the egress industrial networks allow. ArcNet gives each node an address on your organization's own private network, and its traffic rides Flux, so a site gets plain IP reachability without opening anything inbound on the plant firewall. An endpoint that reports Flux as down is degraded.

Where it sits​

The fabric uses different layers for different jobs:

LayerCarried byWhat rides on it
IP routingArcNetNode-to-node reachability and storage replication between nodes
Application overlayFluxCluster management, cross-site app interfaces, device proxying, remote access
Ethernet bridgingAn optional bridgeLegacy protocols that need a broadcast domain, such as EtherNet/IP and PROFINET discovery

Most deployments only use the first two. The bridge is switched on only for equipment that cannot work any other way.

Managing a site does not depend on ArcNet. A site keeps a working control plane even when its ArcNet interface is down, so you do not need to design around losing it.

Addressing​

Each organization gets its own private address range, kept apart from every other organization's. The range is chosen so it never collides with the addressing already in your plant, which means the management network is still there when you need it during an incident, and there is room for any deployment to grow.

Tunnel status and peers​

Fireball manages ArcNet for you. We add, rename, enable, and disable peers, assign each one to your organization, and hand out its enrollment.

A peer counts as connected when it has checked in recently. ArcNet is quiet when there is nothing to send, so a genuinely idle peer can drift out of connected and recover the moment traffic resumes.

Tenant users do not manage ArcNet peers, and a peer that is not assigned to an organization belongs to none.

Relationship to the rest of the platform​

  • Flux is the transport. It carries application traffic, and ArcNet's traffic rides it too. They are complementary, not alternatives.
  • Network Devices reaches managed network equipment over ArcNet.
  • Ops deploys to clusters that are reachable over ArcNet.
  • Cinder replicates storage between nodes across it.

Next steps​