NetworkInspector.Exporters 0.4.0

NetworkInspector.Exporters

User-focused export package for writing either raw frames or parsed packets.

What This Is

NetworkInspector.Exporters contains two exporter families:

• Frame exporters (IFrameListener): preserve capture frame structure.
• Packet exporters (IPacketListener): serialize parsed packet data for analysis workflows.

Why It Stands Out

• One package covers conversion-oriented and analysis-oriented outputs.
• Consistent builder pattern across formats.
• Practical output targets (file, stream, and stdout depending on exporter).

Install

dotnet add package NetworkInspector.Exporters

Typical packet-export stacks also include:

dotnet add package NetworkInspector.Core
dotnet add package NetworkInspector.Protocols
dotnet add package NetworkInspector.Sources

Choose Your Export Path

Quick Start

Frame Export Quick Start (PCAPNG)

using NetworkInspector.Exporters.Pcapng;

using PcapngExporter exporter = PcapngExporter.CreateBuilder()
    .ToFile("capture.pcapng")
    .Build();

foreach (Frame frame in frames)
{
    if (!exporter.OnFrame(frame))
    {
        break;
    }
}

exporter.OnFinish();

Packet Export Quick Start (JSON)

using NetworkInspector.Exporters.Json;

using JsonExporter exporter = JsonExporter.CreateBuilder()
    .ToFile("packets.json")
    .Build();

foreach (Packet packet in packets)
{
    if (!exporter.OnPacket(packet))
    {
        break;
    }
}

exporter.OnFinish();

Export Format Map

Common Tasks

Export To Stdout

Use builders with stdout targets for pipeline-first workflows.

Stop Early On Limits

Pair exporters with upstream count/time/cancellation controls to avoid unbounded runs.

Finalize Correctly

Call OnFinish() before disposal to flush final metadata and trailing structures.

Limits And Thread-Safety Notes

• Treat exporter instances as single-threaded unless a format README states otherwise.
• Exporters do not validate upstream trust assumptions; validate and bound input at source/parse boundaries.
• Feature details (compression, schema variants, dialect nuances) are format-specific and documented in each sub-README.

Safe Usage (STRIDE)

• Spoofing: Preserve source provenance metadata outside the exporter output when chain-of-custody matters.
• Tampering: Surface and log malformed input handling decisions in calling code.
• Repudiation: Persist exporter configuration with output artifacts for reproducibility.
• Information disclosure: Treat JSON/CSV/Text outputs as potentially sensitive and protect destinations accordingly.
• Denial of service: Enforce cancellation and bounded processing in high-volume runs.
• Elevation of privilege: Run exporter processes with least-privilege write access.

Links

• GitHub repository
• NuGet package
• Source folder
• Issue tracker
• Pcapng exporter
• Blf exporter
• Asc exporter
• Json exporter
• Pbf exporter
• Csv exporter
• Text exporter
• Root overview

License

MIT License