Network Config

Network Config v2.0.0 — a sysops toolkit for scanning, monitoring, alerting, benchmarking, and managing network configurations from the command line. All data is stored locally with full history tracking, search, and multi-format export.

Commands

Run network-config [args] to use. Each data command accepts optional input — with no arguments it shows recent entries; with arguments it records a new entry.

Features

• 20+ subcommands covering the full network config lifecycle
• Local-first storage — all data in ~/.local/share/network-config/ as plain-text logs
• Timestamped entries — every record includes YYYY-MM-DD HH:MM timestamps
• Unified history log — history.log tracks every action for auditability
• Multi-format export — JSON, CSV, and plain-text export built in
• Full-text search — grep-based search across all log files
• Zero external dependencies — pure Bash, runs anywhere
• Automatic data directory creation — no setup required

Data Storage

All data is stored in ~/.local/share/network-config/:

• scan.log, monitor.log, report.log, alert.log, top.log, usage.log, check.log, fix.log, cleanup.log, backup.log, restore.log, log.log, benchmark.log, compare.log — per-command entry logs
• history.log — unified audit trail of all operations
• export.json, export.csv, export.txt — generated export files

Each entry is stored as YYYY-MM-DD HH:MM| (pipe-delimited).

Override the data directory by setting NETWORK_CONFIG_DIR (not yet wired — default is ~/.local/share/network-config/).

Requirements

• Bash 4.0+ (uses set -euo pipefail)
• Standard Unix utilities: date, wc, du, tail, grep, sed, cat, basename
• No root privileges required
• No internet connection required

When to Use

1. Recording network scan results — run network-config scan "192.168.1.0/24 — 14 hosts found" after scanning your subnet
2. Monitoring network state over time — use network-config monitor "latency 12ms to gateway" to build a time-series log
3. Tracking alerts and incidents — log alerts with network-config alert "DNS resolution failing for api.example.com" for later review
4. Benchmarking and comparing configs — record benchmark results and compare configurations across environments
5. Backing up and restoring configurations — document backup/restore operations with network-config backup and network-config restore

Examples

# Show all available commands
network-config help

# Record a network scan result
network-config scan "Found 23 active hosts on 10.0.0.0/24"

# Log a monitoring observation
network-config monitor "WAN latency spike: 85ms avg over last hour"

# Create an alert entry
network-config alert "Interface eth0 dropped 12 packets in 5 min"

# Record a benchmark
network-config benchmark "iperf3 TCP throughput: 940 Mbps"

# View summary statistics
network-config stats

# Search all logs for a term
network-config search "eth0"

# Export everything to JSON
network-config export json

# Check tool health
network-config status

# View recent activity
network-config recent

How It Works

Network Config stores all data locally in ~/.local/share/network-config/. Each command logs activity with timestamps for full traceability. When called without arguments, data commands display their most recent 20 entries. When called with arguments, they append a new timestamped entry and update the unified history log.

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com