From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Kienker, Fred" <fkienker@at4b.com>
To: development@lists.ipfire.org
Subject: RE: Core 125 - small bug post upgrade
Date: Mon, 19 Nov 2018 13:26:19 -0500
Message-ID: <H000006e00470fcb.1542651978.mail.at4b.net@MHS>
In-Reply-To: <6d38af7a60c2c9aff2646a621840617e9faefada.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2866120257199016228=="
List-Id: <development.lists.ipfire.org>

--===============2866120257199016228==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Will do.

-----Original Message-----
From: Michael Tremer <michael.tremer(a)ipfire.org> 
Sent: Monday, November 19, 2018 13:25
To: Kienker, Fred; development <development(a)lists.ipfire.org>
Subject: Re: Core 125 - small bug post upgrade

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
> 




--===============2866120257199016228==--