SECURE LAYER 2 NETWORK BRIDGING
Create one centrally managed Layer 2 fabric across distributed agents. Connect local bridges through encrypted, resilient relay paths—without configuring a separate tunnel or TAP adapter for every remote location.
Start with two locations and extend the authorised fabric when ready.
ONE AUTHENTICATED ETHERNET ENVIRONMENT
DC Core Ethernet Fabric turns geographically distributed networks into one authenticated Ethernet environment, with central authority separated from the live agent-to-agent data plane.
Each location connects through a single local TAP adapter. One attachment can reach multiple authorised agents without maintaining a separate virtual adapter for every point-to-point path.
Central authorises participating agents and source MAC addresses before they use the fabric. Conflicting, unapproved or incorrectly located devices fail closed.
Agent-to-agent sessions protect every Ethernet frame with AES-256-GCM and carry traffic over automatic, failover, striped or redundant relay paths.
LAYER 2 WITHOUT TUNNEL SPRAWL
The fabric keeps standard Ethernet at each edge while adding explicit identity, encryption and failure handling between locations.
Connect one local bridge to many remote agents without multiplying tunnel interfaces as the fabric grows.
New, conflicting or incorrectly located MAC addresses must be resolved by Central before traffic is accepted.
AES-256-GCM binds the network, source and destination agents, session, epoch and sequence to the traffic.
Choose automatic routing, failover, striping or redundant delivery. Existing connections can survive an individual relay failure without blocking other participants.
Active sessions and previously authorised MAC mappings can continue in memory while new authority-dependent activity stays blocked.
Hosts, virtual machines, containers and appliances keep communicating through their existing local network model.
HOW IT WORKS
Central establishes who may participate. The approved agents then forward Ethernet across protected data-plane sessions and resilient relay infrastructure.
Install an Ethernet attachment on each agent and connect its TAP adapter to the appropriate local bridge.
Central validates agents and MAC addresses, prevents duplicate ownership and establishes secure connectivity.
Known unicast goes only to the destination MAC owner. Broadcast and multicast replicate across authorised connections.
ONE MANAGEMENT EXPERIENCE
Add locations, review identity, choose resilience and investigate events from one solution. Low-level infrastructure hashes, process IDs and session identifiers remain available for diagnostics without dominating everyday operations.
Discuss fabric management →SECURITY BY DESIGN
Membership, source identity and session state are explicit. Unauthorised traffic fails closed, replayed frames are rejected and unavailable peers cannot consume unbounded resources.
IDEAL USE CASES
Use the fabric when applications, devices or operational constraints require Layer 2 adjacency across locations—but traditional VPN tunnel sprawl is difficult to secure and operate.
Connect branch, industrial and manufacturing Ethernet environments while keeping local devices on familiar network interfaces.
Bridge hosted and local compute without building a separate point-to-point tunnel for every participating location.
Bridge approved security and building-system Ethernet segments across sites without directly publishing device interfaces or maintaining a separate VPN tunnel per location.
COMMON QUESTIONS
Start with the locations, local bridge design and Layer 2 behaviours that must cross the fabric. We can then scope identity, relay and continuity policy.
A Layer 2 Ethernet fabric extends one authenticated Ethernet environment across distributed locations. DC Core connects local bridges through approved agents, encrypted agent-to-agent sessions and resilient relay paths.
Each participating agent uses one local TAP attachment. That attachment can connect its bridge to multiple authorised remote agents, avoiding a separate virtual adapter for every point-to-point connection.
Central validates participating agents and discovered MAC addresses, prevents duplicate ownership and authorises source MAC locations before traffic can use the fabric. Unknown or conflicting identities fail closed.
Previously authorised MAC mappings and active sessions can remain available in memory. New devices and new connectivity stay blocked until Central authority returns, so a control-plane outage does not silently expand access.
Yes. Attach the fabric TAP to an existing Linux bridge, or let the agent provision a managed TAP and bridge. Hosts, virtual machines, containers and appliances continue using standard Ethernet.
Yes. DC Core can supply a preconfigured fabric bridge appliance for an agreed site. The installer connects power, the designated Ethernet segment and approved uplink; DC Core handles fabric onboarding and remote path validation. Local switching, cabling, VLAN placement, physical protection and system safety remain part of the site design.
CONNECTED CAPABILITIES
BUILD ONE SECURE ETHERNET FABRIC
Connect distributed networks through centrally authorised identities, encrypted agent-to-agent sessions and resilient relay infrastructure.