Skip to content

Office Network Setup (Router on a Stick)

Project Name: Router A Stick ( ROAS ) Office Network Setup

Document Version: 1.1

Date: December 25, 2025

Author: Rajkumar Neupane

Download YAML

This document details the logical and physical network design for the “Lab One” office environment. The infrastructure supports 12 end-user devices distributed across three departments (HR, Sales, and IT). The network utilizes a Router-on-a-Stick (ROAS) architecture for inter-VLAN routing and a centralized Dnsmasq server for automated IP addressing and name resolution.

Pasted image 20251225031435


The following hardware components are utilized in this implementation:

Table 1: Equipment List

Device TypeQuantityDescriptionRole
Router1Cisco IOSv RouterWAN Gateway, Inter-VLAN Routing (ROAS)
Switch1Cisco IOSv-L2 Managed SwitchAccess Layer, VLAN Segmentation (802.1Q)
Endpoints12Alpine Linux DesktopsEnd-user workstations for HR, Sales, and IT
Server1Dnsmasq Docker ContainerDHCP and DNS Services (Hosted in IT_MGMT)

To ensure security and traffic segmentation, the network is divided into four distinct Virtual LANs (VLANs). Traffic between VLANs is managed by sub-interfaces on the router.

Table 2: VLAN Configuration

VLAN IDNameDepartmentSubnetGateway IP
10HR_DATAHuman Resources192.168.10.0/28192.168.10.1
20SALES_DATASales192.168.10.16/28192.168.10.17
30IT_MGMTIT Support192.168.10.32/28192.168.10.33
99NATIVEManagement192.168.10.48/28192.168.10.49

The managed switch is configured with specific access ports for each department and a Trunk port for the router uplink. Port Security and Spanning-Tree Portfast are enabled to ensure stability and security.

Table 3: Physical Port Mapping

Switch InterfaceVLANDepartmentConnected Device
Et0/2, Et0/3, Et1/0, Et1/110HRDesktops 2, 3, 5, 6
Et0/0, Et0/1, Et1/2, Et1/3, Et2/2, Et2/320SalesDesktops 0, 1, 6*, 7, 10, 11
Et2/0, Et2/130ITDesktops 8, 9
Et3/130ITDnsmasq Server
Et3/0TrunkUplinkRouter1 (Ethernet 0/0)

Pasted image 20251225031229


The network uses a central Dnsmasq server located at 192.168.10.34. It uses Tagging logic to provide unique gateways for each VLAN while sharing a common DNS pool.

Dnsmasq Configuration Snippet:

Bash

# VLAN 10 - HR_Department
dhcp-range=set:vlan10,192.168.10.5,192.168.10.14,255.255.255.240,12h
dhcp-option=tag:vlan10,option:router,192.168.10.1
# VLAN 20 - Sales_Department
dhcp-range=set:vlan20,192.168.10.21,192.168.10.30,255.255.255.240,12h
dhcp-option=tag:vlan20,option:router,192.168.10.17

Pasted image 20251225031053


Successful implementation is verified by the ability of Alpine Linux clients to pull correct IP addresses from the designated subnets. All clients successfully reached the relay agent at 192.168.10.34.

Verification Log (Desktop 0 - Sales):

Bash

inserthostname-here:~$ sudo udhcpc -i eth0
udhcpc: broadcasting select for 192.168.10.21, server 192.168.10.34
udhcpc: lease of 192.168.10.21 obtained from 192.168.10.34

Pasted image 20251225031010

Connectivity is confirmed via ICMP ping tests:

  1. Local Gateway Ping: Clients can ping their respective sub-interfaces (e.g., 192.168.10.1). Pasted image 20251225030705
  2. Inter-VLAN Ping: Verified communication between HR (VLAN 10) and Sales (VLAN 20). Pasted image 20251225030822

The Lab One network successfully demonstrates a secure, tiered office infrastructure. By utilizing a Router-on-a-Stick design and DHCP relaying, the network provides efficient resource management and department isolation while allowing controlled inter-departmental communication.


End of Document