Messages

1

22.1 Legacy Series / Unbound and Suricata both crash during overnight operations

« on: March 13, 2022, 11:35:08 am »

Updated to 22.1.2 last Friday.  Each night since, both Unbound and Suricata have been in a stopped state when I get up in the morning.

Code: [Select]

2022-03-13T04:34:50-05:00 Informational unbound [71050:0] info: service stopped (unbound 1.15.0).
2022-03-13T04:20:39-05:00 Informational unbound [71050:0] info: start of service (unbound 1.15.0).
2022-03-13T04:20:39-05:00 Notice unbound [71050:0] notice: init module 0: iterator
2022-03-13T04:20:39-05:00 Notice unbound daemonize unbound dhcpd watcher.
2022-03-12T20:34:14-06:00 Notice unbound dhcpd expired MTXINABOX @ 192.168.37.200
2022-03-12T20:33:13-06:00 Notice unbound dhcpd expired dan-Standard-PC-i440FX-PIIX-1996 @ 192.168.37.179
2022-03-12T16:02:08-06:00 Informational unbound [41343:0] info: start of service (unbound 1.15.0).
Here we see me restarting the Unbound service yesterday afternoon at 4:02pm after coming back from a trip.  Then it needs to start the service again at 4:20am?  And then stops the service at 4:34am?  From 4:34 until when I manually start it again in the morning there's 7 pages of statistics all generated within 2 minutes of that service stop.

Code: [Select]

2022-03-13T04:31:27-05:00 Notice suricata [100278] <Notice> -- all 3 packet processing threads, 4 management threads initialized, engine started.
2022-03-13T04:23:28-05:00 Notice suricata [100207] <Notice> -- This is Suricata version 6.0.4 RELEASE running in SYSTEM mode
2022-03-13T00:02:37-06:00 Notice suricata [100188] <Notice> -- rule reload starting
2022-03-12T16:10:09-06:00 Notice suricata [100188] <Notice> -- all 3 packet processing threads, 4 management threads initialized, engine started.
2022-03-12T16:02:14-06:00 Notice suricata [100101] <Notice> -- This is Suricata version 6.0.4 RELEASE running in SYSTEM mode
For Suricata we see me starting it at 4:02pm yesterday (again, when I got back from a trip), no information until the Rule Reload at 2:37am.  Nothing showing the service stopped for any reason and yet here I am starting the service at 4:23am today.

How can I figure out what is causing these services to stop? 

2

21.1 Legacy Series / Re: Wrong domain name w/Unbound DHCP leases with multiple VLANs

« on: September 15, 2021, 01:20:37 pm »

Again, forgive me as I'm not a developer and such...

Thanks for the update on that.  I'm not sure what you would like for implementation feedback, just testers or what settings should be placed in the UI? 

I wouldn't say it is necessarily "important"? but I don't believe it is expected behavior to query unbound and have it come back with a default domain when a machine is on a different vlan with different domain.  That's how I wandered into this thread.  More than likely users just don't care or don't do rDNS lookups often?  No idea.

Really appreciate the work on OPN, I've been pretty happy with it overall.  This isn't a sticking point where I would go through the work of switching or putting my USG (shudder) back in place.

3

21.1 Legacy Series / Re: Wrong domain name w/Unbound DHCP leases with multiple VLANs

« on: September 15, 2021, 03:32:46 am »

From GitHub, it looks like this has been solved? How can I test the new version?

I may have gotten lost in the conversation of the original problem and the talk of DDNS.  Are you saying Unbound handling multiple domain names on different VLANs has been fixed?

I'm fully updated and have the same issue as the OP.  Wondering if there is a solution coming or not.  It's not a huge deal, just easier to understand what device I'm looking at on a rDNS lookup (pi-hole stats).