AdGuardHome/internal/dhcpd
2024-10-02 18:24:07 +03:00
..
bitset.go all: sync with master; upd chlog 2023-07-03 14:10:40 +03:00
bitset_test.go Pull request: dhcpd: imp static lease validation 2021-03-18 17:07:13 +03:00
broadcast_bsd.go all: sync with master 2022-09-14 16:36:29 +03:00
broadcast_bsd_test.go all: sync with master 2022-09-14 16:36:29 +03:00
broadcast_others.go all: sync with master 2022-09-14 16:36:29 +03:00
broadcast_others_test.go all: sync with master 2022-09-14 16:36:29 +03:00
config.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
conn_bsd.go all: sync with master; upd chlog 2023-09-07 17:13:48 +03:00
conn_bsd_internal_test.go all: sync with master; upd chlog 2023-06-07 20:04:01 +03:00
conn_linux.go all: sync with master; upd chlog 2023-09-07 17:13:48 +03:00
conn_linux_internal_test.go all: sync with master; upd chlog 2023-06-07 20:04:01 +03:00
conn_unix.go all: sync with master; upd chlog 2023-09-07 17:13:48 +03:00
db.go all: add permcheck, client fix; imp chlog 2024-10-02 18:24:07 +03:00
dhcpd.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
dhcpd_unix_test.go all: sync with master 2024-03-12 18:15:58 +03:00
http_unix.go all: sync with master 2024-03-12 18:15:58 +03:00
http_unix_internal_test.go all: sync with master; upd chlog 2023-10-11 17:31:41 +03:00
http_windows.go all: sync with master; upd chlog 2023-10-11 17:31:41 +03:00
http_windows_test.go all: sync with master 2022-09-14 16:36:29 +03:00
iprange.go all: sync with master; upd chlog 2023-04-12 14:48:42 +03:00
iprange_test.go Pull request: use testutil 2021-10-22 11:58:18 +03:00
migrate.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
migrate_internal_test.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
options_unix.go all: sync with master; upd chlog 2023-03-09 15:39:35 +03:00
options_unix_test.go all: sync with master 2022-11-02 16:18:02 +03:00
README.md all: sync with master; upd chlog 2023-09-07 17:13:48 +03:00
routeradv.go all: sync with master; upd chlog 2023-07-03 14:10:40 +03:00
routeradv_test.go Pull request: dhcpd: do not assume mac addrs of 6 bytes 2021-03-31 12:36:57 +03:00
v4_unix.go all: sync with master 2024-03-12 18:15:58 +03:00
v4_unix_test.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
v6_unix.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
v6_unix_test.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00
v46_windows.go Pull request 2100: v0.107.42-rc 2023-12-07 17:23:00 +03:00

Testing DHCP Server

Contents:

Test setup with Virtual Box

Prerequisites

To set up a test environment for DHCP server you will need:

  • Linux AG Home host machine (Virtual).
  • Virtual Box.
  • Virtual machine (guest OS doesn't matter).

Configure Virtual Box

  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 addresses 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
         local_domain_name: lan
         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 -v
    

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

    [info] DHCP: listening on 0.0.0.0:67
    

Quick test with DHCPTest utility

Prerequisites

Quick test

The DHCP server could be tested for DISCOVER-OFFER packets with in interactive mode.