badguardhome/internal/dhcpd
Eugene Burkov 5a50efadb2 Pull request: 2509 type-safety vol.1
Merge in DNS/adguard-home from 2509-type-safety to master

Updates #2509.

Squashed commit of the following:

commit 535968eb7de3a9e0817ddb57bc2320e5c5a55086
Author: Eugene Burkov <e.burkov@adguard.com>
Date:   Wed Jan 20 15:06:16 2021 +0300

    dhcpd: fix comments

commit dc79b80381fe7a8ecec6f9659fd23710c9229f59
Author: Eugene Burkov <e.burkov@adguard.com>
Date:   Wed Jan 20 14:08:10 2021 +0300

    all: improve docs

commit 156ebf6c9bad95f82cd121f019f3b59b77b18ba6
Author: Eugene Burkov <e.burkov@adguard.com>
Date:   Tue Jan 19 17:08:15 2021 +0300

    all: improve JSON encoding and decoding
2021-01-20 15:59:24 +03:00
..
nclient4 Pull request: all: fix lint and naming issues vol. 2 2020-12-07 15:38:05 +03:00
checkother_windows.go Pull request: all: fix lint and naming issues vol. 2 2020-12-07 15:38:05 +03:00
checkother.go Pull request: all: fix lint and naming issues vol. 2 2020-12-07 15:38:05 +03:00
db.go Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00
dhcpd_test.go Pull request: 2508 ip conversion vol.1 2021-01-13 16:56:05 +03:00
dhcpd.go Pull request: 2509 type-safety vol.1 2021-01-20 15:59:24 +03:00
dhcphttp_test.go Pull request: return 501 when we don't support features 2020-11-16 19:01:12 +03:00
dhcphttp.go Pull request: 2509 type-safety vol.1 2021-01-20 15:59:24 +03:00
helpers.go Pull request: 2508 ip conversion vol.1 2021-01-13 16:56:05 +03:00
os_windows.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
README.md Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
routeradv_test.go Pull request: all: fix lint and naming issues vol. 2 2020-12-07 15:38:05 +03:00
routeradv.go Pull request: all: fix lint and naming issues vol. 2 2020-12-07 15:38:05 +03:00
server.go Pull request: 2509 type-safety vol.1 2021-01-20 15:59:24 +03:00
v4_test.go Pull request: 2508 ip conversion vol.1 2021-01-13 16:56:05 +03:00
v4.go Pull request: 2509 type-safety vol.1 2021-01-20 15:59:24 +03:00
v6_test.go Pull request: 2508 ip conversion vol.1 2021-01-13 16:56:05 +03:00
v6.go Pull request: 2509 type-safety vol.1 2021-01-20 15:59:24 +03:00
v46_test.go Pull request: dhcpd: wait for interfaces' ip addresses to appear 2020-11-27 14:39:43 +03:00
v46_windows.go Pull request: all: fix lint and naming issues vol. 2 2020-12-07 15:38:05 +03:00
v46.go Pull request: dhcpd: wait for interfaces' ip addresses to appear 2020-11-27 14:39:43 +03:00

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

  1. Install Virtual Box and run the following command to create a Host-Only network:

     $ VBoxManage hostonlyif create
    

    You can check its status by ip a command.

    You can also set up Host-Only network using Virtual Box menu:

     File -> Host Network Manager...
    
  2. Create your virtual machine and set up its network:

     VM Settings -> Network -> Host-only Adapter
    
  3. 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.

  4. To see the current IP address on client OS you can use ip a command on Linux or ipconfig on Windows.

  5. To force the client OS to request an IP from DHCP server again, you can use dhclient on Linux or ipconfig /release on Windows.

Configure server

  1. Edit server configuration file 'AdGuardHome.yaml', for example:

     dhcp:
       enabled: true
       interface_name: vboxnet0
       dhcpv4:
         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
         options: []
       dhcpv6:
         range_start: 2001::1
         lease_duration: 86400
         ra_slaac_only: false
         ra_allow_slaac: false
    
  2. Start the server

     ./AdGuardHome
    

    There should be a message in log which shows that DHCP server is ready:

     [info] DHCP: listening on 0.0.0.0:67