I’ve just updated my Turris to version 3.11.2 and after a restart it seems as if the DHCP server does not serve any IP addresses any more.
If I try to restart the resolver I get an error. Can’t remember if it was there before:
/etc/init.d/resolver restart
Called /etc/init.d/kresd stop
set dhcp script
Called /etc/init.d/kresd start
set dhcp script
uci: Entry not found
Called /etc/resolver/dhcp_host_domain_ng.py
That’s a confusing report. kresd is a DNS server. DHCP is something else, though this dhcp_host_domain_ng.py script transports names from DHCP to DNS. So… what exactly does not work?
Maybe someone could provide me with some hint to how to debug - or get some output - of the daemon responsible for serving IP addresses. This may bring me further in gettin back into normal operation.
I’m afraid that doesn’t make it clear to me, as both protocols can be said to “serve IP addresses”, though each in quite a different way. My favorite simple tests on any affected device in the network (incl. the router):
I get an IP address from upstream, so udhpc must be running.
IPv6 is also giving out addresses to the LAN.
So the culprit must be dnsmasq, since it is the IPv4 addresses I miss.
Right now I configured a Fedora on an old laptop to serve as a DHCP-server, so I can do some other necessary work. But I’ll look into dnsmasq this evening, probably.
edit: I might have the same issue:
I have just returned home only to discover Turris stopped working
I could not connect to any wifi network (even though they showed in the air - they had full reception)
LED of every connected port (WAN port connected to bridged modem and one LAN port) was rapidly flashing. With them was also flashing (in synchronised manner) LEDs on switch and DSL router that are connected to Omnia.
I restarted the Omnia but still could not connect to it afterwards over wifi and so I went to ethernet connected machine. It could not connect either! That is when I remember seeing this thread - I changed the IP configuration to manual (matching the IP address that should have been assigned by DHCP) and suddenly I can write you this.
Please fix this! and tell me if I can provide more information
edit:
Turris OS version: 3.11.2
some other packages that are installed: adblock, lxc, pakon, openvpn, tor, kmod-ipt-extra, kmod-ipt-hashlimit, kmod-ip6tables-extra
(the kernel modules were necessary to get Ubuntu firewall running, as suggested here: Turris Omnia OS 3.5.1 + UFW in lxc Ubuntu Xenial = ERROR )
I was just trying ‘/etc/init.d/dnsmasq status’ to no avail
2019-03-20 23:29:12 notice dnsmasq[]: DNS rebinding protection is active, will discard upstream RFC1918 responses!
2019-03-20 23:29:12 notice dnsmasq[]: Allowing 127.0.0.0/8 responses
2019-03-20 23:29:21 crit dnsmasq[22825]: duplicate dhcp-host IP address 10.0.0.75 at line 29 of /var/etc/dnsmasq.conf
2019-03-20 23:29:21 crit dnsmasq[22825]: FAILED to start up
2019-03-20 23:29:26 crit dnsmasq[22851]: duplicate dhcp-host IP address 10.0.0.75 at line 29 of /var/etc/dnsmasq.conf
2019-03-20 23:29:26 crit dnsmasq[22851]: FAILED to start up
2019-03-20 23:29:31 crit dnsmasq[22880]: duplicate dhcp-host IP address 10.0.0.75 at line 29 of /var/etc/dnsmasq.conf
2019-03-20 23:29:31 crit dnsmasq[22880]: FAILED to start up
2019-03-20 23:29:36 crit dnsmasq[22904]: duplicate dhcp-host IP address 10.0.0.75 at line 29 of /var/etc/dnsmasq.conf
2019-03-20 23:29:36 crit dnsmasq[22904]: FAILED to start up
2019-03-20 23:29:42 crit dnsmasq[22928]: duplicate dhcp-host IP address 10.0.0.75 at line 29 of /var/etc/dnsmasq.conf
2019-03-20 23:29:42 crit dnsmasq[22928]: FAILED to start up
2019-03-20 23:29:47 crit dnsmasq[22957]: duplicate dhcp-host IP address 10.0.0.75 at line 29 of /var/etc/dnsmasq.conf
2019-03-20 23:29:47 crit dnsmasq[22957]: FAILED to start up
2019-03-20 23:29:47 info procd[]: Instance dnsmasq::instance1 s in a crash loop 6 crashes, 0 seconds since last crash
When executing /etc/init.d/dnsmasq restart I get these errors. I have another DCHP server running on my lan and DHCP switched off in the configuration of the networks.
2019-04-02 10:16:24 notice dnsmasq[]: DNS rebinding protection is active, will discard upstream RFC1918 responses!
2019-04-02 10:16:24 notice dnsmasq[]: Allowing 127.0.0.0/8 responses
2019-04-02 10:16:24 crit dnsmasq[11388]: failed to create listening socket for port 53: Address in use
2019-04-02 10:16:24 crit dnsmasq[11388]: FAILED to start up
2019-04-02 10:16:34 notice dnsmasq[]: DNS rebinding protection is active, will discard upstream RFC1918 responses!
2019-04-02 10:16:34 notice dnsmasq[]: Allowing 127.0.0.0/8 responses
2019-04-02 10:16:34 crit dnsmasq[11571]: failed to create listening socket for port 53: Address in use
2019-04-02 10:16:34 crit dnsmasq[11571]: FAILED to start up
Some other program is sitting on the port 53, but which one?
53 is plain DNS port. Turris routers never used dnsmasq for DNS (by default). EDIT: the default sets dnsmasq’s DNS port to 0 (i.e. disables it), but it’s not clear to me what you actually want…