Search Results

Introduction The Topton X2E (Intel N150 variant) is a compact, fanless mini PC designed primarily for use as a firewall, router, or lightweight virtualization host. Built with an industrial-grade aluminum chassis, it combines silent operation with efficie...

Proxmox VE is based on Debian.  The installer will guide you through the setup, allowing you to partition the local disk(s), apply basic system configurations (for example, timezone, language, network) and install all required packages. Installing with the p...

Introduction OPNsense is an open-source, FreeBSD-based firewall and routing platform designed to be both user-friendly and highly customizable. Built on a modular architecture, it offers a rich feature set often found in commercial offerings—including sta...

Introduction Note I have not configured the Network settings on the previous OPNsense installation page. I will configure it separately according to the following addressing plan and topology: Here I am introducing my homelab topology version 1.0, which will...

Introduction This is the initial version of the network topology, specially crafted for testing wireless and studying the CCNA Wireless certification. The network is meant to be future proof (CCNP Wireless is coming in early 2026) and modular. Although built...

Introduction Starting from where we left on the previous page, where we configured the Proxmox network interfaces, we will now configure the interfaces on the OPNsense VM. First, I will configure the WAN interface and the PPPoE session. Then I will configure...

Introduction Proxmox VE is using the Linux network stack. The configuration can be done either via the GUI, or by manually editing the file /etc/network/interfaces, which contains the whole network configuration. All Proxmox VE tools try hard to keep direct u...

Introduction Per the reference topology, which I have copied below for reference, the TP-LINK switch must be configured so it can pass tagged traffic onto the OPNsense (a trunk link): Not shown is Topton miniPC with Proxmox where WLC is hosted....

Introduction The Cisco Catalyst 9800-CL Cloud Wireless Controller is a virtual wireless controller that is deployed on a Cisco Unified Computing System (UCS) server as a virtual machine (VM) instance on a Linux-based 64-bit guest operating system. The support...

Introduction In the previous page I installed the WLC 9800 VM on a Proxmox node. Now, I will configure it to make an 9120AXI AP usable. Network Configuration First of all, we will take a look at the following topology and considerations: Not ...

Introduction The goal here is to configure Proxmox to have a management interface in the VLAN 10 - MGMT network (10.0.10.0/24). The routing for this VLAN is handled by OPNsense (10.0.10.1). Proxmox Configuration I will assign the Proxmox host the 10.0.10....

Not shown is Topton miniPC with Proxmox where the WLC 9800 is hosted. TP-LINK port 2 = VLAN 20 untagged. TP-LINK port 6 = trunk (tagged). AP and wireless clients get IP from Win2k8 DHCP server hosted in Proxmox. This is the fi...

Topology Task 1: Define the Addressing Plan and Assignments Before beginning with the configuration of the devices themselves, the addressing plan must be properly defined. We will use the following subnets and VLAN numbers: MADRID OFFICE NETWORK...

TopologyTask 1: Cable the Management Server to JRI.EDGEThe Management Server will be given a fixed IP address (172.20.10.10/24) in the MADRID_MGMT VLAN. It will be physically connected to JRI.EDGE on an access port in that VLAN (210). The port on JRI.EDGE will...

Topology Task 1: JRI.WLC.01 Bootup, Factory Reset First task is to bring the JRI.WLC.01 5508 WLC up and have it factory reset. The controller bootloader (ppcboot) must be accessed by pressing Esc key during the boot process on the WLC. We are prompted to...

TopologyTask 1: Using the Controller InterfaceUsing the Controller GUIA browser-based GUI is built into each controller. It allows up to five users to simultaneously browse into the controller HTTP or HTTPS.To view the Main Dashboard, JavaScript must be enable...

Topology Task 1: CAPWAP Exploration Cisco lightweight access points use the IETF standard Control and Provisioning of Wireless Access Points Protocol (CAPWAP) to communicate with the controller and other lightweight access points on the network. CAPWAP,...

Topology Task 1: JRI.WLC.02 Bootup, Factory Reset We have already setup the JRI.WLC.01 (which will be the main WLC for this lab). Now I want to initialize and setup what will become the secondary WLC, JRI.WLC.02.  As in Lab 2-1, first task is to bring t...

Topology Task 1: Explain Link Aggregation Link aggregation (LAG) is a partial implementation of the 802.3ad port aggregation standard. It bundles all of the controller’s distribution system ports into a single 802.3ad port channel. This reduces the numbe...

Topology Task 1: The Need for Upgrading JRI.WLC.02 This page will show the upgrade process for an AireOS WLC in version 8.5. The WLC to be upgraded in the topology is the JRI.WLC.02 which we just setup in the previous lab (Lab 4-2).  To add some context...