Development discussion of WireGuard
 help / color / mirror / Atom feed
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: Thu, 14 May 2020 19:04:49 +0930	[thread overview]
Message-ID: <3a12db88-85f5-8379-dc6a-f64866e006f3@pineview.net> (raw)
In-Reply-To: <20200514141508.294bf88c@natsu>


> 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 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.
>
I have a ipv6 range allocated, I changed the ip before posting.

I'm routing my part of my class C and a small part of my ipv6 range from
my DC to my home.

Mike


  reply	other threads:[~2020-05-14  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14  7:05 Mike O'Connor
2020-05-14  9:15 ` Roman Mamedov
2020-05-14  9:34   ` Mike O'Connor [this message]
2020-05-14  9:53   ` Mike O'Connor
2020-05-17  8:50   ` Mike O'Connor

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=3a12db88-85f5-8379-dc6a-f64866e006f3@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).