Do you have another DHCP server on that network? That can lead to lots of trouble...
1 Like
100% no. Its not single router. Its many routers in different locations.
Those logs show clients obtaining an IP address, and then quering the DNS... what is exactly not working in your setup?
Sun Jul 23 11:02:52 2017 daemon.info procd: Instance dnsmasq::cfg02411c s in a crash loop 6 crashes, 5 seconds since last crash
Your worries should be here:
Sun Jul 23 11:02:52 2017 kern.info kernel: [ 214.156585]
Sun Jul 23 11:02:52 2017 kern.info kernel: [ 214.156585] do_page_fault(): sending SIGSEGV to dnsmasq for invalid write access to 005f3000
Sun Jul 23 11:02:52 2017 kern.info kernel: [ 214.165411] epc = 778b6884 in libc.so[77844000+92000]
Sun Jul 23 11:02:52 2017 kern.info kernel: [ 214.170685] ra = 004067ed in dnsmasq[400000+1f000]
Sun Jul 23 11:02:52 2017 kern.info kernel: [ 214.175762]
That looks like a serious bug; I would open a bug report.
This worked for me too! Thanks a billion... I was trying to solve this forever, and it just wouldn't go.
I have a similar situation: only one router, only one DHCP server; it worked great, then all of a sudden no leases; changed it to 'Force DHCP even if another server is detected,' then poof, all my leases came back.
It had nothing to do with the version... Previously, I had reverted to factory image stable release, and same problem. I literally have no idea what changed, but that option did the trick, where previously it was not required.
1 Like
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.