From: Roman Mamedov <rm@romanrm.net>
To: Nico Schottelius <nico.schottelius@ungleich.ch>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Outgoing ping required in container environment (even with PersistentKeepalive)
Date: Mon, 9 May 2022 01:09:19 +0500 [thread overview]
Message-ID: <20220509010919.390ea1d8@nvm> (raw)
In-Reply-To: <878rrcfrpv.fsf@ungleich.ch>
On Sun, 08 May 2022 08:34:46 +0200
Nico Schottelius <nico.schottelius@ungleich.ch> wrote:
> The connection stays correctly established.
>
> If anyone has a pointer on what might be going on, any help is
> appreciated.
Maybe you don't have a corresponding firewall rule, and happen to rely on the
ESTABLISHED,RELATED matching instead? This could explain the "works after a
ping" behaviour. But then the PersistentKeepalive could be expected to help as
well.
--
With respect,
Roman
prev parent reply other threads:[~2022-05-08 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 6:34 Nico Schottelius
2022-05-08 19:53 ` Nico Schottelius
2022-05-08 20:09 ` Roman Mamedov [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=20220509010919.390ea1d8@nvm \
--to=rm@romanrm.net \
--cc=nico.schottelius@ungleich.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).