Merge in DNS/adguard-home from 2554-setup-guide to new-client-dashboard Pull request #949: + client: add setup guide page Merge branch 'new-client-dashboard' of ssh://:7999/dns/adguard-home into new-client-dashboard Remove old params for MiniCssExtractPlugin Merge branch 'master' into new-client-dashboard Merge in DNS/adguard-home from new-client-dashboard to master This only affects my Windows client machine and only specifically after setting a static IP address. This is the only time that I get an IP conflict and there is no choice but to do these drastic measures because AGH DHCP cannot recover from this state. I always have to resort to drastic measures by stopping the AGH service, deleting leases.db, sessions.db, stats.db and restarting the AGH service. It is at this point that my Windows client machine fails to receive an IP address from AGH DHCP server, noting a conflict of IP.
When I am satisfied with my testing of changes to AGH, I set my main Windows client system back to receiving IP and DNS automatically. Quite often when I am doing my testing with AGH, I set my main Windows client system with a static IP during this testing time so that I don't lose connections during this time. AGH DHCP is working 99% fantastic with only this one issue that I have noticed.Running AGH service on OpenWrt with AGH DHCP enabled.It was already fixed in #833, it will be published in the next This issue mentioned about in quote and the linked commit/fix seems to be an issue that I still have several times now. Why can't assign the IP a device already has as it's static? When I switched over to using AdGuards DHCP server I was unable to set that IP as it's static when I tried it said IP already in use. My server had a static IP address assigned by my router. One problem with the DHCP server I ran into. server checks for existence of the IP address it plans to offer, before it offers)
primary and secondary DNS) so clients have fallback
Doesn't work on Windows (I just tried to configure a scope and got error "Can't detect static IP: not supported on Windows").I'm basing my comparison on Windows Server DHCP Server which I currently use, and within that, the features I currently use. Could you please explain what important features are missing?Īpologies if anything below is incorrect, but it is based on my observation so I may have overlooked or just not worked out how to do something, or a feature might just not be obviously documented.
0 kommentar(er)
