c5ed6da5bd
Before this patch we couldn't receive incoming DHCP packets. Now we bind() to 0.0.0.0 and set the required network interface using SO_BINDTODEVICE option. As an improvement, we now wait until a reply to our request is received and skip all unknown packets. |
||
|---|---|---|
| .. | ||
| standalone | ||
| check_other_dhcp.go | ||
| db.go | ||
| dhcpd_test.go | ||
| dhcpd.go | ||
| filter_conn.go | ||
| helpers.go | ||
| os_unix.go | ||
| os_windows.go | ||
| README.md | ||
DHCP server
Contents:
Test setup with Virtual Box
To set up a test environment for DHCP server you need:
- Linux host machine
- Virtual Box
- Virtual machine (guest OS doesn't matter)
Configure client
-
Install Virtual Box and run the following command to create a Host-Only network:
$ VBoxManage hostonlyif createYou can check its status by
ip acommand.You can also set up Host-Only network using Virtual Box menu:
File -> Host Network Manager... -
Create your virtual machine and set up its network:
VM Settings -> Network -> Host-only Adapter -
Start your VM, install an OS. Configure your network interface to use DHCP and the OS should ask for a IP address from our DHCP server.
Configure server
-
Edit server configuration file 'AdGuardHome.yaml', for example:
dhcp: enabled: true interface_name: vboxnet0 gateway_ip: 192.168.56.1 subnet_mask: 255.255.255.0 range_start: 192.168.56.2 range_end: 192.168.56.2 lease_duration: 86400 icmp_timeout_msec: 1000 -
Start the server
./AdGuardHomeThere should be a message in log which shows that DHCP server is ready:
[info] DHCP: listening on 0.0.0.0:67