From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Core Update 149 (testing) feedback
Date: Sat, 12 Sep 2020 15:09:25 +0200 [thread overview]
Message-ID: <c0fc2c56-6f0a-02e1-0a05-d26ee6fa0de6@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
Hallo all,
Have been running Core Update 149 on by test bed system. Everything that I have in place is running fine with no problems, although my IPFire setups are always kept fairly minimal.
Haven't been able to test OpenVPN yet as I am still working to get this running on my test bed, although I have got it running fine on my production system.
Hope to have it fully functioning in my test bed system before long so future core updates will be able to include it in my evaluation and feedback.
Regards,
Adolf Belka
next reply other threads:[~2020-09-12 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 13:09 Adolf Belka [this message]
2020-09-17 15:04 ` Michael Tremer
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=c0fc2c56-6f0a-02e1-0a05-d26ee6fa0de6@gmail.com \
--to=ahb.ipfire@gmail.com \
--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