Invalid DHCP pool - for LAN subnet 192.168.xx.0/23 detected. Please correct the settings in Services, DHCP Server
-
So shouldn't error have gone away after he changed it to /24, etc.. ?
Good trackdown! I didn't think to look there ;)
-
An error like this
Dec 23 08:47:35 firewall php-fpm[28463]: /services_unbound.php: New alert found: Invalid DHCP pool - for LAN subnet 192.168.14.0/23 detected. Please correct the settings in Services, DHCP Servermisses nearly half the information - and that why it's triggered.
Compare this to the actual error text string :
$error_msg = sprintf(gettext('Invalid DHCP pool %1$s - %2$s for %3$s subnet %4$s/%5$s detected. Please correct the settings in Services, DHCP Server'), $poolconf['range']['from'], $poolconf['range']['to'], convert_real_interface_to_friendly_descr($dhcpif), $subnet, $ifcfgsn);Only variables %3$s - %4$s %5$ = 3, 4 and 5 print useful text, which are convert_real_interface_to_friendly_descr($dhcpif), $subnet and $ifcfgsn
These become 'LAN', '192.168.14.0' and '23' in your case.
Variable 1 and 2, in that pool, $poolconf['range']['from'] and $poolconf['range']['to'] are probably not defined and/or empty.
That triggers the error.@pyrodex : check you config.xml and compare good relation between :
<interfaces> .... <lan> <if>fxp0</if> .... <enable></enable> .... <ipaddr>192.168.1.1</ipaddr> <subnet>24</subnet>and
<dhcpd> <lan> <range> <from>192.168.1.70</from> <to>192.168.1.253</to> </range> ....Also, are there any 'sub' <pool> in :
<dhcpd> <lan> .... <pool> <range> <from>192.168.1.210</from> <to>192.168.1.220</to> </range>?
Probably not related :
Take also a look at this :@pyrodex said in Invalid DHCP pool - for LAN subnet 192.168.xx.0/23 detected. Please correct the settings in Services, DHCP Server:
Dec 23 14:18:16 firewall dhcpleases: Sending HUP signal to dns daemon(46048)
one second later :
Dec 23 14:18:17 firewall dhcpleases: Sending HUP signal to dns daemon(46048)
Dec 23 14:18:17 firewall dhcpleases: Sending HUP signal to dns daemon(46048)Check your syslog for more "Sending HUP signal to dns daemon".
Unbound being restarted many times per minute is not good at all. -
<lan> <descr><![CDATA[LAN]]></descr> <if>vmx1</if> <enable></enable> <spoofmac></spoofmac> <ipaddr>192.168.14.1</ipaddr> <subnet>23</subnet> <ipaddrv6>track6</ipaddrv6> <track6-interface>wan</track6-interface> <track6-prefix-id>1</track6-prefix-id> </lan><lan> <range> <from>192.168.15.220</from> <to>192.168.15.240</to> </range> <enable></enable> <failover_peerip></failover_peerip> <defaultleasetime>86400</defaultleasetime> <maxleasetime></maxleasetime> <netmask></netmask> <gateway></gateway> <domain>lan</domain> <domainsearchlist>lan;iot;dmz</domainsearchlist> <ddnsdomain></ddnsdomain> <ddnsdomainprimary></ddnsdomainprimary> <ddnsdomainkeyname></ddnsdomainkeyname> <ddnsdomainkeyalgorithm>hmac-md5</ddnsdomainkeyalgorithm> <ddnsdomainkey></ddnsdomainkey> <mac_allow></mac_allow> <mac_deny></mac_deny> <ddnsclientupdates>allow</ddnsclientupdates> <tftp>192.168.14.31</tftp> <ldap></ldap> <nextserver>192.168.14.31</nextserver> <filename>pxelinux.0</filename> <filename32>syslinux32.efi</filename32> <filename64>syslinux64.efi</filename64> <rootpath></rootpath> <numberoptions></numberoptions>I fixed it myself by removing all my static maps and re-adding...
-
So what what wrong with the statics? I looked through them I didn't see anything that was out of scope..
