Another possibly somewhat similar issue to report.
In this scenario there's a "server" wg system that 3 peers connect to
in a site-to-site configuration; all systems are running OpenBSD
-current. No keepalive alive necessary as the sites are active 24/7.
This was setup when wg first entered the Ope
Hi misc@
I have a somewhat similar issue using wireguard on a different scenario.
I'm running a wireguard roadwarrior gateway on -CURRENT, most of my
clients are tiny devices running recent openwrt.
This gateway has ~ 15 peers connected, some are always on, most are on
disconnected state and are
> On Nov 16, 2024, at 12:41, Stuart Henderson wrote:
>
> What do you mean by "refresh the connection”?
Hi Stuart,
I’m glad you replied, because I’m sure you have a much deeper understanding of
how wireguard works than me. I think wgpka is probably working as intended, and
a network appliance
On 2024-11-16, Will wrote:
>> On Nov 15, 2024, at 16:22, obs...@loopw.com wrote:
>>
>> there are situations where stateful firewalls can forget about the wireguard
>> session, but one or more of the peers remember it. Even wireguard’s
>> keepalive wont fix that situation.
>
> From a technical
> On Nov 15, 2024, at 16:22, obs...@loopw.com wrote:
>
> there are situations where stateful firewalls can forget about the wireguard
> session, but one or more of the peers remember it. Even wireguard’s
> keepalive wont fix that situation.
From a technical perspective, wouldn’t it make sense
Den lör 16 nov. 2024 kl 13:11 skrev Gregory Edigarov :
> On Fri, 15 Nov 2024 15:22:27 -0800
> obs...@loopw.com wrote:
>
> > there are situations where stateful firewalls can forget about the
> > wireguard session, but one or more of the peers remember it. Even
> > wireguard’s keepalive wont fix th
On Fri, 15 Nov 2024 15:22:27 -0800
obs...@loopw.com wrote:
> there are situations where stateful firewalls can forget about the
> wireguard session, but one or more of the peers remember it. Even
> wireguard’s keepalive wont fix that situation.
>
isn't ifstated(8) the cure for this?
there are situations where stateful firewalls can forget about the wireguard
session, but one or more of the peers remember it. Even wireguard’s keepalive
wont fix that situation.
my “bandwidth is basically free” solution:
I have a script that basically pings an endpoint over a tunnel, and res
8 matches
Mail list logo
