Hi
> Reduce MTU of the WG interfaces to accomodate for overhead. See
> https://www.mail-archive.com/wireguard@lists.zx2c4.com/msg01856.html for
> calculations of by how much.
So yes it was, but I can not understand why. I worked out the MTU be
pinging back from the VPN server to the clients
> Reduce MTU of the WG interfaces to accomodate for overhead. See
> https://www.mail-archive.com/wireguard@lists.zx2c4.com/msg01856.html for
> calculations of by how much.
Ok but why all of a sudden, I'll go thought the process again and see.
>> inet6 addr: 2506:c500:ff4:1::aa/64
On Thu, 14 May 2020 16:35:30 +0930
Mike O'Connor wrote:
> Hi All
>
> For the last few weeks my Wireguard link which I use to as my default
> gateway has been having issues with TCP connections stalling.
>
> I've been trying to work out what is wrong. I just noticed that the
> Wireguard link
Hi All
For the last few weeks my Wireguard link which I use to as my default
gateway has been having issues with TCP connections stalling.
I've been trying to work out what is wrong. I just noticed that the
Wireguard link has dropped packets at both ends.
wg-p2p Link encap:UNSPEC HWaddr
