On Tue, Nov 21, 2017 at 20:51:49 +0100,
"Jason A. Donenfeld" wrote:
Hi Bruno,
I'll start working on 4.15 after rc1 hits or possibly sooner, as
there's currently quite a bit of churn at the moment. The current
errors are caused by:
OK. I switched back to 4.14 and things are
Hi Bruno,
I'll start working on 4.15 after rc1 hits or possibly sooner, as
there's currently quite a bit of churn at the moment. The current
errors are caused by:
https://git.zx2c4.com/linux/commit/?id=0a833c29d89656025443cb9f0ebff7052dd95ce0
I tried building the latest WireGuard on the latest rawhide kernel an got
the following error:
/home/bruno/WireGuard/src/netlink.c: In function ‘get_device_dump_real’:
/home/bruno/WireGuard/src/netlink.c:180:2: error: too many arguments to
function ‘genl_dump_check_consistent’
For who has a Firewalld based Linux distribution like Fedora/RHEL/CentOS:
=== Host B (VPN gateway) ===
When system creates interface wg0, it is not attached to any firewall
zone, so it falls into default zone, that blocks everything except for
ICMP packets. Therefore if you simply run ping among
Hi Roman,
Great to hear. In the process of debugging this today, I managed to
find this kernel bug, in case you're curious:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-November/543183.html
THUMB2_KERNEL is still a bit flaky I guess.
Jason
Hi!
Yes. The problem is solved. Thanks for the help.
2017-11-21 18:10 GMT+03:00 Jason A. Donenfeld :
> Hi Roman,
>
> It took me all day to get a working configuration, due to a binutils
> bug, but I finally reproduced it, and then fixed the bug. Can you grab
> the latest git
Hi Roman,
It took me all day to get a working configuration, due to a binutils
bug, but I finally reproduced it, and then fixed the bug. Can you grab
the latest git master `git fetch && git reset --hard origin/master`
and let me know if it works for you?
Thanks,
Jason
2017-11-21 22:15 GMT+08:00 Jason A. Donenfeld :
> On Tue, Nov 21, 2017 at 2:21 PM, d tbsky wrote:
>> so at first client 2.2.2.2:51820 connect to server 1.1.1.1:51820
>> but then server use 172.18.1.254(lan ip address) to reply and 51820
>> port is nat to 1085
On Tue, Nov 21, 2017 at 2:21 PM, d tbsky wrote:
> so at first client 2.2.2.2:51820 connect to server 1.1.1.1:51820
> but then server use 172.18.1.254(lan ip address) to reply and 51820
> port is nat to 1085 so the communication is broken.
The server should use 1.1.1.1 to
+1 for binding only on specific IP
On 11/21/2017 02:21 PM, d tbsky wrote:
> Hi:
>I tested wireguard and the speed is amazing. but when I try to
> deploy it to our real linux firewall, I found it is hard to make it
> work.
>
>our current linux firewall have multiple interface and multiple
Hi:
I tested wireguard and the speed is amazing. but when I try to
deploy it to our real linux firewall, I found it is hard to make it
work.
our current linux firewall have multiple interface and multiple
routing tables. local program will get lan ip address and nat to
correct wan ip
On Tue, Nov 21, 2017 at 10:34 AM, Ivan Labáth
wrote:
> I don't know much about arm modules, but is seems
> like a generic module-kernel mismatch.
Nope. This is some wild consequence of all that new hand-rolled
assembly I introduced, and the interworking of thumb and
Hi René,
There are a few bottlenecks in the existing queuing code:
- transmission of packets is limited to one core, even if encryption
is multicore, to avoid out of order packets.
- packet queues use a ring buffer with two spinlocks, which cause
contention on systems with copious amounts of
Hi Jason,
Part 2 ;)
I was expecting that my ixm6 quad core 933MHz outperform my single
core dove 800MHz with a large magnitude.
Dove (Cubox-es) iperf results:
root@cubox-es:~# iperf3 -c 10.0.0.1 -t 10 -Z -i 10
Connecting to host 10.0.0.1, port 5201
[ 4] local 10.0.0.4 port 43600
Thank you very much Jason, your help has been precious!!
___
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
Hi Jason,
iperf3 -c 10.0.0.1 -t 10 -Z -i 40 -P 3
1 [
87.7%] Tasks: 29, 9 thr, 83 kthr; 6 running
2 [
28.5%] Load average: 0.86 0.64 0.87
3 [|||
16 matches
Mail list logo