Messages

They used to be compressed - when you set up with ZFS

Thanks for the explanation, I didn't take note of the specifics of how ZFS works.

they are rotated every hour if they are above the configured size.

You wrote above that it is compressed to reduce the size, I don't see any archives in the log directory (except for nginx logs and a few other applications). These are just text strings and archiving would significantly reduce the size of the files, and freebsd logging settings allow you to do this, why this functionality is not used is another question.

The "maximum file size" tells the system to rotate and compress any file that's over that particular size.

nope. Neither the size of the log files with the settings from the menu does not match, and none of them are placed in the archive as you write.
File system is of course ZFS

Code Select Expand

root@OPNsense:~ # ls -lh /var/log/filter
total 234881
-rw-------  1 root wheel   47M Jun 12 17:01 filter_20250612.0017.log
-rw-------  1 root wheel   48M Jun 12 18:01 filter_20250612.0018.log
-rw-------  1 root wheel   45M Jun 12 19:01 filter_20250612.0019.log
-rw-------  1 root wheel   32M Jun 12 20:00 filter_20250612.0020.log
-rw-------  1 root wheel   47M Jun 12 21:00 filter_20250612.0021.log
-rw-------  1 root wheel   33M Jun 12 22:00 filter_20250612.0022.log
-rw-------  1 root wheel   41M Jun 12 23:01 filter_20250612.0023.log
-rw-------  1 root wheel   46M Jun 12 23:59 filter_20250612.log
-rw-------  1 root wheel   45M Jun 13 01:01 filter_20250613.0001.log
-rw-------  1 root wheel   42M Jun 13 02:01 filter_20250613.0002.log
-rw-------  1 root wheel   32M Jun 13 03:01 filter_20250613.0003.log
-rw-------  1 root wheel   21M Jun 13 04:00 filter_20250613.0004.log
-rw-------  1 root wheel   38M Jun 13 05:01 filter_20250613.0005.log
-rw-------  1 root wheel   36M Jun 13 06:00 filter_20250613.0006.log
-rw-------  1 root wheel   25M Jun 13 07:01 filter_20250613.0007.log
-rw-------  1 root wheel   36M Jun 13 08:01 filter_20250613.0008.log
-rw-------  1 root wheel   60M Jun 13 10:00 filter_20250613.0009.log
-rw-------  1 root wheel   44M Jun 13 11:01 filter_20250613.0010.log
-rw-------  1 root wheel   43M Jun 13 12:01 filter_20250613.0011.log
-rw-------  1 root wheel   47M Jun 13 13:00 filter_20250613.0012.log
-rw-------  1 root wheel   47M Jun 13 14:00 filter_20250613.0013.log
-rw-------  1 root wheel   46M Jun 13 15:00 filter_20250613.0014.log
-rw-------  1 root wheel   48M Jun 13 16:01 filter_20250613.0015.log
-rw-------  1 root wheel   47M Jun 13 17:01 filter_20250613.0016.log
-rw-------  1 root wheel   47M Jun 13 18:01 filter_20250613.0017.log
-rw-------  1 root wheel   48M Jun 13 19:00 filter_20250613.0018.log
-rw-------  1 root wheel   33M Jun 13 20:01 filter_20250613.0019.log
-rw-------  1 root wheel   40M Jun 13 21:00 filter_20250613.0020.log
-rw-------  1 root wheel   50M Jun 13 22:01 filter_20250613.0021.log
-rw-------  1 root wheel   48M Jun 13 23:01 filter_20250613.0022.log
-rw-------  1 root wheel   44M Jun 13 23:59 filter_20250613.log
-rw-------  1 root wheel  660K Jun 14 00:00 filter_20250614.log


I'm also interested in this question, I've already disabled the log of everything I can, but it continues to grow by gigabytes per day.

I have once written to the author of the plugin, he said that everything works there and that was the end of it.

как пир конечно
вот примерно так настраивается: https://www.ivpn.net/setup/router/opnsense-wireguard/

У wireguard вообще нет понятия сервер, у него все клиенты. Вопрос то в чем? У вас не получается настроить? Если Россия, то учтите, что у некоторых провайдеров протокол WG заблочен наглухо.

От так и часть фейсбука грохнет
Лучше открыть страничку с ним и в "Средствах разработчика" посмотреть какие хосты используются... и посидеть подабавлять в блок пока работать не перестанет.

Hi to all.
I've got this code:

Code Select Expand

#!/bin/sh

OPNSENSE_URL="https://ip:port"
API_KEY="key"
API_SECRET="secret"
ALIAS_NAME="NNN_ips"
IP_FILE="/tmp/NNN_ips.txt"

add_ip_to_alias() {
    local ip="$1"
    curl -k -X POST \
         -H "Content-Type: application/json" \
         -u "${API_KEY}:${API_SECRET}" \
         -d "{\"address\":\"${ip}\"}" \
         "${OPNSENSE_URL}/api/firewall/alias_util/add/${ALIAS_NAME}"
}

apply_changes() {
    curl -k -X POST \
        -H "Content-Type: application/json" \
        -u "${API_KEY}:${API_SECRET}" \
        -d "{}" \
        "${OPNSENSE_URL}/api/firewall/alias/reconfigure"
}

while IFS= read -r ip; do
    if [ -n "$ip" ]; then
        add_ip_to_alias "$ip"
        echo "$ip"
    fi
done < "$IP_FILE"

apply_changes

But it adds one address at a time, which is not very efficient. Is it possible to send the whole list to the API at once, so that the adding can be done in one request?

Try this guide: https://blog.ohmykreee.top/article/setup-tun2socks-in-opnsense/ of course replacing it with your own file

I meant that apart from folding@home there are many inherently CPU projects where performance will not be so catastrophically low.

As I remember it's a GPU-based project. And CPU will have extremely low speed of analyzing or checking jobs. Maybe you should choose a CPU-based project?  But yes, you can install it and even add the ability to run it from GUI.

I have 44 lists which gives me about 600 000 blocked domains.

I have only 4 lists in unbound blacklist category and they gave me about 900k blocked donains. Everything that can be blocked via domains can be blocked as it is, you don't need an additional service for that.

Maybe everyone else is running 4k monitors nowadays,

Then I really sympathize with them, it's shallow on 1080p, and on 4k you won't be able to see anything at all).

Ну это я, если память не изменяет, давал ссылку. Я, кстати, пробовал из start оно тоже запускается вполне себе нормально. Если кто найдет описание в чем различие, с удовольствием бы почитал. Подозреваю, что в очередности загрузки дело.. но что из них первое идет start или early вопрос интересный и в доке не описан.

Апд. нашел, наверное все же лучше в Start добавлять пользовательские службы, Early вообще до загрузки всего работает.