wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Mike O'Connor <mike@pineview.net>
To: Roman Mamedov <rm@romanrm.net>
Cc: Daniel <tech@tootai.net>, wireguard@lists.zx2c4.com
Subject: Re: [Warning: DMARC Fail Email] Re: ipv6 connexion fail - ipv4 OK
Date: Sat, 28 Aug 2021 07:24:16 +0930	[thread overview]
Message-ID: <18028d40-be81-f80b-31a2-d9ba15486dff@pineview.net> (raw)
In-Reply-To: <20210828024454.1766744f@natsu>

root@gw:~# ping -M do -s 1472 13.17.1.2
PING 103.127.123.217 (13.17.1.2) 1472(1500) bytes of data.
1480 bytes from 13.17.1.2: icmp_seq=1 ttl=60 time=7.93 ms

Link can transmit a max of 1500 bytes as seen above.

Pinging a LAN segment has the same limit. ie PC to PC has the same result.

Mike

On 28/8/21 7:14 am, Roman Mamedov wrote:
> On Sat, 28 Aug 2021 07:05:45 +0930
> Mike O'Connor <mike@pineview.net> wrote:
>
>> On a 1500 link I'm having to use 1280 to get ipv6 to successfully go
>> over a wireguard link.
> Then it is not a true 1500 MTU link, something in-between drops packets at a
> lower bar. Or maybe not all of them, but just UDP, for example.
>
> But yeah, 1280 is worth trying as well, maybe Daniel has a similar issue.
>
> As for me I am using MTU 1412 WG over IPv6 on a 1492 MTU underlying link just
> fine.
>
>> I really think wireguard should be able to fragment and send via
>> multiply UDP packets.
> It is able to, as long as the underlying link MTU is set to a correct value
> (i.e. where largest-sized packets actually go through, and not get silently
> dropped).
>


  reply	other threads:[~2021-08-27 21:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-25 15:25 Daniel
2021-08-26 11:14 ` Daniel
2021-08-27 16:14   ` Roman Mamedov
2021-08-27 17:16     ` Daniel
2021-08-27 21:35       ` [Warning: DMARC Fail Email] " Mike O'Connor
2021-08-27 21:44         ` Roman Mamedov
2021-08-27 21:54           ` Mike O'Connor [this message]
2021-08-30 10:24           ` Daniel
2021-08-30 12:55             ` Skyler Mäntysaari
2021-08-30 16:43             ` Roman Mamedov
2021-08-30 17:28               ` Daniel
2021-08-30 17:38                 ` Roman Mamedov
2021-08-30 17:44                   ` Daniel
2021-08-30 17:59                     ` Roman Mamedov
2021-08-31 17:50                       ` Daniel
2021-09-01 17:44                         ` Daniel
2021-09-03 13:59                       ` ipv6 connexion fail - ipv4 OK (SOLVED) Daniel

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=18028d40-be81-f80b-31a2-d9ba15486dff@pineview.net \
    --to=mike@pineview.net \
    --cc=rm@romanrm.net \
    --cc=tech@tootai.net \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: [Warning: DMARC Fail Email] Re: ipv6 connexion fail - ipv4 OK' \
    /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

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).