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>
43 lines
894 B
TOML
43 lines
894 B
TOML
# GuruRMM Agent Configuration
|
|
# Client: Glaztech Industries
|
|
# Site: SLC - Salt Lake City
|
|
# Site Code: DARK-GROVE-7839
|
|
|
|
[server]
|
|
# WebSocket URL for the GuruRMM server
|
|
url = "wss://rmm-api.azcomputerguru.com/ws"
|
|
|
|
# API key for this site
|
|
api_key = "grmm_Qw64eawPBjnMdwN5UmDGWoPlqwvjM7lI"
|
|
|
|
[metrics]
|
|
# Interval between metrics reports (in seconds)
|
|
interval_seconds = 60
|
|
|
|
# Enable/disable specific metric types
|
|
collect_cpu = true
|
|
collect_memory = true
|
|
collect_disk = true
|
|
collect_network = true
|
|
|
|
[watchdog]
|
|
# Enable service/process monitoring
|
|
enabled = true
|
|
|
|
# Interval between watchdog checks (in seconds)
|
|
check_interval_seconds = 30
|
|
|
|
# Datto RMM Agent Service
|
|
[[watchdog.services]]
|
|
name = "CagService"
|
|
action = "restart"
|
|
max_restarts = 3
|
|
restart_cooldown_seconds = 60
|
|
|
|
# Syncro Agent Service
|
|
[[watchdog.services]]
|
|
name = "Syncro"
|
|
action = "restart"
|
|
max_restarts = 3
|
|
restart_cooldown_seconds = 60
|