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>
41 lines
1.1 KiB
Rust
41 lines
1.1 KiB
Rust
//! Watchdog module for service/process monitoring
|
|
//!
|
|
//! Monitors configured services and processes, alerting and optionally
|
|
//! restarting them when they stop.
|
|
//!
|
|
//! This module will be implemented in Phase 3.
|
|
|
|
// Platform-specific implementations will go here:
|
|
// - windows.rs: Windows service monitoring via SCM
|
|
// - linux.rs: Systemd service monitoring
|
|
// - macos.rs: Launchd service monitoring
|
|
|
|
use serde::{Deserialize, Serialize};
|
|
|
|
/// Watchdog status for a single service/process
|
|
#[derive(Debug, Clone, Serialize, Deserialize)]
|
|
pub struct WatchdogStatus {
|
|
pub name: String,
|
|
pub running: bool,
|
|
pub restart_count: u32,
|
|
pub last_checked: chrono::DateTime<chrono::Utc>,
|
|
}
|
|
|
|
/// Placeholder for the watchdog manager
|
|
/// Will be implemented in Phase 3
|
|
pub struct WatchdogManager {
|
|
// Will contain the watchdog configuration and state
|
|
}
|
|
|
|
impl WatchdogManager {
|
|
pub fn new(_config: &crate::config::WatchdogConfig) -> Self {
|
|
Self {}
|
|
}
|
|
|
|
/// Check all watched services/processes
|
|
pub async fn check_all(&self) -> Vec<WatchdogStatus> {
|
|
// Placeholder - will be implemented in Phase 3
|
|
Vec::new()
|
|
}
|
|
}
|