Created comprehensive VPN setup tooling for Peaceful Spirit L2TP/IPsec connection and enhanced agent documentation framework. VPN Configuration (PST-NW-VPN): - Setup-PST-L2TP-VPN.ps1: Automated L2TP/IPsec setup with split-tunnel and DNS - Connect-PST-VPN.ps1: Connection helper with PPP adapter detection, DNS (192.168.0.2), and route config (192.168.0.0/24) - Connect-PST-VPN-Standalone.ps1: Self-contained connection script for remote deployment - Fix-PST-VPN-Auth.ps1: Authentication troubleshooting for CHAP/MSChapv2 - Diagnose-VPN-Interface.ps1: Comprehensive VPN interface and routing diagnostic - Quick-Test-VPN.ps1: Fast connectivity verification (DNS/router/routes) - Add-PST-VPN-Route-Manual.ps1: Manual route configuration helper - vpn-connect.bat, vpn-disconnect.bat: Simple batch file shortcuts - OpenVPN config files (Windows-compatible, abandoned for L2TP) Key VPN Implementation Details: - L2TP creates PPP adapter with connection name as interface description - UniFi auto-configures DNS (192.168.0.2) but requires manual route to 192.168.0.0/24 - Split-tunnel enabled (only remote traffic through VPN) - All-user connection for pre-login auto-connect via scheduled task - Authentication: CHAP + MSChapv2 for UniFi compatibility Agent Documentation: - AGENT_QUICK_REFERENCE.md: Quick reference for all specialized agents - documentation-squire.md: Documentation and task management specialist agent - Updated all agent markdown files with standardized formatting Project Organization: - Moved conversation logs to dedicated directories (guru-connect-conversation-logs, guru-rmm-conversation-logs) - Cleaned up old session JSONL files from projects/msp-tools/ - Added guru-connect infrastructure (agent, dashboard, proto, scripts, .gitea workflows) - Added guru-rmm server components and deployment configs Technical Notes: - VPN IP pool: 192.168.4.x (client gets 192.168.4.6) - Remote network: 192.168.0.0/24 (router at 192.168.0.10) - PSK: rrClvnmUeXEFo90Ol+z7tfsAZHeSK6w7 - Credentials: pst-admin / 24Hearts$ Files: 15 VPN scripts, 2 agent docs, conversation log reorganization, guru-connect/guru-rmm infrastructure additions Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
35 lines
1.5 KiB
SQL
35 lines
1.5 KiB
SQL
-- Extended metrics and agent state
|
|
-- Adds columns for uptime, user info, IPs, and network state storage
|
|
|
|
-- Add extended columns to metrics table
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS uptime_seconds BIGINT;
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS boot_time BIGINT;
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS logged_in_user VARCHAR(255);
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS user_idle_seconds BIGINT;
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS public_ip VARCHAR(45); -- Supports IPv6
|
|
|
|
-- Agent state table for current/latest agent information
|
|
-- This stores the latest snapshot of extended agent info (not time-series)
|
|
CREATE TABLE IF NOT EXISTS agent_state (
|
|
agent_id UUID PRIMARY KEY REFERENCES agents(id) ON DELETE CASCADE,
|
|
-- Network state
|
|
network_interfaces JSONB,
|
|
network_state_hash VARCHAR(32),
|
|
-- Latest extended metrics (cached for quick access)
|
|
uptime_seconds BIGINT,
|
|
boot_time BIGINT,
|
|
logged_in_user VARCHAR(255),
|
|
user_idle_seconds BIGINT,
|
|
public_ip VARCHAR(45),
|
|
-- Timestamps
|
|
network_updated_at TIMESTAMPTZ,
|
|
metrics_updated_at TIMESTAMPTZ DEFAULT NOW()
|
|
);
|
|
|
|
-- Index for finding agents by public IP (useful for diagnostics)
|
|
CREATE INDEX IF NOT EXISTS idx_agent_state_public_ip ON agent_state(public_ip);
|
|
|
|
-- Add memory_total_bytes and disk_total_bytes to metrics for completeness
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS memory_total_bytes BIGINT;
|
|
ALTER TABLE metrics ADD COLUMN IF NOT EXISTS disk_total_bytes BIGINT;
|