Omniasec Labs

Technology research & product development

GNS3 Agent: a network-lab exploration.

Historical project record. The original page described Windows-first diagnostics, GNS3 connectivity and evidence capture. Current maintenance and capability have not been independently reverified.

The problem being explored

Network labs can fail between environment setup, instructions and evidence. Python packages, virtualization, local paths, ports and server versions can fail independently. Students and engineers then spend time translating lab instructions into device actions, validation and reports.

The intended project explored visible, bounded assistance for those workflows. The earlier target environment was Windows and GNS3 2.x; that is context, not a current compatibility guarantee.

Original capability record

The labels below preserve the earlier archive's distinctions. They are attributed historical reports, not new verification of implementation, support or production readiness.

Environment doctor
Python runtime, packages, Windows paths, GNS3 installation, processes and virtualization checks.Originally reported implemented; not reverified here.
REST connectivity
Typed connection to the GNS3 REST API with structured success and error results.Originally reported implemented; not reverified here.
Server inspection
Server information, projects, templates, configuration and diagnostic summaries.Originally reported implemented; not reverified here.
Report artifacts
JSON and Markdown reports for diagnostic and read-only inspection output.Originally reported implemented; not reverified here.
Topology execution
Bounded creation/configuration workflows with checkpoints and rollback awareness.Originally reported in progress; not reverified here.
Evidence automation
Scope-aware screenshots, command evidence, validation and reporting.Originally planned; not reverified here.

The intended execution loop

  1. Understand the environment, request, instructions, constraints and required evidence.
  2. Plan device actions and validation checkpoints before modifying state.
  3. Execute only approved tools and endpoints with visible boundaries.
  4. Verify state, connectivity, expected outputs and failure conditions.
  5. Stop, explain or return control when confidence or authority is insufficient.
  6. Document commands, results and limitations in traceable artifacts.

Architecture described in the archive

Interface
CLI in the earlier description; desktop and guided workflow interfaces were future ideas.
Orchestration
Task planning, typed results, policy checks, checkpoints and execution state.
GNS3 adapter
Typed REST operations for server, project, template, node and link workflows.
System diagnostics
Windows process, path, port, package, installation and virtualization inspection.
Evidence
Structured logs, JSON/Markdown artifacts, screenshots and reporting.
Model assistance
Optional local or cloud reasoning assistance according to task sensitivity.

Audience and limits

The original intent included students learning through repeatable labs, educators investigating setup problems and technical teams exploring controlled test environments. No current early-access program, release timeline, supported service or capacity is promised.

Before use, request current source, installation instructions, tests, permissions and supported environments. The earlier page linked to the founder's GitHub profile, not a dedicated public repository; no repository URL is invented here.

Discuss the project or return to the work archive.