public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 139 (testing) report
Date: Thu, 12 Dec 2019 20:59:48 +0100	[thread overview]
Message-ID: <a34604559673d5d4d0d860687f27b152ce844bba.camel@ipfire.org> (raw)
In-Reply-To: <870f0e4f-d807-f088-76c9-a876b3eea335@ipfire.org>

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

Hi all,
after the update there are a lots of 
sshd[17731]: error: kex_exchange_identification: Connection closed by remote host
messages. SSH was not accesible but like Peter already announced it, a restart fixed this.

OpenVPN RW and N2N seems to work as expected.

Currently here are no further complications.

Erik

Am Donnerstag, den 12.12.2019, 19:35 +0000 schrieb Peter Müller:
> Hello *,
> 
> upcoming Core Update 139 (testing, see: 
> https://blog.ipfire.org/post/ipfire-2-23-core-update-139-is-available-for-testing
> )
> is running here for about 24 hours by now, and caused major trouble
> especially
> related to IPsec.
> 
> First, the update did not triggered a "reboot is requried" message,
> which is
> obligatory since we are shipping some new Intel microcodes. Those
> need a reboot
> in order to be loaded into the CPU.
> 
> Second, I forgot to execute /usr/local/bin/sshctrl during update
> (update.sh),
> so user settings were not applied to the SSH configuration. My fault
> (again).
> 
> Third, IPsec N2N connections are not set up automatically after
> rebooting although
> they were configured to be. Worse, something seems to go seriously
> wrong, as traffic
> to a destination IP address on the other side of the IPsec connection
> is emitted
> directly to the internet.
> 
> Surprisingly enough, connections initiated from the remote network
> behind an IPsec
> connection succeed and response packets apparently are sent back
> through the tunnel.
> 
> Reason for this is unknown; as far as I am concerned, this Core
> Update is not yet ready.
> I will open bug tickets for the problems mentioned above (and others,
> if necessary).
> 
> Output of "uname -a" for reference purposes:
> > [root(a)maverick ~]# uname -a
> > Linux maverick 4.14.154-ipfire #1 SMP Fri Nov 15 07:27:41 GMT 2019
> > x86_64 Intel(R) Celeron(R) CPU N3150 @ 1.60GHz GenuineIntel
> > GNU/Linux
> 
> Thanks, and best regards,
> Peter Müller


  reply	other threads:[~2019-12-12 19:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12 19:35 Peter Müller
2019-12-12 19:59 ` ummeegge [this message]
2019-12-13 17:40 ` Peter Müller

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=a34604559673d5d4d0d860687f27b152ce844bba.camel@ipfire.org \
    --to=ummeegge@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