Contents

DHCP Monitor

Broadcast a DHCPDISCOVER on the local segment and list every DHCP server that answers, flagging any that are not on your authorized list.

Sidebar group: Discovery and SNMP · Works offline: no (broadcasts on the local network, only when you click Probe or Monitor) · Needs admin rights: on Linux, permission to bind UDP 68 (see Platform notes); no on macOS and Windows in normal setups

When to use it

Quick start

  1. Pick the Interface on the segment you want to test, or leave Default route.
  2. Enter your known servers in Authorized servers, for example 192.0.2.1, 192.0.2.2. Leave it empty if you only want to see who answers.
  3. Click Probe. The tool sends one DISCOVER and listens for the number of seconds in Probe: listen (s).
  4. Read the verdict banner and the Servers table.
  5. For ongoing checks, click Monitor instead. It sends a new DISCOVER every Monitor: every (s) seconds until you click Stop.
  6. Use Export next to the Servers heading to save the result or add it to a project.

Inputs and options

Field What it means Default / accepted values
Interface The interface to send and listen on. The list shows non-loopback IPv4 interfaces as name (address/prefix). Default route
Authorized servers (optional) IPv4 addresses of legitimate DHCP servers, separated by commas, spaces or new lines. A server is authorized if its server identifier or the packet's source address is on the list. Empty (every server shows as unverified)
Probe: listen (s) How long Probe listens after its single DISCOVER. 5; 1 to 60
Monitor: every (s) Seconds between DISCOVERs in Monitor mode. 30; 5 to 3600
Probe Send one DISCOVER, listen, then stop.
Monitor Send a DISCOVER now and then on the interval, until Stop.

Each DISCOVER uses a new random transaction id and a random, locally administered unicast client MAC, and sets the broadcast flag so servers broadcast their offers back. The tool never sends a REQUEST, so no lease is taken and your own lease is untouched. A server may still hold the offered address briefly, as it would for any DISCOVER.

Reading the results

Status line. Listening on UDP 68 (interface), then DISCOVER #n sent as <client MAC>, xid <id>, and at the end Stopped after N DISCOVERs, M servers seen.

Warnings. Non-fatal problems, such as an interface that could not be bound, or rate-limited replies.

Verdict banner.

Servers table, one row per server identity (option 54, or the source address if absent):

Replies log, newest first, last 300 replies: time, message type (OFFER, ACK or NAK), source address, server, client MAC, transaction id, and For: our probe if the reply matches one of the tool's recent transaction ids, or other client for broadcast replies to other hosts on the segment.

Worked example. With authorized servers 192.0.2.1, a probe on en0 returns:

Status Server Offered Mask Router DNS Lease
authorized 192.0.2.1 192.0.2.150 255.255.255.0 192.0.2.1 192.0.2.53 1d
rogue 192.0.2.254 203.0.113.100 255.255.255.0 192.0.2.254 192.0.2.254 12h

The red banner reads Rogue DHCP server detected: 192.0.2.254.

What the results do and do not tell you

Online activity and privacy

The tool sends DHCPDISCOVER broadcasts to 255.255.255.255:67 on the local segment, and only when you click Probe or Monitor. It listens on UDP 68 only while running and closes the socket on Stop or at the end of a probe. Nothing leaves the local segment unless a DHCP relay forwards the DISCOVER, which is normal relay behavior. Results are not saved unless you export them.

Export and projects

The Export menu (shown once a server answered) offers HTML, PDF, Markdown and plain text, Redacted..., and Add to project. The report lists the interface, authorized servers, probes sent, and for each server: status, replies, offered address, mask, router, DNS, domain, lease (seconds), relay, first and last seen, plus any warnings. The replies log is not included. See Export and redaction.

Platform notes

Troubleshooting

Error "binding UDP 68 needs permission to use ports below 1024..." (Linux). Use one of the two commands in the message.

Error "permission denied binding UDP 68: ...". The OS refused the port. Check local security policy or endpoint software.

Error "UDP 68 is held exclusively by another program, usually the OS DHCP client or a local DHCP server." Close that program, or run the probe from another host.

Error "could not send the DHCPDISCOVER broadcast: ... Check that the interface is up and has an IPv4 address." The interface is down or has no IPv4 address.

Warning "could not bind to : ...; using the default route". The interface pin failed. On Linux this needs CAP_NET_RAW.

Warning "interface not found; using the default route". The interface disappeared since the list was loaded.

Error "invalid IPv4 address '...'". An entry in Authorized servers is not an IPv4 address.

Banner "No DHCP server answered." Check the interface, that the segment has a server or relay, and that a host firewall is not blocking inbound UDP 68.

Error "receive failed repeatedly: ...". 100 receive errors in a row. Check the interface and try again.