Hardware requirements and Raspberry Pi 5 platform
Bill of materials required to deploy an autonomous GADNET hardware node. Open, off-the-shelf components ensure deterministic performance, thermal stability, and minimal electrical power draw.
Compute core: Raspberry Pi 5
Raspberry Pi 5 single-board computer with 4 GB or 8 GB LPDDR4X RAM. Quad-core 64-bit ARM Cortex-A76 (2.4 GHz) with hardware cryptographic extensions (ARMv8-A CE) delivers wire-speed gigabit packet inspection.
Official 27W USB-C power supply
Official 27W USB-C PD power supply (5.1V / 5A). Clean, stable power delivery prevents undervoltage throttling and supplies full USB 3.0 current headroom to high-throughput external network adapters.
Active cooling solution
Official aluminum heatsink with PWM blower fan (Active Cooler) or equivalent active cooling chassis. Maintains SoC and PMIC temperatures under 55°C under continuous gigabit packet load.
High-endurance A2 microSD storage
High-endurance 32 GB (or larger) microSD card rated Application Performance Class 2 (A2). High random IOPS handling protects against flash wear during local bbolt database rotations.
>> Technical details: thermal envelope, power consumption & PCIe bus parameters
The GADNET node on Raspberry Pi 5 draws approximately 2.7W at idle and stays under 8.5W under continuous line-rate packet load. The BCM2712 SoC features dedicated ARMv8-A CE cryptographic instructions. The 16-pin PCIe 2.0 x1 connector (capable of PCIe 3.0) enables high-speed M.2 NVMe storage expansions for enterprise logging.
Network interfaces and gigabit throughput
WAN and LAN interface architecture, dual Wi-Fi radio integration, and deterministic wire-speed throughput with active Zero Trust filtering, anti-fraud correlation, and CAKE SQM queue discipline.
Onboard 1 GbE port (WAN)
Native 1000BASE-T RJ-45 port connected directly to ISP optical ONT or bridged modem. Enforces strict kernel ingress drop policy, completely shielding the node from unsolicited WAN reconnaissance.
USB 3.0 to 1 GbE adapter (LAN)
Supported USB 3.0 Gigabit adapter (Realtek RTL8153 or ASIX AX88179 chipset) providing dedicated wire-speed LAN interface for household workstations, NAS arrays, or managed core switches.
Integrated Wi-Fi 5 & optional Wi-Fi 6
Integrated dual-band 802.11ac (Wi-Fi 5) radio powers bootstrap setup and mobile client zones. Connecting an approved USB or M.2 Wi-Fi 6 dongle unlocks 802.11ax with mandatory WPA3-Personal SAE encryption.
Full 1 Gbps wire-speed throughput
Deterministic packet processing: up to 1 Gbps wire-speed forwarding with active 5-zone micro-segmentation, atomic nftables rule sets, and CAKE SQM queue management to help limit latency increases under load.
>> Technical details: RTL8153 driver tuning, MTU & ethtool offloading configurations
GADNET applies automated ethtool tuning across network interfaces: 'rx-checksumming on', 'tx-checksumming on', 'generic-segmentation-offload on'. Both eth0 (BCM54213PE) and eth1 (USB) run MTU 1500. For PPPoE fiber links, nftables clamps TCP MSS automatically: 'tcp flags syn tcp option maxseg size set rt mtu'.
Software stack and Linux kernel
GADNET uses a minimal Alpine Linux system on ARM64. It runs in RAM, while persistence mechanisms save selected configuration changes.
Hardened Alpine Linux (musl libc)
Lightweight, hardened Linux distribution. musl libc architecture combined with compiler exploit mitigations (Stack Smashing Protection SSP, ASLR, Position Independent Executables PIE) dramatically shrinks attack surface.
Long-term Linux kernel
Stable, officially maintained Linux kernel with long-term support lifecycle. Optimized for BCM2712 hardware, featuring built-in nftables, sch_cake queue discipline, conntrack state tracking, and USB gigabit drivers.
Native nftables L3/L4 firewall engine
Centrally organized 'inet filter' and 'inet nat' tables. Supersedes legacy iptables scripts by compiling filter rules directly into kernel nftables bytecode, executing at wire-speed line rates.
Recursive Unbound resolver
Local recursive resolver sandboxed in chroot with cryptographic DNSSEC validation. Upstream domain lookups encrypted via DNS-over-TLS (port 853) alongside live Response Policy Zones (RPZ) warning feeds.
>> Technical details: /data partition persistence, LBU apkovl & OpenRC init scripts
System boots from read-only squashfs into RAM. Persistent configuration changes commit to /etc/lbu/apkovl.tar.gz via Alpine Local Backup. The bbolt database, mTLS certificates, and rotated audit logs reside on a dedicated /data (ext4) partition. Daemons are supervised by OpenRC init with supervise-daemon restart monitors.
Post-quantum cryptography and certificates
Cryptographic primitives implemented inside the GADNET node. Quantum-resistant hybrid key exchange, stateless SLH-DSA digital signatures, and memory-hard Argon2id password hashing.
Hybrid TLS 1.3 (ML-KEM-768)
Session key exchange utilizing X25519MLKEM768 (NIST FIPS 203 standard). Comprehensive defense against state-level 'harvest now, decrypt later' (HNDL) data retention attacks.
SLH-DSA stateless signatures
SLH-DSA signatures help confirm package integrity and origin. The router checks signatures with trusted keys before accepting supported updates.
Argon2id password hashing
Auxiliary administrator passwords secured with Argon2id (parameters: 64 MB memory cost, 3 iterations, 4 parallelism lanes). Immune to massively parallel offline brute-force attacks on GPU/ASIC clusters.
GPG recovery escrow & BIP-39 seed
Cryptographic disaster recovery mechanism. The 24-word BIP-39 mnemonic seed phrase and asymmetrically encrypted GPG key escrow allow complete node restoration following hardware replacement.
>> Technical details: OpenSSL crypto engine & TLS 1.3 KEM group identifiers
OpenSSL negotiates the supported key-exchange group with the client. Compatible peers can use hybrid post-quantum groups, while other peers negotiate a mutually supported classical group.
Getting started deployment procedure
Prepare the microSD card, connect the device and follow the browser setup wizard. The installation guide explains required accessories and first-setup confirmation.
Step 1: Download & flash image (5 min)
Download the official GADNET image for Raspberry Pi 5. Verify the SHA-256 checksum and SLH-DSA signature, then flash to your microSD card using Raspberry Pi Imager or balenaEtcher.
Step 2: Hardware connections (5 min)
Insert the microSD card into Raspberry Pi 5. Connect the onboard Ethernet port (WAN) to your modem/ONT, plug the USB Ethernet adapter (LAN) into your local switch or PC, and connect the 27W USB-C power supply.
Step 3: Connect to GADNET-Setup (5 min)
Within 60 seconds of boot, the node broadcasts an initial setup Wi-Fi network named 'GADNET-Setup'. Connect via phone or laptop; your browser automatically redirects to the onboarding wizard (RFC 8908 Captive Portal).
Step 4: Create admin credentials (5 min)
Enroll your physical FIDO2 / Passkey token (YubiKey or device biometrics), record the 24-word BIP-39 recovery seed phrase in secure offline storage, and finalize configuration. Your network is immediately secured.
>> Technical details: SHA-256 integrity verification & RFC 8908 captive portal discovery
Image verification command: 'sha256sum -c gadnet-rpi5-v0.1.67.img.xz.sha256'. The on-node Captive Portal intercepts operating system probe queries (captive.apple.com, connectivitycheck.gstatic.com, detectportal.firefox.com) with HTTP 307 Redirect, opening onboarding seamlessly on all client platforms.
Technical specifications summary sheet
Detailed breakdown of technical specifications, physical interfaces, power envelope, and cryptographic standards for GADNET hardware node v0.1.67.