public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Mentalic <mentalic@cox.net>
To: development@lists.ipfire.org
Subject: RE: Ipfire 2.23 - Core Update 131, backup restore fail
Date: Thu, 25 Apr 2019 11:00:00 -0500	[thread overview]
Message-ID: <000b01d4fb7f$f1760910$d4621b30$@net> (raw)
In-Reply-To: <F85D0F8E-A59A-471F-BD57-27A03C8EA295@ipfire.org>

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

Bug added: 12064

Wayne

-----Original Message-----
From: Michael Tremer [mailto:michael.tremer(a)ipfire.org] 
Sent: Thursday, April 25, 2019 10:49 AM
To: Mentalic
Cc: IPFire: Development-List
Subject: Re: Ipfire 2.23 - Core Update 131, backup restore fail

Hey Wayne,

Could you open a ticket in Bugzilla?

  https://bugzilla.ipfire.org/

I will assign this to Stefan and he will have a look.

-Michael

> On 25 Apr 2019, at 16:34, Mentalic <mentalic(a)cox.net> wrote:
> 
> Loaded up latest, reports master/d4f31567.
> Running: 
> -Red Green Orange Blue
> -Clam Av
>  
> When I restore a backup from 130 the IPS service no longer will run.
Attempted 4 different Ipfire configuration order combinations and was able
to get it working once, but an ipfire reboot resulted in IPS service failing
to run.  
> My configuration has a number of firewall rules and groups and really not
looking forward to retyping this in. Don't have any indication of what's
breaking the IPS though. 
>  
> Thanks and Regards
> Wayne


      reply	other threads:[~2019-04-25 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <000301d4fb7c$62eeca40$28cc5ec0$@net>
2019-04-25 15:48 ` Michael Tremer
2019-04-25 16:00   ` Mentalic [this message]

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='000b01d4fb7f$f1760910$d4621b30$@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