I'm about to do a full factory reset on my RAX80 and I'd like to reserve a range for assigned IP. What is best, to start the DHCP past the reserved range or have it at the beginning?
For clarification...
Say, start the DCHP at 100-254 and use the IPs below 100 to assign to various devices I wish to have static IP for.
Thank you in advance for any suggestions, along w/any OTHER recommendations in this process. I don't want to EVER do this again and I want more stability. (I know, wishful thinking, LOL)
> [...] What is best, to start the DHCP past the reserved range or have > it at the beginning?
Define "best". What difference would it make?
> Say, start the DCHP at 100-254 and use the IPs below 100 to assign to > various devices I wish to have static IP for.
So long as the ".100" - ".254" range is big enough for your DHCP-pool needs, and the ".2" - ".99" range is big enough for your non-pool needs, that should work. (What could go wrong?)
> I have mine setup with the DHCP scope set below 100 and the reserved > scope starts at 101. [...]
Putting the dividing line among the ".1xx" values is not the way I'd do it. As proposed above, _all_ ".1xx" and ".2xx" values are in the same category. No need for thought. And, in the words of the philosopher Williams, "If you don't think too good, don't think too much."
Well folks! The reason I ask, is because last week or so, I read a post saying that having the assigned IP area at the start (.1-.99) then then the DHCP pool. They talked about how the router starts looking to assign IPS, I don’t recall details & I wish I would’ve kept it. Thank you all for your input! Tomorrow I’ll do it & see what color smoke I get. (Only OLD engineers like me would understand that. )
“ Putting the dividing line among the ".1xx" values is not the way I'd do it. As proposed above, _all_ ".1xx" and ".2xx" values are in the same category.” As I see it, it’s same as you already accepted as ok.
".1" is normally occupied by the router, so you'd use ".2" - ".99". But which comes first between pool and non-pool makes no never-mind. The DHCP server knows where the pool is, and what it's already granted, and the reservations, which is all it needs to know.
No one (with a job) is stupid enough to scan through the ex-pool addresses to find the start of the pool; the start of the pool is well known.
> [...] I don't understand your statement... [...]
Apparently, I misread "below 100" as "100 and below", as if ".100" were the DHCP server Finish IP Address.
But then "the reserved scope starts at 101" makes no sense. If the pool ends at ".99" ("below 100"), then the non-pool range starts at ".100", not ".101". Sorry to add my confusion onto existing confusion.
One reasonable goal is to make it easy to distinguish between in-pool and ex-pool. My (simple) point was that "If it looks like "1xx" or "2xx", then it's <whatever>" is easy. "If it's ".101" or above" is too messy.
Ohhh, you’re referring to the other guy, ok. And yes, of course .1 is the router itself, that goes without saying, just didn’t want to be THAT specific.
