Blog Post
I'm annoyed. Yes, that's what it is. Annoyed.
Reproducible bug: change DHCP server config by adding a reservation in the assigned range, whether the server is on or not (in Router mode, of course) and you can neither DHCPREQUEST (renew) an address, nor soft-reset the modem. Just how exactly is someone supposed to remotely recover from a situation like that when the DHCP lease on their existing equipment expires and then eventually fails? If it were not for a quick pre-flight spot check, I would not have noticed that the DHCP reservation I'd set up for my MikroTik RB5009 (in DMZ) wasn't working. Thank God I was here to hard reset it, then test DHCP renewals on the new reservation to make sure they always succeeded. One can hope more people will just notice that their DHCP reservations weren't working in time--silly of me not to check, I know--but it's still inexcusable. With software like this, no wonder the Hub gets panned!
And, yes, as soon as I'm out of my (it seems, unbeknownst to me, OFCOM-registered) speed complaint, I'm going straight back into Modem Mode. But I have to be a Router for now so they can speed-test.
But I'm still annoyed. I shouldn't run spot checks just to find that I'm facing disaster. I can't justify setting up a backup connection, but especially when it's local equipment failure. Maybe I need to recalculate, though there's no time now before I leave.