Application Msg BrokerAccepts the local application message
01LAYERTM OPERATING PLATFORM
One operating environment across FlowDirector, Service Node, and FlowMagic for consistent management, service design, and visibility operations.
Unified by 01LayerTM
01LayerTM is the intelligent unified operating platform that seamlessly integrates appliance control, advanced service design, high-performance traffic processing, real-time monitoring, and comprehensive audit-ready workflows — delivering one consistent, powerful experience across your entire ecosystem of FlowDirector, Service Node, and FlowMagic deployments.
Build Service and Analysis Flows from Modular Functions with Clarity, Speed, and Control.
The 01Layer Data Diode Solution is designed for security boundaries where information must leave a protected environment without creating a return communication path. Application-level message processing is terminated independently on each side of the boundary, while physical or logical enforcement permits traffic only in the approved source-to-destination direction.
Within the protected source zone, the Application Message Broker passes each accepted message to the DD Framer/Encryptor. The message is framed, fragmented, integrity-protected, and optionally encrypted before the DD Port or Virtual DD Port transmits it across the one-way boundary.
At the destination, a regular receive port forwards the packet stream to the DD DeFramer/Decrypter. The fragments are validated, decrypted when required, and reconstructed into the original message. The Application Message Sender then delivers the complete, validated message to the destination application. No acknowledgement, control session, or application-level return channel traverses the boundary.
The DD Framer/Encryptor converts each accepted application message into protected fragments. The DD DeFramer/Decrypter validates, decrypts, and reconstructs complete messages without acknowledgements or control traffic crossing the one-way boundary.
The Data Diode Sender accepts each application message from its upstream queue and converts it into a bounded, transmit-ready packet stream. It segments the message to the configured MTU, applies diode framing and integrity controls, encapsulates the fragments for UDP or ESP transport, and invokes encryption when enabled.
The Data Diode Receiver accepts only traffic that matches the configured UDP destination port or ESP SPI. It decapsulates and optionally decrypts the packet stream, validates the diode framing and fragment controls, reassembles complete messages within configured resource limits, and releases validated output to the downstream queue.
The sender and receiver operate without a cross-boundary acknowledgement or control session. Direction is enforced by an absent return fiber, a forward-only NextIO service edge, or both, while reply-dependent protocols terminate locally on each side of the boundary.
| Transport | Plain IPv4/UDP or ESP AES-256-GCM; optional 802.1Q VLAN tagging. |
|---|---|
| Framing | Version 1, 56-byte diode header with stream/message identity, fragment map, timestamp, flags, and header CRC32C. |
| Configured bounds | 512–9,216 byte output MTU; 64 KB–4 MB message profiles; up to 65,535 fragments per message. |
| Failure posture | Oversize, malformed, CRC-failed, replayed, overlapping, timed-out, or resource-constrained work is rejected and counted. |
| Observability | Message, byte, fragment, drop, CRC, timeout, queue, control, and cryptographic counters are exposed per component. |
Cloud networks do not expose a removable Tx/Rx fiber pair. Place DD Sender and DD Receiver in separate trust zones, allow only source-to-destination traffic, and align routes, security policy, and the NextIO service graph so no reverse edge exists.
This shared reference summarizes the common property groups that appear across NextIO components: identity, display behavior, and pad connectivity.
Display Properties change how the component is drawn on the canvas for service review and documentation. They do not change packet processing behavior.
Use the + control to add another numbered input or output pad. The Edit control beside each count opens the matching pad-list editor, where users can name pads, reorder pads, delete entries, then apply or close the dialog.
01LayerTM makes packet services easier to create by turning sources, processing functions, and destinations into connected building blocks. The same model supports troubleshooting, validation, monitoring, replay, and analysis workflows.
Bring traffic into the service canvas from physical ports, port groups, bonded links, OS devices, virtual interfaces, PCAP files, and TAP sources. Each source enters the same flow model, so live traffic and recorded traffic can be designed, validated, and reused consistently.
Drag NextIO components onto the canvas, connect each node to form full packet processing data path. 01Layer's Flow-Based Service Design Environment turns complex into an intuitive visual experience, delivering instant validation, zero errors, and production-ready services in minutes with total confidence.
01LayerTM helps teams reuse the same flow-based method for packet brokering, capture, replay, filtering, analysis, and validation instead of rebuilding each workflow from scratch.
Route results to egress ports, tool groups, OS interfaces, virtual devices, PCAP files, or serial TAP workflows from the same service definition.
DiscoverConfigureConfirm
01LayerTM unifies the same operational model across the visibility stack.
Core capabilities shared across appliances and deployment types.
Workflows and feature sets tailored to each product family while preserving a common operating model.
FlowMagic Visibility Studio extends 01LayerTM with generation and validation tools for test-driven operations.
FlowDirector extends 01LayerTM with high-throughput packet broker operations and unified SPAN/ERSPAN capture architecture.
Work with Infinicore engineering to map 01LayerTM capabilities to your FlowMagic and FlowDirector deployment goals, or open the user manual for operator workflows and system-management references.
