IP / Network Issue

MikroTik router: DHCP clients not receiving IP

Q: Where can I find the MikroTik official documentation?

https://help.mikrotik.com — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

Vendor	MikroTik
Operating system	RouterOS
Category	IP / Network Issue
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need MikroTik Support + RMA.

What this guide covers

Fix DHCP clients not receiving IP on a MikroTik router.

Step-by-step

Check the DHCP pool / scope for free addresses.
Confirm IP helper-address / DHCP relay is configured.
Verify L2 + L3 reachability between client VLAN and DHCP server.
Capture DHCP traffic in the relay path.

CLI / commands

/interface print
/interface ethernet print stats ether1
/system routerboard print

When the issue persists

Open a MikroTik Support case with the tech-support bundle.
Provide the timeline + recent changes.

Frequently asked questions

Will this work on my specific RouterOS version?

The procedure reflects current RouterOS behaviour. Older releases may need minor syntax adjustments, use the CLI help (? or tab-completion) to verify.

Should I open a MikroTik Support case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the MikroTik official documentation?

https://help.mikrotik.com: search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

All MikroTik fix guides → /mikrotik/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

References

MikroTik support portal: https://www.mikrotik.com/support
MikroTik knowledge base: https://help.mikrotik.com
MikroTik security advisories: https://mikrotik.com/download/changelogs
Open a case: https://www.mikrotik.com/support

Reference material, not professional advice. Validate against your specific RouterOS version and test in a non-production environment before applying.

What changed recently?

Fault diagnosis on a MikroTik device goes faster when you map the symptom to a recent change:

Did firmware update in the last 7 days?
Did the network (router, ISP, VPN) change?
Was the device moved physically?
Did paired devices (phone, hub, app) update?
Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

Safety + preconditions

Before any work on a MikroTik device:

Unplug from mains for any internal-access procedure.
Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
Avoid moisture; never apply liquids near vents or connectors.
If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

How to confirm it's actually fixed

On a MikroTik device, the test is rarely "reboot and see". Use this list:

Active reproduction: trigger the original failure path on purpose.
Indirect reproduction: do an activity that would expose the same subsystem.
Status indicator review: every LED / display / app status should be green.
24-hour soak: leave the device under normal load overnight; check the next morning.
Telemetry check: review the device or app's diagnostic log for new error entries.

When to call MikroTik support instead

Escalate if:

The same symptom returns within 24 hours of a clean fix.
You see physical damage (burn marks, swollen battery, cracked PCB).
The device is in warranty and a hardware replacement is the cheaper outcome.
Repair requires specialised tools you don't own (alignment jigs, calibration software).
Following the official path keeps the warranty intact, which matters more than the time spent.

Topology deep dive (Tier-2 WISP / ISP edge perspective)

On the typical small-ISP edge I deal with, the MikroTik router sits between an upstream BSNL or Airtel leased-line / GPON ONT and a Layer-2 distribution switch feeding 6 to 24 OLT or sector ports. The router does NAT (carrier-grade if licensed), DHCP for the customer pool, a single BGP or static default toward the POP, and OSPF area 0 between the MikroTik router and a secondary survivor box in the same rack. MikroTik router: DHCP clients not receiving IP

The interface map I run on most sites looks like this: ether1 is the upstream WAN to Jio/Airtel/BSNL, ether2 is a backup LTE bonded link via a Quectel modem, ether3 to ether9 are the L2 trunks toward the OLT or AP shelves carrying tagged VLANs 100, 200, 300 for residential, SMB, and management respectively. I have learned to start every change with `/system backup save name=pre-change-2026-06-10` because a 2KB backup has saved me three on-site visits in the last year.

What changes the playbook for a small ISP is asymmetry of investment: a tower site might host an INR 18,500 RB4011 with no PSU redundancy, while the NOC has an INR 1.85 lakh CCR2216 with dual PSUs and a fan tray. The fix matrix below assumes you are operating somewhere on that spectrum, not a Mumbai BFSI data center. If your box is the only edge on a 400-customer WISP, you cannot reload it casually at 2pm: the fix sequence here is written for exactly that risk profile.

One more topology note: most Tier-2 ISP edges have no out-of-band console server. We use a 5G USB dongle on the lab laptop and SSH over LTE when the WAN dies. Make sure your /tool romon network is on in advance, otherwise you will be driving to the tower at 3am. I do this with `/tool romon set enabled=yes` on every device before it leaves the bench.

Configuration walkthrough that holds up in production

This is the order I run when bringing a MikroTik router into a working state for the scenario this article covers. Open a console session via a USB-to-RJ45 adapter at 115200 8N1. The CCR series uses RS-232 on the front; the RB series uses a 3.5mm jack with a vendor cable (INR 1,250 from Amazon India, do not buy the unbranded one, the pinout is wrong). MikroTik router: DHCP clients not receiving IP

# 1. Identify what you are working on, do not assume.
/system identity print
/system resource print
/system routerboard print
/system health print

# 2. Save a clean snapshot before anything.
/export file=pre-change-2026-06-10.rsc
/system backup save name=pre-change-2026-06-10

# 3. Inspect the active interface state.
/interface print stats
/interface ethernet print
/interface ethernet monitor [find] once

# 4. Inspect routing state on the survivor path.
/routing ospf neighbor print
/ip route print where active and dst-address=0.0.0.0/0
/ip dhcp-server lease print count-only

# 5. Capture for the support case BEFORE you change anything.
/log print follow-only file=incident-2026-06-10.txt

The line that catches most ISP admins is forgetting step 5. RouterOS has a tiny circular log buffer (by default 100 entries) and the boot-loop scenario will overwrite the evidence in 45 seconds. Either bump it with /system logging action set memory memory-lines=10000 as a permanent change, or pipe to disk while you work.

Once the snapshot is on hand, apply the change from a single CLI session, not WinBox. WinBox commits each field individually and any rollback you do later will be untidy. I have lost an hour to that exact footgun on a CCR1036 in Salem and now I never use WinBox for change windows.

Troubleshooting commands by platform

Even on a MikroTik-only WISP, I often have to compare behaviour against a Cisco or Juniper neighbour upstream, because Airtel and BSNL run mixed-vendor edge gear. MikroTik router: DHCP clients not receiving IP The commands below are the cross-vendor equivalents you will actually type on a 3am bridge call when an upstream NOC engineer is reading from a Cisco runbook.

# RouterOS (MikroTik) on MikroTik router
/interface ethernet monitor [find] once
/system resource print
/system health print
/log print where topics~"critical|error"
/system routerboard print
/system reset-configuration no-defaults=yes skip-backup=yes  # ONLY for recovery

# Cisco IOS equivalent (if peer is a Cisco 4321 or ISR4451)
show interfaces brief
show platform hardware fed switch active fwd-asic resource tcam utilization
show environment all
show logging | include %LINK|%LINEPROTO|%SYS
show version | include uptime

# Juniper Junos equivalent (if peer is an ACX or MX)
show interfaces extensive
show chassis hardware
show chassis environment
show system uptime
show log messages | match alarm

# Huawei VRP equivalent (BSNL / MTNL POP gear)
display interface brief
display device
display environment
display logbuffer
display version | include uptime

# HPE Comware / Aruba CX (sometimes on the LAN side at a school WAN)
display interface brief
display device
display environment
display logbuffer

I keep this matrix in a sticky note on the side of my lab monitor. When a Jio core engineer says "ASIC is dropping" and you only know RouterOS, the translation is /interface ethernet monitor for the optic-level state plus /system routerboard print for the on-board state. Saying that on the bridge buys you ten minutes of credibility you will need later.

India compliance and deployment notes

MikroTik router: DHCP clients not receiving IP A few things that catch out small ISP admins and that almost no global vendor doc covers:

DPDP Act 2023 (MeitY). Customer DHCP logs are personal data under the Digital Personal Data Protection Act. If you are exporting /log print off the MikroTik router for vendor support, redact source IPs and MACs that map to subscriber accounts, or get a signed data-handling clause from the support partner. I template the redaction with a one-line sed pipe and keep the original encrypted on a USB stick that never leaves the office.
TRAI tariff order on bill-shock. If the box fails in a way that drops customer sessions for more than 24 hours, you owe pro-rated credit under TRAI's QoS regulation. Document the start and end of the outage on the MikroTik router via /log print exports, not your memory.
GeM tender pricing for replacements. If you supply a government school WAN or PSU bank branch, the replacement MikroTik router or PSU must come through GeM (Government e-Marketplace). The MikroTik router on GeM was listed around INR 18,500 to INR 24,000 in May 2026 depending on the firmware bundle. Distributor pricing on the open channel is INR 16,400 but you cannot bill it to a GeM-mandated buyer.
BIS certification. Some MikroTik SKUs imported via grey channels do not carry the BIS R-N registration mark. For a BSNL leased-line customer that runs an audit, an unmarked unit can be ordered off-site. Always ask the distributor for the BIS certificate copy and keep it with the AMC paperwork.
AMC pricing reality. A T+1 onsite AMC on a MikroTik router runs INR 4,200 to INR 6,800 per year per box for Tier-2 town coverage in 2026. Carry a 7% buffer for fuel surcharge.

A real deployment I worked through

Around November 2025 a school-WAN ISP in Coimbatore I help out called at 11pm because their CCR went dark during a thunderstorm. The MSEDCL feed had a 11kV transient and the AMC vendor was a six-hour drive away. We brought the box back with a console session and the steps below. The principal still calls me 'router uncle' which is fine I guess. MikroTik router: DHCP clients not receiving IP The site had two MikroTik router units, both bought through a Bengaluru distributor in 2024 for INR 17,200 each on a GeM order, and only one had the active AMC. Customer-facing SLA was 99.5% monthly, so we had about 3 hours 30 minutes of allowable downtime per month, and we had already burned 2 of those on a BSNL fibre cut the week before.

What I did first was take a console snapshot with `/export file=pre-fix.rsc` and `/system backup save name=pre-fix`. Then I confirmed the symptom matched the article, not the wishful version of it. The temptation on a 3am call is to apply the fix you remember, not the fix the box needs. I have made that mistake. The cost was a 4-hour outage and a refund credit of INR 21,400 to the affected residential block.

The fix itself took 24 minutes. Verification took another 35 minutes because I wanted to soak the box under real customer load before I left site, and the Reliance Jio backhaul was still flapping on the upstream side. The follow-up the next morning was the boring but vital bit: I updated the AMC vendor ticket with the MikroTik router serial, the mikrotik router: dhcp clients not receiving ip... and the exact RouterOS version. The vendor closed the ticket within the same business day because the documentation was tight.

Lesson stored: /system backup save first, screenshot the LED panel second, never touch a production MikroTik router without a rollback path, and keep an extra console adapter in the laptop bag because the one in the rack drawer will always be missing.

Extended FAQs from the bridge call

Will this work on the older RouterBoard hardware revision shipped before 2023?

Mostly yes, the CLI verbs are stable across RouterOS 6.x and 7.x. The two gotchas are: (a) /tool romon behaves differently before 7.10 and you may need to bring up a static IPv6 on the management VLAN; (b) some /system health sensor names changed between 6.49 and 7.13. If you are on 6.49.x in a hard-to-reach site, document the sensor names before you upgrade.

How long will the fix take with a junior NOC engineer driving?

Plan for 60 to 90 minutes on the first run, 30 minutes when they have done it twice. The longest single step in our team's run-book is the soak: 20 minutes under real customer load is the minimum before you close the change ticket. A WISP has no second chance to apologise to a residential customer for a wobbly fix.

Do I need a paid MikroTik support contract for the MikroTik router?

MikroTik does not sell tiered support the way Cisco or Juniper do. Community support is the main channel via forum.mikrotik.com. For a 400-customer WISP, I budget INR 12,000 a year for a third-party MTCNA-certified consultant on retainer instead, which buys 8 hours of remote help a month. That has been better value than any vendor TAC I have used elsewhere.

Can I use this procedure on a CHR (Cloud Hosted Router) running on a virtual machine?

The CLI is identical but the hardware-specific commands like /system health print and /system routerboard print will return empty or not-found. Skip those steps; everything else applies. I run a CHR on a small AWS Mumbai t3.small for a customer's secondary site and it has carried 250 Mbps of real traffic without complaint for 14 months.

What if I do not have console access and SSH is dead?

That is the worst case for mikrotik router: dhcp clients not receiving ip. You have three options: (a) MAC-Telnet via WinBox over Layer 2 from a directly-connected laptop, often forgotten and often works; (b) Netinstall from a Windows laptop on the management VLAN with a static IP; (c) ship the box back to a Bengaluru or Pune service center, expect 7 to 10 working days. I have done (a) and (b) more times than I can count; (c) I have done once in five years.

Will the fix survive a power loss?

RouterOS commits config to NVRAM on each change unless you use /system scheduler to defer. After the fix, do a controlled /system reboot at the end of your maintenance window to confirm the box comes back clean. Skipping that step has cost me a 4am site visit because the config was held in RAM only on a CCR1009 with a flaky PSU.