On Sun, 08 May 2022 08:34:46 +0200
Nico Schottelius 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
A follow up: we "upgraded" the wireguard container to use the following
entrypoint.sh instead:
set -x
# Ensure everything is clean / show prior state
wg show
# Start all definitions
for conf in
Good morning,
another day news from the container land. When running wireguard in
kubernetes, deleting the existing pod and replacing it with a new one, I
see the following behaviour:
- The assigned IPv4 address stops being reachable (good so far)
- The assigned IPv4 address is then shortly
