badguardhome/internal/dhcpd
Ainar Garipov 36c7735b85 Pull request: dhcpd: fix interface ipv6 check
Merge in DNS/adguard-home from 2355-dhcpcheck-ipv6 to master

Updates #2335.

Squashed commit of the following:

commit 5ce1cc7bc244ba5dd4a065d47dec8884fa3d45e7
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Wed Nov 25 14:03:24 2020 +0300

    dhcpd: fix loop exit condition

commit 32b4b946bfa30159326dc295fa1a2607b78172af
Author: Ainar Garipov <A.Garipov@AdGuard.COM>
Date:   Wed Nov 25 13:26:50 2020 +0300

    dhcpd: fix interface ipv6 check
2020-11-25 14:26:26 +03:00
..
nclient4 Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00
README.md Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
check_other_dhcp.go Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00
check_other_dhcp_windows.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
db.go Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00
dhcpd.go Pull request: return 501 when we don't support features 2020-11-16 19:01:12 +03:00
dhcpd_test.go Pull request: 2273 clean tests output 2020-11-16 15:52:05 +03:00
dhcphttp.go Pull request: 2305 limit message size 2020-11-23 14:14:08 +03:00
dhcphttp_test.go Pull request: return 501 when we don't support features 2020-11-16 19:01:12 +03:00
helpers.go Pull request: * dhcpd: send secondary dns as well 2020-11-09 19:27:04 +03:00
network_utils.go Pull request: return 501 when we don't support features 2020-11-16 19:01:12 +03:00
network_utils_test.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
os_windows.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
router_adv.go Pull request:* all: remove github.com/joomcode/errorx dependency 2020-11-05 15:20:57 +03:00
router_adv_test.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
server.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
v4.go Pull request: all: update backend tools and dependencies 2020-11-20 13:44:21 +03:00
v4_test.go Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
v6.go Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00
v6_test.go Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00
v46_windows.go Pull request: dhcpd: fix interface ipv6 check 2020-11-25 14:26:26 +03:00

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

  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