Jump to content

PfSense Training Project Tracker

From MediawikiCIT
Revision as of 10:14, 23 April 2026 by Justinaquino (talk | contribs) (Update Phase 1: Resource analysis completed (R.1-R.6), add AI evaluation pipeline tasks, update status dashboard)

Project Tracker for Comfac's pfSense Practical Training System implementation. This page tracks all tasks from material conversion to infrastructure deployment and course delivery.

Phase 0: Material Conversion (FUND001 → Wiki)

Convert all Netgate FUND001 training PDFs into CITWiki pages with detailed summaries. Each wiki page should include: learning objectives, key concepts, step-by-step lab instructions adapted for virtual environment, and troubleshooting tips.

Slide Decks

Labs

Comfac Original Content

Phase 1: Infrastructure Setup

Build the virtual training environment on Comfac's 200-core / 1TB RAM machine.

Resource Analysis (Completed)

  • [x] R.1 Compare Pure Linux (FOSS) vs Windows stacks -> Networking PfSense Index#Resource Estimates Per Student
  • [x] R.2 Calculate 20% server utilization targets -> 13 students (Linux), 6 students (Windows)
  • [x] R.3 Analyze container-based alternatives -> LXC for Linux routers; KVM still required for pfSense
  • [x] R.4 Define exercise-limited deployment model -> Right-size per lab; 0-4 vCPUs per student
  • [x] R.5 Specify smaller server options for 10 students -> Dell R630 (Linux) / R740 (Windows)
  • [x] R.6 Design AI evaluation pipeline -> Qwen 3.5 Coder 9GB + DeepSeek + OpenCode for automated readiness

Host Preparation

  • [ ] A.1 Install Ubuntu Server LTS on 200-core host
  • [ ] A.2 Configure KVM/libvirt with storage pools (NVMe for images, SSD for ephemeral clones)
  • [ ] A.3 Set up network bridges: br-mgmt, br-lan, br-wan, br-dmz, br-internet
  • [ ] A.4 Configure VLANs for student isolation (one VLAN per student or per lab)
  • [ ] A.5 Install and configure Ansible controller (host or container)

Base Images

  • [ ] B.1 Download pfSense CE ISO and create qcow2 golden image (1 vCPU, 512 MB RAM, 4 GB disk - microVM)
  • [ ] B.2 Create Alpine Linux LXC golden image (0.5 vCPU, 256 MB RAM, 1 GB disk)
  • [ ] B.3 Create Debian XFCE LXC golden image for NoVNC client (0.5 vCPU, 256 MB RAM, 2 GB disk)
  • [ ] B.4 Create Ubuntu Server LXC golden image (0.5 vCPU, 256 MB RAM, 1 GB disk)
  • [ ] B.5 Create "Internet Router" LXC golden image (0.5 vCPU, 128 MB RAM, 0.5 GB disk)
  • [ ] B.6 Test each golden image boots and functions correctly

Automation

  • [ ] C.1 Write Ansible playbook: lab1-student-env.yml (1 pfSense microVM + 1 LXC client)
  • [ ] C.2 Write Ansible playbook: lab2-student-env.yml (1 pfSense + 1 client + 1 server LXC)
  • [ ] C.3 Write Ansible playbook: lab3-student-env.yml (1 pfSense + 1 server + internet router LXC)
  • [ ] C.4 Write Ansible playbook: lab4-student-env.yml (2 pfSense + 2 clients + 1 server)
  • [ ] C.5 Write Ansible playbooks for Labs 5-10 (VPNs, Multi-WAN, Shaping, HA)
  • [ ] C.6 Write Ansible playbook: cleanup-student-env.yml (destroy VMs/LXCs, free resources)
  • [ ] C.7 Write Ansible playbook: reset-student-env.yml (revert to snapshot/linked clone base)
  • [ ] C.8 Test all playbooks end-to-end with a single student ID

NoVNC Portal

  • [ ] D.1 Evaluate Kimchi vs Apache Guacamole vs custom NoVNC proxy
  • [ ] D.2 Install and configure chosen NoVNC solution
  • [ ] D.3 Integrate NoVNC with student authentication (LDAP, local wiki accounts, or simple token-based)
  • [ ] D.4 Build student dashboard: list of phases/labs, "Launch Lab" button, countdown timer
  • [ ] D.5 Test 5 concurrent NoVNC sessions for stability
  • [ ] D.6 Test 20 concurrent NoVNC sessions for performance

AI Evaluation Pipeline

  • [ ] E.1 Deploy Qwen 3.5 Instruct Coder 9GB on GPU box or 200-core host
  • [ ] E.2 Build pytest + Selenium test suite for pfSense GUI validation
  • [ ] E.3 Build SSH-based health check suite for VM/LXC connectivity
  • [ ] E.4 Integrate DeepSeek or OpenCode for playbook syntax validation
  • [ ] E.5 Create readiness dashboard (pass/fail per lab, resource usage graphs)
  • [ ] E.6 Schedule automated nightly tests of all lab environments


Phase 2: Curriculum Development

Design the student-facing training program.

Introduction Course (Most Common Use Case)

  • [x] E.1 Define "Setting Up a Firewall for Yourself" scope: home office / small business
  • [x] E.2 Write Module 0: Why You Need a Firewall (threats, NAT basics, basic topology)
  • [x] E.3 Write Module 1: Install pfSense on Old PC or VM (hardware requirements, USB install, first boot wizard)
  • [x] E.4 Write Module 2: Basic WAN + LAN Setup (DHCP, DNS, first internet connection)
  • [x] E.5 Write Module 3: Essential Firewall Rules (block incoming, allow outgoing, ICMP)
  • [x] E.6 Write Module 4: Port Forwarding for Common Services (game server, camera, NAS)
  • [x] E.7 Write Module 5: VPN for Remote Access (WireGuard road warrior setup)
  • [x] E.8 Write Module 6: Backup and Updates (config.xml backup, update schedule)
  • [x] E.9 Create hands-on lab for Introduction Course (single pfSense + 1 client VM)
  • [ ] E.10 Record or source video walkthroughs for each module

Full FUND001 Adaptation

  • [x] F.1 Map each SEG slide deck to a wiki training page with summary + key takeaways
  • [x] F.2 Adapt Netgate labs from physical/virtualbox environment to KVM/Ansible environment
  • [ ] F.3 Update IP addressing schema for Comfac virtual lab (avoid conflicts with production)
  • [ ] F.4 Write pre-lab briefing pages (what you'll learn, expected outcomes)
  • [ ] F.5 Write post-lab review pages (common mistakes, verification steps, "show me" checklist)
  • [ ] F.6 Create quiz questions for each phase (5–10 questions, auto-graded if possible)

Phase 3: Pilot & Refinement

Run the training with a small group before full rollout.

Internal Pilot

  • [ ] G.1 Recruit 3–5 internal Comfac IT staff as pilot students
  • [ ] G.2 Run Phase 1 (Foundations) with pilot group — collect feedback
  • [ ] G.3 Run Phase 2 (NAT & Services) with pilot group — collect feedback
  • [ ] G.4 Run one VPN lab (IPsec or OpenVPN) with pilot group — test resource limits
  • [ ] G.5 Document all bugs, confusion points, and timeouts
  • [ ] G.6 Refine playbooks and wiki pages based on pilot feedback

Resource Tuning

  • [ ] H.1 Measure actual CPU/RAM/disk usage per student during pilot
  • [ ] H.2 Adjust VM specs if over- or under-provisioned
  • [ ] H.3 Test memory overcommit ratios for safe concurrency scaling
  • [ ] H.4 Document maximum safe concurrent student count

Phase 4: Deployment & Operations

Prepare for regular training delivery.

Student Onboarding

  • [ ] I.1 Create student onboarding guide (how to access portal, use NoVNC, reset lab)
  • [ ] I.2 Create instructor guide (how to monitor progress, assist students, grade labs)
  • [ ] I.3 Set up scheduling system (book lab time slots, prevent over-allocation)
  • [ ] I.4 Create completion certificates or badges

Monitoring & Maintenance

  • [ ] J.1 Set up host monitoring (Prometheus/Grafana or simple `libvirt` stats)
  • [ ] J.2 Configure alerts for host resource exhaustion
  • [ ] J.3 Schedule weekly base image updates (pfSense patches, OS updates)
  • [ ] J.4 Document disaster recovery (rebuild host from Ansible, restore golden images)

Quick Status Dashboard

Phase Status % Complete Blockers
Phase 0: Material Conversion 🟢 Done (22/23) 96% Pending: reference PDF, support files, videos
Phase 1: Infrastructure Setup 🟡 In Progress 15% Resource analysis complete; need host access for image builds
Phase 2: Curriculum Development 🟡 In Progress 65% Need video recordings, quizzes, pre/post lab pages
Phase 3: Pilot & Refinement 🔴 Not Started 0% Waiting on Phase 1 + 2
Phase 4: Deployment & Operations 🔴 Not Started 0% Waiting on Phase 3

Resource Summary

Per-student minimum: 6 vCPUs, 6.5 GB RAM, 62 GB disk Per-student full lab: 10 vCPUs, 10.5 GB RAM, 110 GB disk 200-core / 1TB capacity: 20–40 concurrent students (conservative to optimized)

Next Actions (This Week):

  1. Summarize the-pfsense-documentation.pdf into a reference page
  2. Document WindowsTrainingSupportFiles.zip contents
  3. Catalog training video timestamps
  4. Begin Ansible playbook drafting for Lab 1 environment
  5. Evaluate Kimchi vs Guacamole for NoVNC portal
Retrieved from "https://mediawiki.comfac.net/index.php?title=PfSense_Training_Project_Tracker&oldid=250"