UDP may (eventually) get a native segmentation capability,
but the work is still under discussion, and possibly subject
to change.
See the FRAG option within draft-ietf-tsvwg-udp-options
(https://tools.ietf.org/html/draft-ietf-tsvwg-udp-options-05)
DF
On 13-08-18, Roman Mamedov wrote:
> On Mon, 13 Aug 2018 02:53:44 +1000
> StarBrilliant wrote:
>
> > I know Wireguard can already do IP layer fragmentation. (Just set
> > tunnel MTU >= 1441 then fragmentation will be turned on)
>
> Is that really expected to work? I tried setting MTU 9000 on
On Mon, Aug 13, 2018 at 4:41 PM Jason A. Donenfeld wrote:
>
> WireGuard's socket.c calls udp_tunnel_xmit with the DF bit set to 0,
> which means if the underlying endpoint's path has an MTU that is too
> small, the UDP packet will simply be fragmented, not dropped.
Hi Jason,
Thank you for your
WireGuard's socket.c calls udp_tunnel_xmit with the DF bit set to 0,
which means if the underlying endpoint's path has an MTU that is too
small, the UDP packet will simply be fragmented, not dropped.
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
On Mon, Aug 13, 2018 at 5:06 AM Roman Mamedov wrote:
>
> On Mon, 13 Aug 2018 02:53:44 +1000
> StarBrilliant wrote:
>
> > I know Wireguard can already do IP layer fragmentation. (Just set
> > tunnel MTU >= 1441 then fragmentation will be turned on)
>
> Is that really expected to work? I tried
On Mon, 13 Aug 2018 02:53:44 +1000
StarBrilliant wrote:
> I know Wireguard can already do IP layer fragmentation. (Just set
> tunnel MTU >= 1441 then fragmentation will be turned on)
Is that really expected to work? I tried setting MTU 9000 on both ends of a WG
tunnel, but large packets still
yer fragmentation through the "--fragment X"
option. By specifying this option, UDP packets will be no more than X
bytes. It adds an additional 4-byte overhead per fragment.
My question is, is UDP layer fragmentation technically possible for
Wireguard? If possible, will it introduce incompati
