192.168.1.42 via 192.168.1.1 dev blue0 proto static
192.168.1.150 via 192.168.1.1 dev blue0 proto static
192.168.178.29 via 192.168.178.1 dev green0 proto static
192.168.178.100 via 192.168.178.1 dev green0 proto static
192.168.178.134 via 192.168.178.1 dev green0 proto static
192.168.178.135 via 192.168.178.1 dev green0 proto static
192.168.178.136 via 192.168.178.1 dev green0 proto static
192.168.178.140 via 192.168.178.1 dev green0 proto static
192.168.178.181 via 192.168.178.1 dev green0 proto static
192.168.178.251 via 192.168.178.1 dev green0 proto static
dhcp.cgi shows the networks defined in IPFire.
A save operation transfers this information to dhcpd.conf.
Why do you this network definition for dhcpd in dhcpd.conf.local?
BTW: from a shell you can check the dhcpd config with dhcpd -t
This is the output:
dhcpd -t
Internet Systems Consortium DHCP Server 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit ISC DHCP - ISC
Config file: /etc/dhcp/dhcpd.conf
Database file: /var/state/dhcp/dhcpd.leases
PID file: /var/run/dhcpd.pid
In the forum someone said to to do that in the .local so it will stay persistent?
The output of dhcpd -t shows that the config is ok.
How are the definitions of the subnets in dhcpd.conf?
With your settings in dhcpd.conf.local you may have double DNS / router definitions. I think the last definition is active.