I have unbound 22.214.171.124 on my Openwrt router, as well as unbound 1.10.1 nightly on a Linux box on my LAN. I didn't try to use unbound-control until recently, even though I have had it set up on both boxes years ago:
The following still works:
Linux unbound-control 1.10.1 -> Linux unbound 1.10.1
Linux unbound-control 1.10.1 -> Openwrt unbound 126.96.36.199
The following was working in the past few days, after manually installing the missing dependencies libevent2-7 and libmnl0 that the unbound-control pkg apparently started requiring (since a few minor versions ago?) but didn't (doesn't) pull down automatically:
Openwrt unbound-control 188.8.131.52 -> Openwrt unbound 184.108.40.206
Today, however, I can't get the above to work anymore, after I updated Openwrt unbound pkgs to 220.127.116.11 from the nightly trunk; I simply get:
unbound-control[28708:0] warning: control-enable is 'no' in the config file. Segmentation fault
even though my configs concerning unbound-control haven't changed, as far as I can recall.
I have re-done unbound-control-setup on the Openwrt router, to no avail, locally only.
I see the following in the log, with unbound -dvvvvv:
Wed Apr 1 12:01:38 2020 kern.info kernel: [141571.460081] do_page_fault(): sending SIGSEGV to unbound-control for invalid read access from 00000000 Wed Apr 1 12:01:38 2020 kern.info kernel: [141571.474976] ra = 77df0d2d in libunbound.so.8.1.7[77dbc000+b3000]
Is this indicative of something I'm missing with my access-control, or is this a bug?
Edit: I just tried the unbound-control v18.104.22.168 on Openwrt against the Linux unbound v1.10.1 instance. It failed with the same seg fault.