Cannot boot... BOOTP "no address configured" log spam in external DHCP

Hello!

Happy user of a few Mikrotik switches - all running SwOS. Never had an issue in the past!

New CRS309-1G-8S-IN arrived yesterday.

  • First boot, went into RouterOS, Accessed UI via 192.168.88.1 as expected.
  • Logged in with password sticker on the back
  • Changed to a new admin password
  • Set up SNMP
  • Add static reservation and hostname to external DHCP server
  • Went to firmware upgrade in RouterOS. Saw there was a new one available and clicked "upgrade and restart" or the equivalent.

Then I was able to access the WebUI on the expected hostname. But when I tried to log in, neither the new password or the original (from the sticker on the device) worked.

Then it seemed to reboot and I noticed it was back on the original 192.168.88.1 address, but only for 20 seconds or so.

Then I tried power-cycling and waiting a few more times...

I tried the "hold the reset button in while powering on an release after a few seconds" thing.

Where am I now?

When I power on the device, I get nothing on the reserved IP or the factory default IP. I do see my DHCP server logs spammed with logs like:

2026-08-12 09:45:21.666 BOOTP(eth0) d0:ea:11:f6:90:02 no address configured

Hundreds of entries.

Another observation, the device makes a little noise every few minutes - maybe it's rebooting? Hard to describe the noise.

So, it's trying to netboot, but I don't have a netboot server set up.

How can I just "reset" to factory defaults again? Is this Netboot / BOOTP loop going to continue until I can give it a netinstall software package to use?

I will keep trying but wondered if there was an obvious mistake I have made here.

Thank you in advance

I am currently using Netinstall and it seems to be working...! Woohoo!

OK. Still had the same issues after updates.

I was able to connect with WinBox and saw the IP was hard-set to 0.0.0.0. Weird.

So, I changed that to DHCP, waited...waited... Then after 10min I power-cycled the switch and now we're all good.

Leaving all of this here in case it helps anyone else!

Good to now :slightly_smiling_face:, though "strange" (it is rather common that a device is set to 0.0.0.0 for some reasons, but usually as soon as the DHCP client is reset/enabled it gets an IP address from DHCP server immediately, in a matter of a few seconds at most).