public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Bernhard Bitsch <bbitsch@ipfire.org>
To: IPFire Development <development@lists.ipfire.org>
Subject: Feedback about the DNS FW
Date: Wed, 29 Apr 2026 19:43:09 +0200	[thread overview]
Message-ID: <1fad9a20-1291-4584-a35e-e0a6251df296@ipfire.org> (raw)

Hi,

after using the new DNS FW ( congrats to this nice feature! ), I found 
some issues.
- Each 'save' in WUI page increases the memory consumption. Even if 
nothing changed. A restart of unbound frees this huge allocation.
- Knowing from using Jon's RPZ prototype, I checked whether a single 
reload ( used in DNS FW? ) propagates the changes, new list and/or 
allow/deny entries, really. I found cases where this isn't true. A 
unbound restart yielded the right behaviour.


I must apologize not to have tested the release. But I haven't the 
equipment, yet ( only one production system ).

Regards,
Bernhard


             reply	other threads:[~2026-04-29 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 17:43 Bernhard Bitsch [this message]
2026-04-29 20:09 ` Michael Tremer
2026-04-29 22:19   ` Bernhard Bitsch
2026-04-30 10:06     ` Michael Tremer
     [not found]       ` <210f08e2-c1ed-46c9-9e51-65ec200fe487@Canary>
2026-05-02 20:23         ` Bernhard Bitsch
2026-05-06  8:29           ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1fad9a20-1291-4584-a35e-e0a6251df296@ipfire.org \
    --to=bbitsch@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox