AdGuardHome/internal/dhcpd
2023-03-09 15:39:35 +03:00
..
bitset.go Pull request: dhcpd: imp static lease validation 2021-03-18 17:07:13 +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 all: sync with master; upd chlog 2023-03-09 15:39:35 +03:00
conn_unix.go all: sync with master 2022-11-02 16:18:02 +03:00
conn_unix_test.go all: sync with master 2022-09-14 16:36:29 +03:00
db.go all: sync with master 2022-09-14 16:36:29 +03:00
dhcpd.go all: sync with master; upd chlog 2023-03-09 15:39:35 +03:00
dhcpd_unix_test.go all: sync with master 2022-11-02 16:18:02 +03:00
http_unix.go all: sync with master 2022-11-02 16:18:02 +03:00
http_windows.go all: sync with master 2022-11-02 16:18:02 +03:00
http_windows_test.go all: sync with master 2022-09-14 16:36:29 +03:00
iprange.go all: sync with master 2022-11-02 16:18:02 +03:00
iprange_test.go Pull request: use testutil 2021-10-22 11:58:18 +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
os_windows.go all: sync with master 2022-09-14 16:36:29 +03:00
README.md Pull request: * all: move internal Go packages to internal/ 2020-10-30 13:32:02 +03:00
routeradv.go all: sync with master 2022-09-07 18:03:18 +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; upd chlog 2023-03-09 15:39:35 +03:00
v4_unix_test.go all: sync with master; upd chlog 2023-03-09 15:39:35 +03:00
v6_unix.go all: sync with master; upd chlog 2023-03-09 15:39:35 +03:00
v6_unix_test.go all: sync with master 2022-09-14 16:36:29 +03:00
v46_windows.go all: sync with master; upd chlog 2023-03-09 15:39:35 +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