From: "Jason E. Aten" <j.e.aten@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: nat traversal / userspace impl
Date: Mon, 17 Apr 2017 12:45:51 -0500 [thread overview]
Message-ID: <CAPNEFAaG3cQQJSyAuGxdHQHMm6+RzrQVt9ZrzTxrVNKm01z2dA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
New to Wireguard, it looks super interesting... quick questions:
1. If it uses UDP only, how does NAT traversal (firewall punch through)
work?
2. are there userspace implementations available...?
Experience thus far: The src packages that are in repos for centos 7 were
insufficient to compile. I downloaded full wireguard source and tried to
compile the wireguard kernel module on centos 7.3 with kernel 3.10, no
luck, lots of compile time header issues. I upgraded to kernel 4.10 and
could compile the wireguard module under kernel 4.10, but then got stuck on
how to compile the dependent modules;hey aren't specific to wireguard, but
rather generic modules that just weren't in the default 4.10 kernel and I'm
not sure how to build them.
[root@k0 src]# insmod ./wireguard.ko
insmod: ERROR: could not insert module ./wireguard.ko: Unknown symbol in
module
[root@k0 src]# dmesg
...
[77292.707469] wireguard: Unknown symbol udp_sock_create4 (err 0)
[77292.711122] wireguard: Unknown symbol udp_tunnel6_xmit_skb (err 0)
[77292.714899] wireguard: Unknown symbol udp_tunnel_sock_release (err 0)
[77292.718642] wireguard: Unknown symbol setup_udp_tunnel_sock (err 0)
[77292.722699] wireguard: Unknown symbol udp_sock_create6 (err 0)
[77292.726007] wireguard: Unknown symbol udp_tunnel_xmit_skb (err 0)
[root@k0 src]#
Anywho, a userland implementation would be easier to play with. Are such
out there?
Thanks!
Jason
[-- Attachment #2: Type: text/html, Size: 1606 bytes --]
next reply other threads:[~2017-04-17 17:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 17:45 Jason E. Aten [this message]
2017-04-17 17:55 ` Jason A. Donenfeld
2017-04-17 21:28 ` Jason E. Aten
2017-04-17 21:30 ` Jason A. Donenfeld
2017-04-17 21:36 ` Jason E. Aten
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=CAPNEFAaG3cQQJSyAuGxdHQHMm6+RzrQVt9ZrzTxrVNKm01z2dA@mail.gmail.com \
--to=j.e.aten@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).