One of the "problems" with the dhcplb project is that it's difficult to contribute it to it if you are not in that DC environment.
I have worked on setting up a virtual lab using VMs, it has been tested on my OSX laptop using vagrant and chef-solo cookbooks to set up the following:
Ndhcpserver VMs: N VMs running ISC dhcpd (both v4 and v6) configured with a subnet in the private network space. You can start as many as you want by changing the variable on top of the Vagrantfile.
dhcplb: a VM running the dhcplb itself, configured to foward traffic to the above;
dhcprelay: a VM running ISC dhcrelay, it intercepts broadcast/multicast traffic from the client below and relays traffic to the above, it simulates a top of rack switch relay in the DC;
dhcpclient: a VM you can use to run dhclient, or perfdhcp manually to test things. It's DISCOVER/SOLICIT messages will be picked up by the dhcprelay instance
One of the "problems" with the
dhcplb
project is that it's difficult to contribute it to it if you are not in that DC environment.I have worked on setting up a virtual lab using VMs, it has been tested on my OSX laptop using
vagrant
andchef-solo
cookbooks to set up the following:dhcpserver
VMs: N VMs running ISCdhcpd
(both v4 and v6) configured with a subnet in the private network space. You can start as many as you want by changing the variable on top of theVagrantfile
.dhcplb
: a VM running thedhcplb
itself, configured to foward traffic to the above;dhcprelay
: a VM running ISCdhcrelay
, it intercepts broadcast/multicast traffic from the client below and relays traffic to the above, it simulates a top of rack switch relay in the DC;dhcpclient
: a VM you can use to rundhclient
, orperfdhcp
manually to test things. It's DISCOVER/SOLICIT messages will be picked up by thedhcprelay
instancemore information in the
README.md
file