From: Bruno Wolff III <bruno@wolff.to>
To: Joe Doss <joe@solidadmin.com>
Cc: Jack Craig <jack.craig.aptos@gmail.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Silvan Nagl <mail@53c70r.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>,
Neal Gompa <ngompa13@gmail.com>
Subject: Re: Wireguard not available for CentOS Stream
Date: Mon, 4 Jan 2021 14:25:15 -0600 [thread overview]
Message-ID: <20210104202515.GA30080@wolff.to> (raw)
In-Reply-To: <f1b8bbdc-d669-7236-6632-2c8c48f78b3b@solidadmin.com>
On Mon, Jan 04, 2021 at 13:42:22 -0600,
Joe Doss <joe@solidadmin.com> wrote:
>On 1/4/21 1:20 PM, Jack Craig wrote:
>> how is fedora looking? is it stable enough for a small home network?
>
>It's in the Fedora kernel and I use it daily. It works great and it is
>very stable.
Wireguard works fine in Fedora. I have two laptops that route everything
but dhcp to my home router (no matter what network they are on) via
a wireguard tunnel. My home router provides them with endpoints that have
static IP addresses. I also use it for my work desktop so that I can reach it
from home even though it is behind NAT.
next prev parent reply other threads:[~2021-01-04 20:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 20:17 Wireguard not available for CentOS Stream Silvan Nagl
2021-01-03 21:31 ` Silvan Nagl
2021-01-04 1:24 ` Joe Doss
2021-01-04 12:47 ` Jason A. Donenfeld
[not found] ` <CAL0FmdWzknetT9raQcr_BhJwSWSBKPxXZocHSr2TT6bz2QihSA@mail.gmail.com>
2021-01-04 19:42 ` Joe Doss
2021-01-04 20:25 ` Bruno Wolff III [this message]
2021-01-04 21:55 ` Jeffrey Walton
2021-01-05 11:25 ` Jonathan Aquilina
2021-01-05 18:35 ` Joe Doss
2021-01-05 18:14 ` Joe Doss
[not found] ` <VE1PR08MB5837188C79F58A014916E123A0D10@53c70r.de>
2021-01-06 9:32 ` Silvan Nagl
[not found] ` <CAH8yC8n-fC8MJxR7cA+otkqRyDZwhR7wz2Ni+-YTAgiKz7CRHA@53c70r.de>
2021-01-05 13:06 ` Silvan Nagl
2021-01-05 13:56 ` Jeffrey Walton
2021-01-05 14:58 ` Toke Høiland-Jørgensen
2021-01-12 9:57 ` Christopher Ng
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=20210104202515.GA30080@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.com \
--cc=jack.craig.aptos@gmail.com \
--cc=joe@solidadmin.com \
--cc=mail@53c70r.de \
--cc=ngompa13@gmail.com \
--cc=wireguard@lists.zx2c4.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.