DHCP not working after upgrade to TurrisOS 5.3.3

Emil · February 23, 2022, 11:38pm

I have the same problem on my old Turris 1.0 router.
Actual sw: BusyBox v1.30.1 () built-in shell (ash), TurrisOS 5.3.5, Turris 1.x
DHCP doesn’t work and I can’t connect by PC with manual IP 192.168.3.2.
It was working before upgrade to 5.

root@turris:/# uci show network
network.loopback=interface
network.loopback.proto=‘static’
network.loopback.ipaddr=‘127.0.0.1’
network.loopback.netmask=‘255.0.0.0’
network.loopback.ifname=‘lo’
network.globals=globals
network.globals.ula_prefix=‘fdb8:6c63:4bd9::/48’
network.lan=interface
network.lan.force_link=‘1’
network.lan.type=‘bridge’
network.lan.proto=‘static’
network.lan.netmask=‘255.255.255.0’
network.lan.ip6assign=‘60’
network.lan.ipaddr=‘192.168.3.1’
network.lan.ifname=‘lan1’ ‘lan5’ ‘lan4’ ‘lan3’ ‘lan2’
network.wan=interface
network.wan.proto=‘static’
network.wan.netmask=‘255.255.255.0’
network.wan.gateway=‘192.168.2.1’
network.wan.ipaddr=‘192.168.2.20’
network.wan.dns=‘192.168.2.1’ ‘8.8.8.8’
network.wan.ipv6=‘1’
network.wan.ifname=‘eth2’
network.wan6=interface
network.wan6.proto=‘dhcpv6’
network.wan6.noserverunicast=‘1’
network.wan6.ifname=‘@wan’
network.vpn_turris=interface
network.vpn_turris.proto=‘none’
network.vpn_turris.auto=‘1’
network.vpn_turris.ifname=‘tun_turris’
network.guest_turris=interface
network.guest_turris.enabled=‘1’
network.guest_turris.type=‘bridge’
network.guest_turris.proto=‘static’
network.guest_turris.ipaddr=‘10.111.222.1’
network.guest_turris.netmask=‘255.255.255.0’
network.guest_turris.bridge_empty=‘1’
network.guest_turris.ifname=‘guest_turris_0’

root@turris:/# ss -naptul
Netid State udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 udp UNCONN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 tcp LISTEN 0 root@turris:/# Recv-Q Send-Q Local Address:Port Peer Address:Port
0 0.0.0.0:53 0.0.0.0:* users:((“unbound”,pid=6388,fd=3))
0 0.0.0.0:67 0.0.0.0:* users:((“dnsmasq”,pid=4073,fd=4))
0 192.168.2.20:5353 0.0.0.0:* users:((“foris-controlle”,pid=4734,fd=15))
0 127.0.0.1:5353 0.0.0.0:* users:((“foris-controlle”,pid=4734,fd=14))
0 10.111.222.1:5353 0.0.0.0:* users:((“foris-controlle”,pid=4734,fd=13))
0 0.0.0.0:5353 0.0.0.0:* users:((“foris-controlle”,pid=4734,fd=10))
0 :53 : users:((“unbound”,pid=6388,fd=5))
0 [::1]:514 : users:((“syslog-ng”,pid=4209,fd=12))
0 :546 : users:((“odhcp6c”,pid=4781,fd=4))
128 0.0.0.0:53 0.0.0.0: users:((“unbound”,pid=6388,fd=4))
128 0.0.0.0:22 0.0.0.0: users:((“sshd”,pid=4174,fd=3))
100 127.0.0.1:9080 0.0.0.0:* users:((“foris-ws”,pid=4582,fd=9))
128 127.0.0.1:8953 0.0.0.0:* users:((“unbound”,pid=6388,fd=7))
128 0.0.0.0:443 0.0.0.0:* users:((“lighttpd”,pid=4762,fd=5))
100 127.0.0.1:11883 0.0.0.0:* users:((“mosquitto”,pid=4546,fd=5))
128 0.0.0.0:80 0.0.0.0:* users:((“lighttpd”,pid=4762,fd=7))
128 [::]:53 [::]:* users:((“unbound”,pid=6388,fd=6))
128 [::]:22 [::]:* users:((“sshd”,pid=4174,fd=4))
128 [::]:443 [::]:* users:((“lighttpd”,pid=4762,fd=6))
128 :6144 : users:((“domoticz”,pid=5378,fd=17))
100 [::1]:11883 [::]: users:((“mosquitto”,pid=4546,fd=4))
128 :8080 : users:((“domoticz”,pid=5378,fd=12))
128 [::]:80 [::]: users:((“lighttpd”,pid=4762,fd=4))

paulto · May 23, 2022, 3:36pm

If dhcp-range is missing after boot then a quick fix is /etc/init.d/dnsmasq restart.

The bug was fixed in dnsmasq: abort dhcp_check on interface state · openwrt/openwrt@aa403a4 · GitHub by changing carrier to up in /etc/init.d/dnsmasq.

If you are using the hbl branch, which has dnsmasq_2.85 then this fix is already included. In hbk with dnsmasq_2.80 this fix is not present yet.

I fixed it for myself by changing the relevant line:

sed -i 's/\(jsonfilter -e @[.]\)carrier/\1up/' /etc/init.d/dnsmasq

ccdi · May 29, 2022, 8:16pm

I have the same problem since the upgrade from 3.x to 5.x
Haven’t really had time to investigate yet so I put another router on the network to provide DHCP services.