Significant Dropped Packets on WG interface

Mike O'Connor mike at
Sun May 17 10:50:35 CEST 2020

Hi All

So after dropping all the way down to 1364 I'm still getting a lot of
dropped packets, only at one end.

A ping test using 'ping -M do -s 1472 IP' works from both directions but
1473 does not.

I really think there is something else wrong, but I had no idea what.


On 14/5/20 6:45 pm, Roman Mamedov wrote:
> On Thu, 14 May 2020 16:35:30 +0930
> Mike O'Connor <mike at> 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 has dropped packets at both ends.
>> wg-p2p    Link encap:UNSPEC  HWaddr
>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>>           inet addr:  P-t-P: 
>> Mask:
>>           inet6 addr: 2506:c500:ff4:1::ab/64 Scope:Global
>>           inet6 addr: fe80::e6/64 Scope:Link
>>           UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
> Reduce MTU of the WG interfaces to accomodate for overhead. See 
> for
> calculations of by how much.
>>           inet6 addr: 2506:c500:ff4:1::aa/64 Scope:Global
> I wonder what's this IP range, is this some VPN service? Squatting on
> unassigned IPs within 2000::/3 seems like a very bad practice. If they wanted
> an imaginary GUA for their NAT66, I'd suggest something like 66::/16 instead.

More information about the WireGuard mailing list