Quantum Fiber Protocol Guide
You're on pure fiber optic — photon-based transmission with near-zero packet loss and sub-8ms latency. Not all protocols benefit equally. Here's exactly which ones to use to fully harness 2,132 Mbps down / 1,072 Mbps up.
On Linux/Mac: set net.core.rmem_max=134217728 and net.core.wmem_max=134217728 in sysctl. Default buffers were designed for 100Mbps links — your 2Gbps fiber needs 20x larger buffers to saturate.
Quantum Fiber supports standard 1500 MTU. For internal LAN, enable 9000 MTU (jumbo frames) on your switch and NIC. Reduces CPU overhead for large transfers significantly.
Enable Google's BBR (Bottleneck Bandwidth and RTT) on Linux: net.ipv4.tcp_congestion_control=bbr. Outperforms CUBIC on high-bandwidth, low-latency fiber links. Especially on long-distance transfers.
OpenVPN: max ~300Mbps due to userspace TLS. WireGuard: 1.5–1.8Gbps on modern CPU due to kernel-space ChaCha20. On 2Gbps fiber, this choice matters enormously.
Use Cloudflare 1.1.1.1 or Google 8.8.8.8 with DNS-over-HTTPS. On fiber, the latency difference is minimal but the privacy gain is real. Set in router firmware, not per-device.
For interactive protocols (SSH, gaming): TCP_NODELAY disables Nagle's algorithm. Forces immediate packet send without buffering. On fiber where bandwidth isn't scarce, this reduces latency noticeably.
Quantum Fiber · 2,132↓ / 1,072↑ Mbps · FTTH Pure Fiber · Protocol Optimization Guide