The Hex router assigns IP addresses the wrong way LOL, well from my experience routers assign them from the bottom up, aka .2 then .3 …to .254.
Why does this unit start at .254. I think Mikrotik programmers have a sick sense of humour LOL.
Why not? Is it a problem for DHCP users? Why is it “wrong way”?
Look at DHCP configuration … there is even special setting for assigning IPs in a Top-Down or Bottom-Up manner.
What really?!?! Not that it matters in reality but I’ve always wondered why it was descending. Where is this mystical button?
Awesome Great, thanks BartoszpP.
At first I thought you must be an Aussie, where the toilet flushes in the opposite direction, but after closer inspection…
I should have known, Reverse Polish Notation 
Unfortunately I do not see this setting in my 6.41.3 ??
RPN is just faster 
Found it…
insert-queue-before (bottom | first | name; Default: )
Funny the women (non-polish) in my life have never expressed a desire for speed!
I still can’t find it.
I mean I can find it for manually adding devices but for automatic I don’t see it.
I was mistaken Steve, I cannot find it either (I may have been referring to the linked article he posted) - maybe we are supposed to use the Lease Script area at the bottom of the page???
Seems to be accesible only for static leases … grrrr… I have been sure it was accesible as standard setting.
This is a serious matter, think about people who may have a fear of descending numbers. This needs fixing and fast…
(I’m sure there is an apt it’s in v7 joke response to this).
I have checked both systems – hEX and CCR – and the behavior that is written about is not what I see — both systems are delegating leases incrementally starting at bottom up
following pics show my hEX DHCP server and dynamic address assignment:
You have option “Insert Queue before” set as “FIRST” so you have bootom-up order … strange you have this option where it should be. What is your ROS version?
Currently I am on ROS 6.42rc49 … however I initially configured the hEX starting with ROS 6.41.3 which had the exact same behaviour.shown in my pics.
Miracle ..
EDIT:
You have “Lease Script” in other place than on my screenshot.
Is it WinBox problem with stored sessions?
Im with the spit and Polish guy!
My hex looks like his hex, lease script area is what I see and it assigns numbers starting at .254 LOL.
I think this insert-queue-before option has NOTHING to do with the sequence of address assignment.
Unfortunately it is totally undocumented on the WiKi. But I think it is related to queues.
BTW, this behaviour is “standard” on the ISC DHCP server under Linux in some versions. At some point
it was introduced, lots of comments about it were ignored, but later it was reverted to starting from bottom again.
Likely RouterOS still uses a version before that.
It is not really assigning top-down anyway, it appears that way when you use a /24 and have only a couple
of assigned addresses. When you use a larger subnet (e.g. /22) and populate it entirely, you will see that
it sort of randomly gets addresses from a couple of different sub-ranges in that range.
I think there is some hashing and the addresses are assigned in hash sequence or reverse hash sequence.
Yes looks like some GUI changes from 6.41.3 to the rc …
So I’m not going mad then? This is my CHR on 6.41.3. I have 3 DHCP servers all running and none of them have this option for IP assignment as per the previous poster. Must be an “RC” thing. Probably a good thing as I’m waiting for 6.42 to go current anyway to get the vmware-tools functionality.
Steve, your madness is from different sources, perhaps tainted beef or perhaps a smart bug in Mikrotik firmware has made the leap from x’s and o’s, to human chemistry! (at least you would be famous )