From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: feature request ...
Date: Mon, 21 Mar 2022 19:26:21 +0000 [thread overview]
Message-ID: <063ADDA7-6D85-4A50-97EF-090978A2E322@ipfire.org> (raw)
In-Reply-To: <CAGGyJTq3vc=RO0awSX9TaD9qDesA1CjmMXb7p358c5EQY6K54A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2314 bytes --]
Hello Paul,
Please don’t forget to CC the development list.
The goal here should be to integrate the patch into the distribution instead of developing any workarounds. Restarting unbound has an impact on its cache and generally is not a useful idea.
Unfortunately the author of the patch has not submitted it to the list, and has also made more changes to the logging system of the script. I have no idea why that would have been necessary.
Could you please remind the author to submit this patch to the list as Adolf has pointed out so that we can work on integrating the changes?
-Michael
> On 21 Mar 2022, at 19:19, paul kairis <kairis(a)gmail.com> wrote:
>
> Hi Michael
>
> When a new system comes into the network via dhcp, unbound is not notified hence name resolution does not work. When a system expires from dhcp, unbound still remembers it. This is discussed extensively in https://bugzilla.ipfire.org/show_bug.cgi?id=12694 My only solution is to restart dhcp and unbound; then dhcp table matches unbound table. Many times I have 16 hosts in dhcp but 22 in unbound since unbound keeps that (ip,name) pair forever.
>
> Paul
>
>
> On Mon, Mar 21, 2022 at 12:01 PM Michael Tremer <michael.tremer(a)ipfire.org> wrote:
> Hello Paul,
>
> > On 21 Mar 2022, at 13:45, paul kairis <kairis(a)gmail.com> wrote:
> >
> > I would like to have one option in any of the dropdown menus titled "User Exit". When clicked, it will execute a bash script.
> > The interface needs a text box where I specify the path of the script (/root/rst). The user needs to make sure the script is +x
> > No error checking but a Warning: Use this only if you know what it does !!
> >
> > /etc/init.d/dhcp stop
> > /etc/init.d/dhcp start
> > sleep 2
> > /etc/init.d/unbound restart
> >
> > The reason:
> > Until the issues with DHCP and unbound bridge are resolved (and there are many to list here, there are bugs open),
> > I have a small 4 line script that I login to ipfire and execute (restart dhcp and unbound) so that name resolution works.
> > It saves me time from having to pop a term, login to ipfire and exec rst. It would be much easier to do it from the WUI.
>
> What issues with the bridge are you referring to?
>
> >
> > Thank you, Paul
> >
> >
>
next parent reply other threads:[~2022-03-21 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGGyJTq3vc=RO0awSX9TaD9qDesA1CjmMXb7p358c5EQY6K54A@mail.gmail.com>
2022-03-21 19:26 ` Michael Tremer [this message]
[not found] <CAGGyJTqeC7zQma7OT-fFp2J1BqHQPSKpEd3PXvK+i34_TLZWGw@mail.gmail.com>
2022-03-21 19:01 ` 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=063ADDA7-6D85-4A50-97EF-090978A2E322@ipfire.org \
--to=michael.tremer@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