Port 68 — DHCP client
UDP well-known
What runs on port 68
The client side of DHCP address assignment.
Security considerations
Local network only; nothing to expose.
Checking whether something is listening
# Linux / macOS — what is bound to the port
sudo lsof -i :68
sudo ss -lntp | grep :68
# Windows
netstat -ano | findstr :68
Get-NetTCPConnection -LocalPort 68
# is it reachable from outside?
nc -zv example.com 68
curl -v telnet://example.com:68
Freeing the port
# find the process, then stop it
sudo lsof -ti :68 | xargs kill # Linux / macOS
netstat -ano | findstr :68 # note the PID, then:
taskkill /PID <pid> /F # Windows
Should this port be open to the internet?
Usually not. Expose it only if a specific external client needs it, and restrict by source address where you can.
Quick reference
| Port | 68 |
| Protocol | UDP |
| Service | DHCP client |
| Range | Well-known (0–1023) — binding requires root on Unix |
Frequently asked questions
What is port 68 used for?
The client side of DHCP address assignment.
Is it safe to open port 68?
Local network only; nothing to expose.
How do I check if port 68 is open?
Locally, sudo lsof -i :68 on macOS or Linux, or netstat -ano | findstr :68 on Windows. From outside, nc -zv host 68 tells you whether anything answers.
Why do I get "address already in use" on port 68?
Another process is bound to it — often a previous run of your own program that did not exit cleanly. Find it with lsof -ti :68 and stop it, or configure your application to use a different port.
Can I change the port this service uses?
Almost always yes, in the service's configuration. Moving off a default port reduces automated scan noise, but it is obfuscation rather than security — a real attacker scans all 65,535.