From: "Asbjørn Sloth Tønnesen" <wireguard@asbjorn.st>
To: wireguard@lists.zx2c4.com
Subject: Re: Starcraft over Wireguard ... :sideeye:
Date: Wed, 14 Feb 2018 21:24:51 +0000 [thread overview]
Message-ID: <6c70a794-6d9e-f9af-3c0d-ad4e16607a51@asbjorn.st> (raw)
In-Reply-To: <1518420236.1268661.1267596392.738A262C@webmail.messagingengine.com>
Hi Eric,
If the game requires the computers to be on the same LAN,
complete with broadcast, multicast etc., you can run a layer
2 network through WG, running a L2TPv3 tunnel on top of WG's
layer 3 network.
See ip-l2tp(8) for usage examples.
It doesn't say in the man page, but if you set the L2TP MTU
high like 1500 (to simulate standard LAN MTU), then the
packets will be fragmented at the IP layer, so at the cost
the fragmentation overhead you can even emulate a higher MTU.
--
Best regards
Asbjørn Sloth Tønnesen
prev parent reply other threads:[~2018-02-14 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 7:23 Eric Light
2018-02-12 9:07 ` Henning Reich
2018-02-14 21:24 ` Asbjørn Sloth Tønnesen [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=6c70a794-6d9e-f9af-3c0d-ad4e16607a51@asbjorn.st \
--to=wireguard@asbjorn.st \
--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).