public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Mentalic <mentalic@cox.net>
To: development@lists.ipfire.org
Subject: RE: Testing Core update development build 148
Date: Mon, 03 Aug 2020 16:03:21 -0500	[thread overview]
Message-ID: <001401d669d9$8679b070$936d1150$@net> (raw)
In-Reply-To: <7DEC88B9-A05A-46D9-8C9E-C73C084A8BC1@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Michael

Gui did not offer up any information apart from Status:Broken. Tried
toggling settings and resaving, no go, tried non TLS also no go.

Also curious if geoip replacement will work with a backup config or it's a
redo of my rules? Did not get that far to see because of no dns.

Regards
Wayne




-----Original Message-----
From: Michael Tremer [mailto:michael.tremer(a)ipfire.org] 
Sent: Monday, August 3, 2020 2:55 PM
To: Mentalic
Cc: IPFire: Development-List
Subject: Re: Testing Core update development build 148

Hey Wayne,

Thank you for testing.

What do you mean that DNS is not working?

Could you specify that more?

Best,
-Michael

> On 3 Aug 2020, at 20:19, Mentalic <mentalic(a)cox.net> wrote:
> 
>  
> Loaded up x64 image to my spare box. Restored backup from core 147, found
that DNS is broken with settings from the 147 present. Loaded image twice
with same results. Nothing I tried in the DNS gui could get it working.  
>  
> Loaded up Iso for the third try but did not restore a backup. Manually
typed in the same settings from 147 and DNS works normally.  
>  
>  
> Regards
> Wayne


  reply	other threads:[~2020-08-03 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000201d669ca$f3fe06f0$dbfa14d0$@net>
2020-08-03 19:54 ` Michael Tremer
2020-08-03 21:03   ` Mentalic [this message]
2020-08-03 21:06     ` Michael Tremer
2020-08-03 21:27       ` Mentalic

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='001401d669d9$8679b070$936d1150$@net' \
    --to=mentalic@cox.net \
    --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