Joined: 22 Aug 2009 Posts: 282 Location: New York State
Posted: Sat Sep 07, 2019 15:13 Post subject:
It hasn't re-occurred or I would of responded. or maybe I should of said, I couldn't of responded. Not that I want it to, but I'm almost clueless on how to troubleshoot, especially when it's not re-occurring.
(Chrome-dome, FF & Opera GUI's are carbon copies of one another AFAIC ; worthless. It's too bad Opera Classic V12.18 couldn't of been update retaining the same GUI features. It had just about everything.)
Posted: Sat Feb 08, 2020 14:10 Post subject: DHCP Enabled - Stopped
I just wanted to share what caused my problem with the DHCP server being "Enabled - Stopped". I had put a special character in one of the hostnames under Services / Static Leases. The only special character that is allowed in a hostname is a "-", and I didn't know better. You can also generate this problem with an invalid character in the MAC address. There doesn't appear to be any error-checking of inputs for static leases (not a complaint, just an observation).
I had the same "ënabled-stopped" issue, caused in this case by entering an "O" instead of "0" in one of the mac addresses under Services (ie an invalid character)
I didn't see a more recent topic about this DHCP Enabled - Stopped... so I thought I'd add my most recent encounter with this here.
I'd had a router set up with DD-WRT for years, but decided to re-deploy it and put a newer ver. of DD-WRT on it while I was doing so.
I'd had the router using DHCP issuing IPs from 192.168.0.100 upwards. Worked fine, but I failed to remember that I had limited the max # of DHCP clients too. After flashing the new ver. of DD-WRT, and clearing the nvram settings, it was defaulting to 190 max # of DHCP clients but I again set DHCP issuing IPs from 192.168.0.100 upwards.
192.168.0.100 + 190 = 192.168.0.290, out of subnet range that only goes 0 to 255, so invalid and caused DHCP Enabled - Stopped.
Joined: 18 Mar 2014 Posts: 13879 Location: Netherlands
Posted: Mon Nov 04, 2024 14:52 Post subject:
mono wrote:
Per Yngve Berg wrote:
You should start at 128 which is a round binary number. The first bit goes from 0 to 1.
Other numbers is 16, 32, 64 and 96.
What benefit is there in that? I've started at 100 for many years w/o issue?
If you want to use e.g. Policy Based Routing it is far easier to work with.
If you start at 64 for 64 clients you can write that as 192.168.0.64/26
See ip calculator: https://cidr.xyz/