From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 125 - small bug post upgrade
Date: Mon, 19 Nov 2018 18:24:45 +0000 [thread overview]
Message-ID: <6d38af7a60c2c9aff2646a621840617e9faefada.camel@ipfire.org> (raw)
In-Reply-To: <H000006e00470fc7.1542651568.mail.at4b.net@MHS>
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
Okay, was worth a try. Could you please open a ticket and add some logs if you
can find anything useful?
-Michael
On Mon, 2018-11-19 at 13:19 -0500, Kienker, Fred wrote:
> -----Original Message-----
> From: Michael Tremer <michael.tremer(a)ipfire.org>
> Sent: Monday, November 19, 2018 13:05
> To: Kienker, Fred; development <development(a)lists.ipfire.org>
> Subject: Re: Core 125 - small bug post upgrade
>
> Hey,
>
> thanks for testing.
>
> Does this look like this?
>
> https://bugzilla.ipfire.org/show_bug.cgi?id=11917
>
> -Michael
>
> On Mon, 2018-11-19 at 12:34 -0500, Kienker, Fred wrote:
> > IPFire core 124 connecting via DHCP on RED with DNS set via the web
> > interface page Assign DNS-Server.
> > Post upgrade to core 125, after a restart, home page shows unbound in
> > local recursor mode.
> > Going to the Assign DNS-Server page, it displays the correct DNS
> > server IP numbers.
> > Clicking on the Save button corrects the problem and after unbound
> > restarts, the correct DNS server IPs are displayed on the home page.
> >
> > Its a pretty minor issue, but the fix may elude many of the less
>
> experienced.
> > Best regards,
> > Fred Kienker
> >
>
> This is a different issue. It is definitely NOT this bug as written up
> on the bug report you referenced.
>
> -Fred
>
next prev parent reply other threads:[~2018-11-19 18:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <H000006e00470d85.1542648864.mail.at4b.net@MHS>
2018-11-19 18:05 ` Michael Tremer
2018-11-19 18:19 ` Kienker, Fred
2018-11-19 18:24 ` Michael Tremer [this message]
2018-11-19 18:26 ` Kienker, Fred
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=6d38af7a60c2c9aff2646a621840617e9faefada.camel@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