1
General Discussion / Re: RFC8781/PREF64 Support
« on: February 13, 2024, 04:32:42 am »
I guess that's a no, then?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Reporting: Settings: Unbound DNS reporting: Reset DNS data
At least that is the one it complains about. It fills the graphs for Reporting: Unbound DNS but if you don't need those you could also turn if off as well (from the settings page) to save energy and your disk.
Cheers,
Franco
SIGABRT? I would recommend resetting the database and hope that the disk itself isn't failing.
Cheers,
Franco
Same problem here.
Error due to SSL 1.1.1 then update failed.
I have tried the update again to be able to copy the logs, it passed, seemed to have worked but no more routing since reboot.
I cannot post logs as I am writing this from my phone.
What can I do?
The GUI works OK, but no packet routing and CPU load is super high, used by Python3.9.
Similar issue here. I'm not using any of the default lists, I use advanced mode with a single blocklist URL specified. No matter what I do, the size of the blocklist is always 0 now. This is with no whitelisting configured and return NXDOMAIN checked. Unbound blocklist feature does indeed appear to be broken now.Looks like in my case, unbound blocklist format has changed? If I select the "unbound" downloads from oisd.nl or https://github.com/hagezi/dns-blocklists it does not work, but if I use the "domains" format instead, it works as expected.Code: [Select]2023-02-28T12:48:40-05:00 Notice unbound blocklist download done in 2.20 seconds (0 records)
2023-02-28T12:48:40-05:00 Notice unbound blocklist download https://raw.githubusercontent.com/hagezi/dns-blocklists/main/unbound/pro.blacklist.conf (lines: 486283 exclude: 486273 block: 0)
2023-02-28T12:48:38-05:00 Notice unbound blocklist download : exclude domains matching .*localhost$|^(?![a-zA-Z_\d]).*
2023-02-28T12:48:40-05:00 Notice unbound blocklist download done in 2.20 seconds (0 records)
2023-02-28T12:48:40-05:00 Notice unbound blocklist download https://raw.githubusercontent.com/hagezi/dns-blocklists/main/unbound/pro.blacklist.conf (lines: 486283 exclude: 486273 block: 0)
2023-02-28T12:48:38-05:00 Notice unbound blocklist download : exclude domains matching .*localhost$|^(?![a-zA-Z_\d]).*
That would explain it. Maybe not all hardware is affected like this... would be best to keep track of traces separately for each machine. Maybe the other two have a single panic to trace.It was the same RAM modules in all three of them in this case as I just swapped them into each box, but you are right that keeping track of which machine generated which trace is a good idea in the future. Though hopefully with new RAM it won't be necessary...
Cheers,
Franco
So that's a fairly new chipset. Even Intel itself only has windows drivers:Question what? BSD 13 has the igc driver for the I226.
https://www.intel.com/content/www/us/en/products/sku/210599/intel-ethernet-controller-i226v/downloads.html
So if BSD does support them, it's on it's own within the kernel. I would question this greatly.