Upgraded my router to a Asus RT-BE88U (old one ASUS RT-AC68U)

18d (edited) • Hardware

What an improvement 😁

Why the Asus RT-BE88U is my Ultimate Choice and upgrade for my Homelab and Fiber Future

The Asus RT-BE88U (WiFi 7) is uniquely positioned to handle both the extreme speeds my upcoming fiber connection and the complex internal traffic of a homelab user. It serves as the perfect high-bandwidth foundation for my environment.

Merlin firmware

2. The 10Gbps SFP+ & Multi-Gigabit Backbone

3. 10 GB to my Qnap QSW-M804-4C

The dedicated 10Gbps SFP+ port is a game-changer for any Proxmox or NAS user. By using a direct optical or DAC (Direct Attach Copper) connection to my server, I achieve:

Zero-Latency Internal Transfers: Move huge VM images, backups, and 4K media at full 10Gbps speeds.
Future-Proofing: It enables a complete high-speed path from my ISP’s fiber modem, through the router, directly into my server infrastructure.
Expanded Connectivity: Combined with an additional 10Gbps WAN/LAN port and four 2.5Gbps ports, I have plenty of high-speed lanes for all my wired nodes.

2. Advanced VLAN Segmentation & Security

Professional VLAN (Virtual LAN) management allows me to organize my network like a homelab data center:

Network Isolation: Easily separate my IoT devices and smart TV from my main lab environment. This ensures that media devices stay in their own segment while still accessing my Pi-hole/Unbound setup.

Optimized Traffic: VLANs reduce "broadcast noise," ensuring that intensive lab tasks don't interfere with the stability of my daily internet usage or streaming services.

3. WiFi 7 and Multi-Link Operation (MLO)

With my upcoming fiber connection, MLO ensures my wireless network finally matches your wired speed. By allowing devices to connect to multiple bands (2.4GHz, 5GHz, and 6GHz) simultaneously, MLO provides:

Wire-like Stability: If one band encounters interference, traffic seamlessly continues on another, eliminating buffering.
Extreme Throughput: Aggregated bandwidth allows WiFi 7 devices to reach multi-gigabit speeds wirelessly, perfect for high-speed fiber lines.

4. Robust Processing for Pi-hole & DNS

Running a setup with two Pi-hole and Unbound requires significant CPU power to prevent latency spikes. The RT-BE88U’s powerful quad-core processor ensures rapid DNS resolution and smooth traffic management, even when my homelab is under heavy load.

Optimized Core Infrastructure: 10Gbps Integration with QNAP Switching

The RT-BE88U integrates perfectly into a high-performance core network. By connecting the router’s 10Gbps port to a QNAP QSW-M804-4C managed switch, the setup achieves a homelab-grade topology:

10Gbps Backbone: The link between the Asus router and the QNAP switch ensures that my upcoming fiber internet speeds are distributed at full capacity across your entire server stack.
DAC-Powered Server Cluster: Connecting both Proxmox nodes via DAC (Direct Attach Copper) cables to the QNAP switch eliminates the latency and heat associated with traditional RJ45 copper at 10Gbps. This creates a high-speed, low-latency "east-west" traffic lane for cluster communication and storage.
VLAN Consistency: With the QNAP's L2 management and the Asus router's VLAN support, I can maintain consistent network tagging from the wireless client all the way to the virtual machine, ensuring seamless security and traffic shaping.

Pi-hole v6 Preparation

I activated the v6 API on both Pi-holes (app_sudo mode).

I created a specific App Token (API password) on both servers so that external tools can safely make changes.

In the Proxmox LXC settings, I disabled the Firewall on the network cards to enable communication between the servers.

2. Nebula Sync (Synchronization)

I set up a Nebula Sync container (in Docker with network_mode: host).

This tool communicates with my Pi-holes via the domain names (https://domainame) and the tokens.

Result: Every 15 minutes, all settings (Local DNS records, blocklists, groups) are copied from your Primary (150) to my Replica (144). Therefore, I only need to make changes in one place. 3. Keepalived (Failover / Virtual IP)

The Keepalived tool was installed on both Pi-hole LXCs.

A "Virtual IP" has been created: 192.168.11.250.(example)

Result: Server 150 is the 'Master' and holds onto this IP address. If server 150 fails (e.g. during a Proxmox restart), server 144 takes over this IP within a second. My devices will not notice this.

4. Network & Proxy Integration

Router: In the DHCP settings, I now have 192.168.11.250 listed as the only DNS server. All my devices now communicate with this "floating" IP.

Nginx Proxy Manager (NPM): My domain names (pihole.domainname) now also point to the .250. As a result, I always automatically land on the web interface of the Pi-hole that is currently active.

Why I didn't opt for a 19-inch solution? Well, I love my setup the way it is now.

1 comment