Hey Daniel,
On Wed, Nov 16, 2016 at 11:17 PM, Daniel Kahn Gillmor
wrote:
>https://qa.debian.org/madison.php?package=wireguard
Perfect, thanks. I wound up using:
https://qa.debian.org/madison.php?package=wireguard=debian===on==on
And then I just match on the capture
On Wed, Nov 16, 2016 at 10:01 PM, Daniel Kahn Gillmor
wrote:
> On Thu 2016-11-17 02:40:30 +0900, Jason A. Donenfeld wrote:
>> Trying again with no line breaks:
>>
> Please don't assume that the source code is built from a git repository.
> On debian, we build from the
On Thu 2016-11-17 02:40:30 +0900, Jason A. Donenfeld wrote:
> Trying again with no line breaks:
>
>> WIREGUARD_VERSION := $(shell parent_name=$$(readlink -f .. | sed -n
>> 's:.*/[wW]ire[Gg]uard[a-z-]*-\([0-9.]\+\)$$:\1:p'); if [ -d ../.git ]; then
>> echo "git-$$(git rev-parse --short HEAD)";
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
A new experimental snapshot, `experimental-0.0.20161116.1`, has been tagged in
the git repository.
Please note that this snapshot is, like the rest of the project at this point
in time, experimental, and does not consitute a real release
On 2016-11-16 20:35, Jason A. Donenfeld wrote:
> Hi Felix,
>
> Patchwork was changed to "accepted" --
> http://patchwork.ozlabs.org/patch/694517/ -- but this hasn't shown up
> in the actual LEDE repo. What's up?
It's in my staging tree and will make it to the main repo soon.
- Felix
On Wed, Nov 16, 2016 at 8:35 PM, Felix Fietkau wrote:
> It's in my staging tree and will make it to the main repo soon.
Good to hear. Thanks.
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
Hi Felix,
Patchwork was changed to "accepted" --
http://patchwork.ozlabs.org/patch/694517/ -- but this hasn't shown up
in the actual LEDE repo. What's up?
Jason
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
Live on wireguard.io/install/ now:
> commit 6bd5f8cde97456e37415eab80c19d9e8241f7639
> Author: Jason A. Donenfeld
> Date: Wed Nov 16 18:44:17 2016 +0100
>
> Add openwrt docs
>
> diff --git a/docs/install.md b/docs/install.md
> index 0946182..98579e9 100644
> ---
The best I could come with:
> WIREGUARD_VERSION := $(shell parent_name=$$(readlink -f .. | sed -n
> 's:.*/[wW]ire[Gg]uard[a-z-]*-\([0-9.]\+\)$$:\1:p'); if [ -d ../.git ]; then
> echo "git-$$(git rev-parse --shor
t HEAD)"; elif [ -n $parent_name ]; then echo "$$parent_name"; else
echo
> The config value has to be the same to correlate them. In that case,
> you should show an example with multiple peers, so that it's clear
> what's happening.
It says "Peer configurations are managed via one or more wireguard_
sections." to introduce the example. However, won't hurt to add
> On 16 Nov 2016, at 17:56, Jason A. Donenfeld wrote:
>
> config wireguard_foo
>
> -->
>
> config wireguard_peer1
Unfortunately, not. All peers for iface 'foo' will be named wireguard_foo. UCI
sections are iterable if they have the same name.
wireguard_peer1 could belong
Oh, I see, that's not actually a correct suggestion.
The config value has to be the same to correlate them. In that case,
you should show an example with multiple peers, so that it's clear
what's happening.
___
WireGuard mailing list
config wireguard_foo
-->
config wireguard_peer1
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
http://lists.zx2c4.com/mailman/listinfo/wireguard
> If somebody has time, it would be good to include one or two examples at
> the end of the page (otherwise I'll do it at some point).
This one OK?
https://wiki.lede-project.org/docs/user-guide/tunneling_interface_protocols#static_addressing_of_a_gre_tunnel
:D. That is great solution, thank you!
On 2016-11-16 16:05, Jason A. Donenfeld wrote:
https://git.zx2c4.com/WireGuard/commit/?id=34df71964861e7ea5f542bac0225c8b82bb8d9b2
This commit should work around things.
___
WireGuard mailing list
On Wed, Nov 16, 2016 at 3:37 PM, Anonymous Anonymous wrote:
> Btw, as for jabber Jason, seems like I need to search for new tor gateway,
> thats why I disconnected.
Sounds sketchy. Egbert - take the lead, you're the boss, no obligation
to work with sketchorama if you find this
Hey Dan,
On Wed, Nov 16, 2016 at 3:38 PM, Dan Lüdtke wrote:
> Hi Jason,
>
>> I guess I could provide IPv6 connectivity, but why? It's a demo.
>
> Because it is a demo of a brand new protocol, showing how it can be used with
> legacy versions payload and transport protocol. I
Thanks Jason!
No hurry, though.
Is the script open source as well? Maybe I can tinker with it, so you don't
waste your precious development time on supporting infrastructure.
> On 16 Nov 2016, at 15:49, Jason A. Donenfeld wrote:
>
> Hey Dan,
>
> On Wed, Nov 16, 2016 at 3:38
You too both maintain Ubuntu PPAs.
Could you decide some way of consolidating your efforts? Egbert heeded to
the call for help first, so if it comes down to choosing a repository, choosing
his would be most fair. But you can work it out amongst yourselves.
I could join Egbert. We could create
Hey Jason,
The service/hardware is great. But it is a problem with the raid6 module
on the host.
That uses AVX/AVX2. PCExtreme hasalready blacklisted AVX because all of
the virtual machines crashes with it enabled.
I'm the only complaining about AVX2 crashing on the machines, so
therefore
Hey Egbert,
On Wed, Nov 16, 2016 at 3:22 PM, Egbert Verhage wrote:
> Hey Jason,
> Ofc. Source (wireguard-src in git) is a submodule of the last taged
> experimental
Oh, awesome. Git submodules for the win!
Jason
___
WireGuard
Hi Dan,
I guess I could provide IPv6 connectivity, but why? It's a demo.
If you're using it as an access point to the Internet with intentions
beyond simply trying out WireGuard, then you're abusing my service.
I'm happy to consider this, but I'll need to be convinced that this
actually
Hey Egbert,
I'm glad that my avx2disabler module worked for you. I believe it
would be in your interest to pressure the hosting provider into either
reenabling AVX, or fixing their CPUID to report correct information.
CPUID is the kernel's only means of judging capabilities, and if the
[virtual]
Hello Eugene & Egbert,
You too both maintain Ubuntu PPAs. Could you decide some way of
consolidating your efforts? Egbert heeded to the call for help first,
so if it comes down to choosing a repository, choosing his would be
most fair. But you can work it out amongst yourselves.
Thanks,
Jason
Hey Deniel,
Thank your for the support.
I was search for the git repo of the debian package, thank you for the link.
Besides that only difference between ours repo's is that I use a
submodule for the wireguard source.
Git repo: https://git.launchpad.net/wireguard?h=master
Greetz,
Egbert
On
On Wed, Nov 16, 2016 at 5:15 PM, Baptiste Jonglez
wrote:
> On Tue, Nov 15, 2016 at 05:01:14PM +0100, Dan Lüdtke wrote:
>> thanks for the various feedback, guys! Here is the next round:
>>
>> https://github.com/openwrt/packages/pull/3514
>
> This one is now merged,
26 matches
Mail list logo