Posted: Sat May 14, 2022 7:39 Post subject: Why don't al DHCP hosts show up under 'DHCP Clients'
In the status page, I have a computer connected, working, pingable, etc. It has an assigned IP address, everything is working fine, but it doesn't show up under "DHCP Clients".
Also many hostnames are left blank. I've chalked this up to some inherent way DHCP works, but it doesn't make sense to me. Shouldn't by necessity every active client have its IP address and hostname listed? _________________ So you’re a DD-WRT Expert? Figure this out: https://forum.dd-wrt.com/phpBB2/viewtopic.php?p=1168315
I then set static leases with an expiry of 15 minutes for these missing devices, rebooted the devices (NAS boxes), this should have triggered a DHCP request from devices and it did, and even after this, not all devices reliably show, I still had missing devices that didn't show up even after accessing them and sending data/receiving data.
These are all wired devices.
Rebooting dd-wrt and devices (power cycle) still same, not all show up, its a random bag of fun.
The only one that reliably shows up is the first static IP assignment and non expiring lease, which is my main dev machine. Also all wifi devices will show up (non expireing leases), but wired YMMV no matter if lease expires.
Dnsmasq afaik is a test version daemon.info dnsmasq: started, version 2.87test8 cachesize 1500 so this could have some influence on the reliability.
Im running latest 48865, I remember much older builds that always showed all devices without fail, so clearly bugs were introduced upstream, on the project (which is not developed by dd-wrt.
So that clients with DHCP reservation are not shown under "DHCP clients" is already quite a few years (I can't remember that it was ever different!).
and with me it works exactly as I have described it above.
I just have to log in to such a client and restart the network and suddenly the client is displayed again.
Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces
Reconfiguring network interfaces...
No resolv.conf for interface eth0.udhcpc
Sending select for 192.168.1.109...
Lease of 192.168.1.109 obtained, lease time 268435455
/etc/udhcpc.d/50default: Adding DNS 192.168.1.1
But since there is no test9 release yet, I dont think it will be merged into DD-WRT until such time.
From experience and generally speaking, bleeding edge (i.e. running test/master code) is a mixed bag between fixed bugs and possibly introduced issues/stability in general since the code is not mature enough and not widely tested by a large enough pool of users.
Problem is 3rd party projects like DD-WRT, most users who encounter issues with anything DD-WRT uses, dont report it to the projects upstream responsible for their development, intead report it in the 3rd party project.
These developers dont go around chasing reports here or anywhere, so it could happen that the bugs are never fixed, and we cant blame DD-WRT or the upstream project.
I would suggest our community report bugs with 3rd party libs upstream absolutely without fail and following their bug reporting processes, but this is unlikely to have any effect, and likely outcome of any reports would only include vague data attached, like (it doesn't work).