From: Janne Johansson <icepic.dz@gmail.com>
To: "Berkant İpek" <berkant.ipek@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Encapsulation support in wireguard-go
Date: Tue, 7 Feb 2023 09:30:12 +0100 [thread overview]
Message-ID: <CAA6-MF9e2N195qRCkh0Z90BkecYnWo6kDPkV9PA6bLA8vS1z+Q@mail.gmail.com> (raw)
In-Reply-To: <CANAp0rHRK_p+VEJ=6wEUu63XbwS2n_9zLBeOgcWOEONVB__Xog@mail.gmail.com>
Den tis 7 feb. 2023 kl 05:38 skrev Berkant İpek <berkant.ipek@gmail.com>:
> Does wireguard-go provide any facility in order to encapsulate and
> decapsulate WireGuard packets as they leave for and arrive from the
> remote peer? Or, am I just better off to use kernel implementation
> with a TUN device to handle en- and decapsulation and relaying?
I think this is what you might be looking for,
https://github.com/WireGuard/wireguard-go/tree/master/tun/netstack/examples
which has the complete endpoint in the server (and client) so that the
respective programs only need to be able to send/receive UDP packets
and will build themselves a wg tunnel and talk http inside it.
--
May the most significant bit of your life be positive.
prev parent reply other threads:[~2023-02-07 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 18:20 Berkant İpek
2023-02-07 8:30 ` Janne Johansson [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=CAA6-MF9e2N195qRCkh0Z90BkecYnWo6kDPkV9PA6bLA8vS1z+Q@mail.gmail.com \
--to=icepic.dz@gmail.com \
--cc=berkant.ipek@gmail.com \
--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).