On Sat, 22 Sep 2018 15:55:22 -0400
"Aaron W. Swenson" wrote:
> I’m going to use the official documentation IP addresses. I am using real IPv6
> addresses and not using NAT66. Naturally, NAT is being used for IPv4. Here are
> the definitions I’m using:
>
> Server Public IPv6: 2001:DB8::DEAD:F
Hey Chris,
On 9/20/18 2:28 PM, Chris Branch wrote:
wireguard-go has a bad length check in its transport message handling.
Although it cannot be exploited because of another length check earlier in the
function, this should be fixed regardless.
---
receive.go | 2 +-
1 file changed, 1 inserti
Currently, I'm using udp2raw-tunnel to transform wireguard udp traffic into
raw tcp (config files as follows),
It's very stable on my home network than using wireguard alone,
But if we can integrate RAW TCP feature into wireguard, it would
significantly improve performance and stability for end use
wireguard-go has a bad length check in its transport message handling.
Although it cannot be exploited because of another length check earlier in the
function, this should be fixed regardless.
---
receive.go | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/receive.go b/receive.
Hi,
Am I right that the Play store listing is not defined as production ready?
I'm accessing the Play store via a Device Management tool and WireGuard is
not accessible (I believe that only apps marked as "production" will be
visible via this route).
Assuming this is correct, are there any defin
I’m going to use the official documentation IP addresses. I am using real IPv6
addresses and not using NAT66. Naturally, NAT is being used for IPv4. Here are
the definitions I’m using:
Server Public IPv6: 2001:DB8::DEAD:F00D/64
Server Public IPv4: 192.0.2.1
Routed /116: 2001:DB8::BEEF:
Hi folks,
We now have a mirror of the mailing list archives on kernel.org:
https://lore.kernel.org/wireguard/
The primary archives remain in their usual place:
https://lists.zx2c4.com/pipermail/wireguard/
Jason
___
WireGuard mailing list
WireGuard@li
