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>
53 lines
1.5 KiB
Rust
53 lines
1.5 KiB
Rust
//! Frame encoding module
|
|
//!
|
|
//! Encodes captured frames for transmission. Supports:
|
|
//! - Raw BGRA + Zstd compression (lowest latency, LAN mode)
|
|
//! - VP9 software encoding (universal fallback)
|
|
//! - H264 hardware encoding (when GPU available)
|
|
|
|
mod raw;
|
|
|
|
pub use raw::RawEncoder;
|
|
|
|
use crate::capture::CapturedFrame;
|
|
use crate::proto::{VideoFrame, RawFrame, DirtyRect as ProtoDirtyRect};
|
|
use anyhow::Result;
|
|
|
|
/// Encoded frame ready for transmission
|
|
#[derive(Debug)]
|
|
pub struct EncodedFrame {
|
|
/// Protobuf video frame message
|
|
pub frame: VideoFrame,
|
|
|
|
/// Size in bytes after encoding
|
|
pub size: usize,
|
|
|
|
/// Whether this is a keyframe (full frame)
|
|
pub is_keyframe: bool,
|
|
}
|
|
|
|
/// Frame encoder trait
|
|
pub trait Encoder: Send {
|
|
/// Encode a captured frame
|
|
fn encode(&mut self, frame: &CapturedFrame) -> Result<EncodedFrame>;
|
|
|
|
/// Request a keyframe on next encode
|
|
fn request_keyframe(&mut self);
|
|
|
|
/// Get encoder name/type
|
|
fn name(&self) -> &str;
|
|
}
|
|
|
|
/// Create an encoder based on configuration
|
|
pub fn create_encoder(codec: &str, quality: u32) -> Result<Box<dyn Encoder>> {
|
|
match codec.to_lowercase().as_str() {
|
|
"raw" | "zstd" => Ok(Box::new(RawEncoder::new(quality)?)),
|
|
// "vp9" => Ok(Box::new(Vp9Encoder::new(quality)?)),
|
|
// "h264" => Ok(Box::new(H264Encoder::new(quality)?)),
|
|
"auto" | _ => {
|
|
// Default to raw for now (best for LAN)
|
|
Ok(Box::new(RawEncoder::new(quality)?))
|
|
}
|
|
}
|
|
}
|