PacketFence-VM ghcr.io/hoody424/packetfence-vm:latest https://github.com/hoody424/unraid-templates/pkgs/container/packetfence-vm bridge bash false https://github.com/hoody424/unraid-templates/issues https://www.packetfence.org/ https://github.com/hoody424/unraid-templates/blob/main/packetfence-vm/README.md Installs PacketFence, the open source network access control (NAC) system, as a virtual machine in the Unraid VM tab. PacketFence itself does not run in Docker; this container is only the installer. It downloads the official PacketFence ZEN appliance (about 8 GB, MD5-checked), converts its VMware disk into an Unraid vdisk, creates the VM and starts it. Then the container stops. The VM is a normal Unraid VM: start, stop, edit and back it up in the VM tab. Running the container again never changes an existing VM. Needs: VMs enabled (Settings > VM Manager), 16 GB of free memory and 4 cores for the VM, about 40 GB free in the VM storage during the import (the vdisk is 200 GB thin-provisioned, about 21 GB used). After the start: open the VM's VNC console in the VM tab. The first network card gets its address by DHCP. Console login root / p@ck3tf3nc3 (change it). Then open https://VM-address:1443 and go through the configurator. Network:Management Security: https://raw.githubusercontent.com/hoody424/unraid-templates/main/packetfence-vm/packetfence-vm.xml https://raw.githubusercontent.com/hoody424/unraid-templates/main/packetfence-vm/packetfence-vm.png packetfence nac 802.1x radius network access control vm zen inverse VM Manager enabled (Settings > VM Manager). The VM needs 16 GB of free memory, 4 CPU cores and about 40 GB free in the VM storage. MIT (installer); PacketFence is GPL-2.0 ### 2026-10-11 - Initial release 2026-10-11 PacketFence latest 4 16 br0 en-us yes no /mnt/user/domains/ /mnt/user/isos/ yes raw virtio /var/run/libvirt /var/run/docker.sock /boot/config/plugins/dynamix.vm.manager/templates/images