From: Mike O'Connor <mike@pineview.net>
To: Roman Mamedov <rm@romanrm.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Significant Dropped Packets on WG interface
Date: Sun, 17 May 2020 18:20:35 +0930 [thread overview]
Message-ID: <9b569ea3-47cb-1011-a613-6a49d68a047a@pineview.net> (raw)
In-Reply-To: <20200514141508.294bf88c@natsu>
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.
Mike
On 14/5/20 6:45 pm, Roman Mamedov wrote:
> On Thu, 14 May 2020 16:35:30 +0930
> Mike O'Connor <mike@pineview.net> 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:104.127.123.10 P-t-P:103.127.123.10
>> Mask:255.255.255.248
>> 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
> https://www.mail-archive.com/wireguard@lists.zx2c4.com/msg01856.html 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.
>
prev parent reply other threads:[~2020-05-17 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 7:05 Significant Dropped Packets on WG interface Mike O'Connor
2020-05-14 9:15 ` Roman Mamedov
2020-05-14 9:34 ` Mike O'Connor
2020-05-14 9:53 ` Mike O'Connor
2020-05-17 8:50 ` Mike O'Connor [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=9b569ea3-47cb-1011-a613-6a49d68a047a@pineview.net \
--to=mike@pineview.net \
--cc=rm@romanrm.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.