VLAN-Specific DHCP

Problem

Multi-tenant and multi-VLAN sites need isolated DHCP behavior. A single shared DHCP server list is unsafe and hard to scale when each VLAN has different address pools and relay targets.

How it works

• VLANs are modeled as separate Layer-2 domains on LAN/WAN-facing links.
• DHCP server and relay configuration is generated per VLAN, including subnet scopes and server identifiers.
• Each VLAN can keep its own DHCP server list so clients in one tenant/segment do not leak into another.
• Relay and server processes are driven from platform config so changes apply without ad-hoc manual editing on devices.

What I built / owned

• Designed and deployed VLAN-level DHCP server and relay configuration generation.
• Enabled isolated DHCP server lists per VLAN for multi-tenant environments.
• Improved IP management scalability and segmentation between VLANs/zones.

Impact

Cleaner IP assignment and stronger isolation in multi-tenant networks, with less manual DHCP configuration drift.

Tech

C/C++ · DHCP / dhcpd · VLAN · Linux networking · Config generation