From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: Roman Mamedov <rm@romanrm.net>, Mo Balaa <buddybalaa@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: T-Mobile 4G/5G CGNAT vs WireGuard tunnel jitter
Date: Fri, 16 Apr 2021 08:56:04 -0500 [thread overview]
Message-ID: <A40CD39D-BBF3-463D-9C7A-96A620AC6E91@lonnie.abelbeck.com> (raw)
In-Reply-To: <15541873-A1D6-417E-A3B7-121DE0D90F22@lonnie.abelbeck.com>
> On Apr 10, 2021, at 11:12 AM, Lonnie Abelbeck <lists@lonnie.abelbeck.com> wrote:
>
>> On Apr 10, 2021, at 10:59 AM, Roman Mamedov <rm@romanrm.net> wrote:
>>
>> On Sat, 10 Apr 2021 10:27:23 -0500
>> Lonnie Abelbeck <lists@lonnie.abelbeck.com> wrote:
>>
>>> I have been testing the T-Mobile Home Internet (4G/5G fixed wireless) service to a Linode VM via WireGuard.
>>>
>>> The TMHI service uses CGNAT plus an additional NAT in their modem/gateway with a MTU of 1420, so WireGuard is configured with a 1340 MTU.
>>
>> Do they provide IPv6? I see mentions that yes, but with incoming connections
>> blocked. Might still work for WG.
>
> Hi Roman,
>
> TMHI uses IPv6 for their CGNAT, but AFAIK their current firmware does not support IPv6 on the ethernet ports (I disable their WiFi).
>
> But if (when) they support IPv6, establishing the WireGuard tunnel over IPv6 would be great, and back to a 1420 MTU for WireGuard.
A quick update, TMHI does support IPv6 via DHCPv6, but sadly has the same MTU (1420) as IPv4 has, and IPv6 is firewalled inbound (as Roman said).
I now have the WireGuard transport endpoints using IPv6 over TMHI, but the jitter with low bitrate traffic still occurs as with the IPv4 transport endpoint setup. Other than that, it works quite well.
Lonnie
prev parent reply other threads:[~2021-04-16 13:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 15:27 Lonnie Abelbeck
2021-04-10 15:43 ` Mo Balaa
2021-04-10 16:03 ` Lonnie Abelbeck
2021-04-10 15:59 ` Roman Mamedov
2021-04-10 16:12 ` Lonnie Abelbeck
2021-04-16 13:56 ` Lonnie Abelbeck [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=A40CD39D-BBF3-463D-9C7A-96A620AC6E91@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--cc=buddybalaa@gmail.com \
--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).