Jump to content
  • 0

Installation of Wireguard

tpanum

Asked by tpanum,

 Share

Question

tpanum

tpanum

Posted
Posted

Hello,

 

I have been struggling with this for a while, found some replies on the other communities but I simply cannot get Wireguard up and running on my Odroid HC2 with Armbian.

 

Running... 

echo "deb http://deb.debian.org/debian/ unstable main" > /etc/apt/sources.list.d/unstable-wireguard.list
printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n' > /etc/apt/preferences.d/limit-unstable
apt update
apt install -y linux-headers-odroidxu4 wireguard

yields...

  

Loading new wireguard-0.0.20181218 DKMS files...
dpkg: warning: version '3.10.106-odroidxu4
4.19.14' has bad syntax: invalid character in revision number
Building for 4.19.14-odroidxu4
Module build for kernel 4.19.14-odroidxu4 was skipped since the
kernel headers for this kernel does not seem to be installed.

 

Do I really need to compile Wireguard from source? :-(

0
Link to comment
Share on other sites

43 answers to this question

Recommended Posts

  • 0
devman

devman

Posted
Posted

Sorry, I did it on a Armbian/Ubuntu on Nanopi Neo 2, so your specifics will vary.  Hopefully the following will still work:

 

First, you're going to need the kernel headers, so (for my specific version/device): 

apt install linux-headers-4.14.70-sunxi64

In my case, this brings in headers for *every* arch, and the current wireguard install doesn't like this, so: 

cd /usr/src/linux-headers-4.14.70-sunxi64/
mkdir unusedArch
cd arch
sudo mv * ../unusedArch/
cd ../unusedArch/
mv arm64/* ../arch/
add-apt-repository ppa:wireguard/wireguard
apt update
apt install wireguard  wireguard-tools wireguard-dkms

Hope it helps.

0
Link to comment
Share on other sites

Donate your old hardware to community. Start a giveaway Raffle!

  • 0
lampra

lampra

Posted
Posted

I don't know why, but I had similar issues with wireguard on cubietruck and on opi pc.

It was mostly a matter of headers in my case. Even with armbian config I was not able to install the headers some times and on other occasions DKMS was not able to install wireguard.

My workarounds are:

1. check manually apt (eg apt-cache search linux-headers-xxxx) for the correct header package (stable or next or whatever) for your board and kernel from armbian repo  and manually install them. Then try to install wireguard with dkms.

2. If this does not work, install the headers, get the source of wireguard (check the wireguard webpage for manual installation) make & and make install and this should work even if you encounter erros during make. This is really trivial, just two commands as root!!

0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
18 minutes ago, gurabli said:

Hi, 

I'm thinking about getting a HC2, but I would like to be sure if Wireguard is supported on Odroid. Did you manage to make it work? 

I run Armbian on a NEO2 and Wireguard works perfectly. 

Thanks! 


Wireguard is supported everywhere where noted (at the download pages). I am thinking to add tools to the image by default (+328kb unpacked), otherwise just:  

apt install wireguard-tools

is enough since they were added to our main repository: https://github.com/armbian/upload/commit/4b218f5862fb0725c5426f679c1b5d6ef336ada5

0
Link to comment
Share on other sites
  • 0
trohn_javolta

trohn_javolta

Posted
Posted
On 9/4/2019 at 4:50 PM, Igor said:


Wireguard is supported everywhere where noted (at the download pages). I am thinking to add tools to the image by default (+328kb unpacked), otherwise just:  


apt install wireguard-tools

is enough since they were added to our main repository: https://github.com/armbian/upload/commit/4b218f5862fb0725c5426f679c1b5d6ef336ada5

 

I just tried wg-quick to set up wireguard and get : 

RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported

modprobe wireguard gets me: 

modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.14.133-odroidxu4

 

running stretch on odroid hc2, did update & upgrade and rebooted.

 

Any ideas how I can get wireguard to work?

0
Link to comment
Share on other sites
  • 0
trohn_javolta

trohn_javolta

Posted
Posted
3 minutes ago, Igor said:


Without I need to run an experiment .. which is not that simple.

Found a bug.
https://github.com/armbian/build/commit/64f00e821dd2ad97c8aedd6559f97fdfbd7c6894#diff-26c08b1357391cc5ad6431500ad7a103L784

Will be fixed asap.

Thx for instaneous reply. Is there a way to get the fix faster? It will take longer to get it via apt upgrade, right?

0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
14 minutes ago, trohn_javolta said:

via apt upgrade, right?


Well. That require that at least one test latest build on the device. We don't have automated testing facility nor any QA staff. (if I have time) I have to build, transfer to SD/eMMC and see if it doesn't break. If testing is done too quick, it might produce way more expenses than yours and dealing with angry "customers",  when some random but important feature is broken upstream,  is not nice ... :P

 

If you need this faster than light, DIY - you know where to find build tools or donate substantial amount and I will hire people to wait and answer on peoples wishes ...

0
Link to comment
Share on other sites
  • 0
gurabli

gurabli

Posted
Posted
On 1/11/2019 at 7:12 PM, devman said:

Sorry, I did it on a Armbian/Ubuntu on Nanopi Neo 2, so your specifics will vary.  Hopefully the following will still work:

 

First, you're going to need the kernel headers, so (for my specific version/device): 


apt install linux-headers-4.14.70-sunxi64

In my case, this brings in headers for *every* arch, and the current wireguard install doesn't like this, so: 


cd /usr/src/linux-headers-4.14.70-sunxi64/
mkdir unusedArch
cd arch
sudo mv * ../unusedArch/
cd ../unusedArch/
mv arm64/* ../arch/
add-apt-repository ppa:wireguard/wireguard
apt update
apt install wireguard  wireguard-tools wireguard-dkms

Hope it helps.

 

I have a problem now with installing kernel headers:

 

Welcome to Ubuntu Bionic with Armbian Linux 4.19.63-sunxi64
System load:   0.10 0.09 0.08   Up time:       1 day
Memory usage:  26 % of 481MB    Zram usage:    9 % of 240Mb         IP:            192.168.1.125 10.66.66.1
CPU temp:      60°C
Usage of /:    3% of 59G

[ General system configuration (beta): armbian-config ]

Last login: Fri Nov 22 06:43:30 2019 from xxxxx

nanopi@nanopineo2:~$ sudo apt install linux-headers-4.19.63-sunxi64
[sudo] password for nanopi:
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-headers-4.19.63-sunxi64
E: Couldn't find any package by glob 'linux-headers-4.19.63-sunxi64'
E: Couldn't find any package by regex 'linux-headers-4.19.63-sunxi64'
nanopi@nanopineo2:~$

 

I would like to uograde to the latest Wireguard version, but installing wireguard-dkms fails, can't build the requires modules without the kernel headers, I guess. Simply installing WG from the ppa doesn't update to the newest version on system level. I managed to update last time like this, but if I remember correctly, I was abke to install headers. I tried with armbian-config, installed headers, but still doesn't work. Any ideas? 

 

http://ix.io/22v3

0
Link to comment
Share on other sites
  • 0
gurabli

gurabli

Posted
Posted
16 minutes ago, Igor said:

where WG is latest by default anyway ... while DKMS needs some bug fixing.

Wow, many thanks Igor. 

So it is safe to uograde my Nanopi Neo2 and Orange Pi Zero boards to Kernel 5.x,and these are the stable versions. On upgrading it should not brake anything, if I'm correct, as I don't have access to one of my devices, only over ssh.

And kernel 5.x already has WG integrated, so only wg-tools needs to be installes - and that is really good! 

 

Thanks for your hard work! 

0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
31 minutes ago, gurabli said:

it should not brake anything

 

We made several manual upgrades which are noted in that document and it seems its alright.

 

33 minutes ago, gurabli said:

And kernel 5.x already has WG integrated, so only wg-tools needs to be installes - and that is really good! 


If you start with a new image, tools are also installed. Otherwise apt get wg-tools ...

1
Link to comment
Share on other sites
  • 0
gurabli

gurabli

Posted
Posted
On 11/22/2019 at 8:49 AM, Igor said:

 

We made several manual upgrades which are noted in that document and it seems its alright.

If you start with a new image, tools are also installed. Otherwise apt get wg-tools ...

 

I managed to upgrade my NEO2 to the 5.3.9 kernel as per your instructions. It looks everything is running fine.

However, I'm still not on the latest Wireguard verion:

  

[   15.833259] wireguard: WireGuard 0.0.20190702 loaded. See www.wireguard.com for information.
[   15.833268] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.

I have the official Ubuntu PPA added, 

deb http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic main

and if I install wireguard with apt install wireguard the latest version  wireguard-0.0.20191012 is installed, still, even after restart, the version loaded is  0.0.20190702

What do you think, why is this? Maybe this is because the version in the kernel is not updated to the latest 191012 version? If you push that update then it will simply install with an apt update & upgrade?

 

 

0
Link to comment
Share on other sites
  • 0
gurabli

gurabli

Posted
Posted
1 minute ago, Igor said:


Next update is scheduled for 02/2020 but first the issue has to be accepted on the to do list.

OK,  so I was right, that the version available now in the kernel is not the most recent wg version and it will be updated when you push the update to the kernel? It is how it goes?

So basically the downside of having wg in the kernel is that it can't be updated from ppa, a new kernel update is required?

The upside is that there is no need for dkms build since wg is already in the kernel?

 

Can I try to install the kernel headers for the new kernel and try apt install wireguard-dkms or it will fail to build?

0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
5 minutes ago, gurabli said:

so I was right, that the version available now in the kernel is not the most recent

 

WG author usually ping me when its time to switch to a new version. For the rest, ask at Wireguard forums. Not a problem of Armbian. If dkms is broken, do something to fix it before next release.

0
Link to comment
Share on other sites
  • 0
gurabli

gurabli

Posted
Posted
2 minutes ago, Igor said:

 

WG author usually ping me when its time to switch to a new version. For the rest, ask at Wireguard forums. Not a problem of Armbian. If dkms is broken, do something to fix it before next release.

I just wanted to understand correctly who this works (the questions I asked regarding kernel, ppa, dkms). I think I got it right, and basically everything is working as it should.

 

Just to confirm, your version of wg from dmesg is also 0.0.20190702

0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
17 minutes ago, gurabli said:

I just wanted to understand correctly who this works


This is open source. You can track authors of this and that part of the code. Then you have to expect that authors or maintainers might not have time to deal with problems you have in real time. Sometimes yes, mostly not.

2
Link to comment
Share on other sites
  • 0
Alex83

Alex83

Posted
Posted (edited)

Hi, just noticed that with Banana M1 and wireguard something stragne happens...

As described I just installed package wireguard-tools and built a wireguard tunnel. The ping variation is too high. Here is a log of Banana-PI-Tunnel:

Spoiler 

root@bananapi:~# ping 10.0.178.2
PING 10.0.178.2 (10.0.178.2) 56(84) bytes of data.
64 bytes from 10.0.178.2: icmp_seq=1 ttl=64 time=107 ms
64 bytes from 10.0.178.2: icmp_seq=2 ttl=64 time=58.0 ms
64 bytes from 10.0.178.2: icmp_seq=3 ttl=64 time=50.6 ms
64 bytes from 10.0.178.2: icmp_seq=4 ttl=64 time=44.2 ms
64 bytes from 10.0.178.2: icmp_seq=5 ttl=64 time=324 ms
64 bytes from 10.0.178.2: icmp_seq=6 ttl=64 time=51.1 ms
64 bytes from 10.0.178.2: icmp_seq=7 ttl=64 time=49.7 ms
64 bytes from 10.0.178.2: icmp_seq=8 ttl=64 time=47.8 ms
64 bytes from 10.0.178.2: icmp_seq=9 ttl=64 time=120 ms
64 bytes from 10.0.178.2: icmp_seq=10 ttl=64 time=36.1 ms
64 bytes from 10.0.178.2: icmp_seq=11 ttl=64 time=54.7 ms
64 bytes from 10.0.178.2: icmp_seq=12 ttl=64 time=52.8 ms
64 bytes from 10.0.178.2: icmp_seq=13 ttl=64 time=51.9 ms
64 bytes from 10.0.178.2: icmp_seq=14 ttl=64 time=50.7 ms
64 bytes from 10.0.178.2: icmp_seq=15 ttl=64 time=47.9 ms
64 bytes from 10.0.178.2: icmp_seq=16 ttl=64 time=49.8 ms
64 bytes from 10.0.178.2: icmp_seq=17 ttl=64 time=116 ms
64 bytes from 10.0.178.2: icmp_seq=18 ttl=64 time=44.0 ms
64 bytes from 10.0.178.2: icmp_seq=19 ttl=64 time=36.8 ms
64 bytes from 10.0.178.2: icmp_seq=20 ttl=64 time=52.6 ms
64 bytes from 10.0.178.2: icmp_seq=21 ttl=64 time=40.9 ms
64 bytes from 10.0.178.2: icmp_seq=22 ttl=64 time=44.7 ms
64 bytes from 10.0.178.2: icmp_seq=23 ttl=64 time=42.5 ms
64 bytes from 10.0.178.2: icmp_seq=24 ttl=64 time=56.2 ms
64 bytes from 10.0.178.2: icmp_seq=25 ttl=64 time=56.2 ms
64 bytes from 10.0.178.2: icmp_seq=26 ttl=64 time=108 ms
64 bytes from 10.0.178.2: icmp_seq=27 ttl=64 time=36.4 ms
64 bytes from 10.0.178.2: icmp_seq=28 ttl=64 time=58.9 ms
64 bytes from 10.0.178.2: icmp_seq=29 ttl=64 time=44.0 ms
64 bytes from 10.0.178.2: icmp_seq=30 ttl=64 time=42.9 ms
64 bytes from 10.0.178.2: icmp_seq=31 ttl=64 time=56.5 ms
64 bytes from 10.0.178.2: icmp_seq=32 ttl=64 time=44.9 ms
64 bytes from 10.0.178.2: icmp_seq=33 ttl=64 time=53.7 ms
64 bytes from 10.0.178.2: icmp_seq=34 ttl=64 time=39.1 ms
64 bytes from 10.0.178.2: icmp_seq=35 ttl=64 time=61.3 ms
64 bytes from 10.0.178.2: icmp_seq=36 ttl=64 time=49.6 ms
64 bytes from 10.0.178.2: icmp_seq=37 ttl=64 time=537 ms
64 bytes from 10.0.178.2: icmp_seq=38 ttl=64 time=42.4 ms
64 bytes from 10.0.178.2: icmp_seq=39 ttl=64 time=55.7 ms
64 bytes from 10.0.178.2: icmp_seq=40 ttl=64 time=37.8 ms
64 bytes from 10.0.178.2: icmp_seq=41 ttl=64 time=37.7 ms
64 bytes from 10.0.178.2: icmp_seq=42 ttl=64 time=50.8 ms
64 bytes from 10.0.178.2: icmp_seq=43 ttl=64 time=110 ms
64 bytes from 10.0.178.2: icmp_seq=44 ttl=64 time=37.9 ms
64 bytes from 10.0.178.2: icmp_seq=45 ttl=64 time=56.7 ms
64 bytes from 10.0.178.2: icmp_seq=46 ttl=64 time=44.7 ms
64 bytes from 10.0.178.2: icmp_seq=47 ttl=64 time=52.9 ms
64 bytes from 10.0.178.2: icmp_seq=48 ttl=64 time=220 ms
64 bytes from 10.0.178.2: icmp_seq=49 ttl=64 time=49.3 ms
64 bytes from 10.0.178.2: icmp_seq=50 ttl=64 time=48.5 ms
64 bytes from 10.0.178.2: icmp_seq=51 ttl=64 time=46.9 ms
64 bytes from 10.0.178.2: icmp_seq=52 ttl=64 time=55.9 ms
64 bytes from 10.0.178.2: icmp_seq=53 ttl=64 time=128 ms
64 bytes from 10.0.178.2: icmp_seq=54 ttl=64 time=43.9 ms
64 bytes from 10.0.178.2: icmp_seq=55 ttl=64 time=41.9 ms
64 bytes from 10.0.178.2: icmp_seq=56 ttl=64 time=51.0 ms
64 bytes from 10.0.178.2: icmp_seq=57 ttl=64 time=51.8 ms
64 bytes from 10.0.178.2: icmp_seq=58 ttl=64 time=48.9 ms
64 bytes from 10.0.178.2: icmp_seq=59 ttl=64 time=40.6 ms
64 bytes from 10.0.178.2: icmp_seq=60 ttl=64 time=106 ms
64 bytes from 10.0.178.2: icmp_seq=61 ttl=64 time=36.7 ms
64 bytes from 10.0.178.2: icmp_seq=62 ttl=64 time=44.0 ms
64 bytes from 10.0.178.2: icmp_seq=63 ttl=64 time=40.9 ms
64 bytes from 10.0.178.2: icmp_seq=64 ttl=64 time=49.0 ms
64 bytes from 10.0.178.2: icmp_seq=65 ttl=64 time=48.5 ms
64 bytes from 10.0.178.2: icmp_seq=66 ttl=64 time=41.5 ms
64 bytes from 10.0.178.2: icmp_seq=67 ttl=64 time=46.0 ms
64 bytes from 10.0.178.2: icmp_seq=68 ttl=64 time=42.7 ms
64 bytes from 10.0.178.2: icmp_seq=69 ttl=64 time=47.0 ms
64 bytes from 10.0.178.2: icmp_seq=70 ttl=64 time=45.2 ms
64 bytes from 10.0.178.2: icmp_seq=71 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=72 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=73 ttl=64 time=42.0 ms
64 bytes from 10.0.178.2: icmp_seq=74 ttl=64 time=40.7 ms
64 bytes from 10.0.178.2: icmp_seq=75 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=76 ttl=64 time=37.7 ms
64 bytes from 10.0.178.2: icmp_seq=77 ttl=64 time=36.6 ms
64 bytes from 10.0.178.2: icmp_seq=78 ttl=64 time=35.5 ms
64 bytes from 10.0.178.2: icmp_seq=79 ttl=64 time=112 ms
64 bytes from 10.0.178.2: icmp_seq=80 ttl=64 time=432 ms
64 bytes from 10.0.178.2: icmp_seq=81 ttl=64 time=41.4 ms
64 bytes from 10.0.178.2: icmp_seq=82 ttl=64 time=39.8 ms
64 bytes from 10.0.178.2: icmp_seq=83 ttl=64 time=38.7 ms
64 bytes from 10.0.178.2: icmp_seq=84 ttl=64 time=35.9 ms
64 bytes from 10.0.178.2: icmp_seq=85 ttl=64 time=40.8 ms
64 bytes from 10.0.178.2: icmp_seq=86 ttl=64 time=53.7 ms
64 bytes from 10.0.178.2: icmp_seq=87 ttl=64 time=129 ms
64 bytes from 10.0.178.2: icmp_seq=88 ttl=64 time=49.4 ms
64 bytes from 10.0.178.2: icmp_seq=89 ttl=64 time=50.6 ms
64 bytes from 10.0.178.2: icmp_seq=90 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=91 ttl=64 time=221 ms
64 bytes from 10.0.178.2: icmp_seq=92 ttl=64 time=41.1 ms
64 bytes from 10.0.178.2: icmp_seq=93 ttl=64 time=42.6 ms
64 bytes from 10.0.178.2: icmp_seq=94 ttl=64 time=38.2 ms
64 bytes from 10.0.178.2: icmp_seq=95 ttl=64 time=39.0 ms
64 bytes from 10.0.178.2: icmp_seq=96 ttl=64 time=118 ms
64 bytes from 10.0.178.2: icmp_seq=97 ttl=64 time=41.7 ms
64 bytes from 10.0.178.2: icmp_seq=98 ttl=64 time=42.0 ms
64 bytes from 10.0.178.2: icmp_seq=99 ttl=64 time=39.5 ms
64 bytes from 10.0.178.2: icmp_seq=100 ttl=64 time=39.6 ms
64 bytes from 10.0.178.2: icmp_seq=101 ttl=64 time=33.8 ms
64 bytes from 10.0.178.2: icmp_seq=102 ttl=64 time=35.6 ms
64 bytes from 10.0.178.2: icmp_seq=103 ttl=64 time=51.7 ms
64 bytes from 10.0.178.2: icmp_seq=104 ttl=64 time=42.9 ms
64 bytes from 10.0.178.2: icmp_seq=105 ttl=64 time=40.8 ms
64 bytes from 10.0.178.2: icmp_seq=106 ttl=64 time=47.7 ms
64 bytes from 10.0.178.2: icmp_seq=107 ttl=64 time=43.6 ms
64 bytes from 10.0.178.2: icmp_seq=108 ttl=64 time=42.9 ms
64 bytes from 10.0.178.2: icmp_seq=109 ttl=64 time=42.1 ms
64 bytes from 10.0.178.2: icmp_seq=110 ttl=64 time=40.2 ms
64 bytes from 10.0.178.2: icmp_seq=111 ttl=64 time=70.8 ms
64 bytes from 10.0.178.2: icmp_seq=112 ttl=64 time=37.6 ms
64 bytes from 10.0.178.2: icmp_seq=113 ttl=64 time=115 ms
64 bytes from 10.0.178.2: icmp_seq=114 ttl=64 time=43.9 ms
64 bytes from 10.0.178.2: icmp_seq=115 ttl=64 time=43.6 ms
64 bytes from 10.0.178.2: icmp_seq=116 ttl=64 time=41.8 ms
64 bytes from 10.0.178.2: icmp_seq=117 ttl=64 time=35.7 ms
64 bytes from 10.0.178.2: icmp_seq=118 ttl=64 time=46.7 ms
64 bytes from 10.0.178.2: icmp_seq=119 ttl=64 time=37.8 ms
64 bytes from 10.0.178.2: icmp_seq=120 ttl=64 time=35.9 ms
64 bytes from 10.0.178.2: icmp_seq=121 ttl=64 time=37.8 ms
64 bytes from 10.0.178.2: icmp_seq=122 ttl=64 time=65.0 ms
64 bytes from 10.0.178.2: icmp_seq=123 ttl=64 time=142 ms
64 bytes from 10.0.178.2: icmp_seq=124 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=125 ttl=64 time=42.9 ms
64 bytes from 10.0.178.2: icmp_seq=126 ttl=64 time=38.7 ms
64 bytes from 10.0.178.2: icmp_seq=127 ttl=64 time=36.6 ms
64 bytes from 10.0.178.2: icmp_seq=128 ttl=64 time=39.8 ms
64 bytes from 10.0.178.2: icmp_seq=129 ttl=64 time=38.7 ms
64 bytes from 10.0.178.2: icmp_seq=130 ttl=64 time=116 ms
64 bytes from 10.0.178.2: icmp_seq=131 ttl=64 time=45.7 ms
64 bytes from 10.0.178.2: icmp_seq=132 ttl=64 time=51.7 ms
64 bytes from 10.0.178.2: icmp_seq=133 ttl=64 time=41.9 ms
64 bytes from 10.0.178.2: icmp_seq=134 ttl=64 time=163 ms
64 bytes from 10.0.178.2: icmp_seq=135 ttl=64 time=38.8 ms
64 bytes from 10.0.178.2: icmp_seq=136 ttl=64 time=41.7 ms
64 bytes from 10.0.178.2: icmp_seq=137 ttl=64 time=36.8 ms
64 bytes from 10.0.178.2: icmp_seq=138 ttl=64 time=35.6 ms
64 bytes from 10.0.178.2: icmp_seq=139 ttl=64 time=65.3 ms
64 bytes from 10.0.178.2: icmp_seq=140 ttl=64 time=44.8 ms
64 bytes from 10.0.178.2: icmp_seq=141 ttl=64 time=43.4 ms
64 bytes from 10.0.178.2: icmp_seq=142 ttl=64 time=52.8 ms
64 bytes from 10.0.178.2: icmp_seq=143 ttl=64 time=38.8 ms
64 bytes from 10.0.178.2: icmp_seq=144 ttl=64 time=37.7 ms
64 bytes from 10.0.178.2: icmp_seq=145 ttl=64 time=35.8 ms
64 bytes from 10.0.178.2: icmp_seq=146 ttl=64 time=39.8 ms
64 bytes from 10.0.178.2: icmp_seq=147 ttl=64 time=113 ms
64 bytes from 10.0.178.2: icmp_seq=148 ttl=64 time=33.6 ms
64 bytes from 10.0.178.2: icmp_seq=149 ttl=64 time=46.1 ms
64 bytes from 10.0.178.2: icmp_seq=150 ttl=64 time=43.6 ms
64 bytes from 10.0.178.2: icmp_seq=151 ttl=64 time=43.7 ms
64 bytes from 10.0.178.2: icmp_seq=152 ttl=64 time=44.1 ms
64 bytes from 10.0.178.2: icmp_seq=153 ttl=64 time=39.4 ms
64 bytes from 10.0.178.2: icmp_seq=154 ttl=64 time=41.4 ms
64 bytes from 10.0.178.2: icmp_seq=155 ttl=64 time=39.4 ms
64 bytes from 10.0.178.2: icmp_seq=156 ttl=64 time=73.7 ms
64 bytes from 10.0.178.2: icmp_seq=157 ttl=64 time=139 ms
64 bytes from 10.0.178.2: icmp_seq=158 ttl=64 time=41.6 ms
64 bytes from 10.0.178.2: icmp_seq=159 ttl=64 time=40.2 ms
64 bytes from 10.0.178.2: icmp_seq=160 ttl=64 time=53.4 ms
64 bytes from 10.0.178.2: icmp_seq=161 ttl=64 time=40.0 ms
64 bytes from 10.0.178.2: icmp_seq=162 ttl=64 time=35.6 ms
64 bytes from 10.0.178.2: icmp_seq=163 ttl=64 time=49.6 ms
64 bytes from 10.0.178.2: icmp_seq=164 ttl=64 time=41.2 ms
64 bytes from 10.0.178.2: icmp_seq=165 ttl=64 time=40.6 ms
64 bytes from 10.0.178.2: icmp_seq=166 ttl=64 time=288 ms
64 bytes from 10.0.178.2: icmp_seq=167 ttl=64 time=56.0 ms
64 bytes from 10.0.178.2: icmp_seq=168 ttl=64 time=54.9 ms
64 bytes from 10.0.178.2: icmp_seq=169 ttl=64 time=54.7 ms
64 bytes from 10.0.178.2: icmp_seq=170 ttl=64 time=52.8 ms
64 bytes from 10.0.178.2: icmp_seq=171 ttl=64 time=41.9 ms
64 bytes from 10.0.178.2: icmp_seq=172 ttl=64 time=51.9 ms
64 bytes from 10.0.178.2: icmp_seq=173 ttl=64 time=49.7 ms
64 bytes from 10.0.178.2: icmp_seq=174 ttl=64 time=107 ms
64 bytes from 10.0.178.2: icmp_seq=175 ttl=64 time=46.7 ms
64 bytes from 10.0.178.2: icmp_seq=176 ttl=64 time=54.8 ms
64 bytes from 10.0.178.2: icmp_seq=177 ttl=64 time=53.9 ms
64 bytes from 10.0.178.2: icmp_seq=178 ttl=64 time=52.9 ms
64 bytes from 10.0.178.2: icmp_seq=179 ttl=64 time=51.6 ms
64 bytes from 10.0.178.2: icmp_seq=180 ttl=64 time=42.7 ms
64 bytes from 10.0.178.2: icmp_seq=181 ttl=64 time=37.7 ms
64 bytes from 10.0.178.2: icmp_seq=182 ttl=64 time=45.8 ms
64 bytes from 10.0.178.2: icmp_seq=183 ttl=64 time=54.6 ms
64 bytes from 10.0.178.2: icmp_seq=184 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=185 ttl=64 time=41.6 ms
64 bytes from 10.0.178.2: icmp_seq=186 ttl=64 time=49.7 ms
64 bytes from 10.0.178.2: icmp_seq=187 ttl=64 time=47.7 ms
64 bytes from 10.0.178.2: icmp_seq=188 ttl=64 time=45.7 ms
64 bytes from 10.0.178.2: icmp_seq=189 ttl=64 time=34.1 ms
64 bytes from 10.0.178.2: icmp_seq=190 ttl=64 time=53.5 ms
64 bytes from 10.0.178.2: icmp_seq=191 ttl=64 time=110 ms
64 bytes from 10.0.178.2: icmp_seq=192 ttl=64 time=59.9 ms
64 bytes from 10.0.178.2: icmp_seq=193 ttl=64 time=58.7 ms
64 bytes from 10.0.178.2: icmp_seq=194 ttl=64 time=56.8 ms
64 bytes from 10.0.178.2: icmp_seq=195 ttl=64 time=54.8 ms
64 bytes from 10.0.178.2: icmp_seq=196 ttl=64 time=39.8 ms
64 bytes from 10.0.178.2: icmp_seq=197 ttl=64 time=53.8 ms
64 bytes from 10.0.178.2: icmp_seq=198 ttl=64 time=503 ms
64 bytes from 10.0.178.2: icmp_seq=199 ttl=64 time=40.6 ms
64 bytes from 10.0.178.2: icmp_seq=200 ttl=64 time=60.4 ms
64 bytes from 10.0.178.2: icmp_seq=201 ttl=64 time=117 ms
64 bytes from 10.0.178.2: icmp_seq=202 ttl=64 time=56.0 ms
64 bytes from 10.0.178.2: icmp_seq=203 ttl=64 time=55.9 ms
64 bytes from 10.0.178.2: icmp_seq=204 ttl=64 time=44.7 ms
64 bytes from 10.0.178.2: icmp_seq=205 ttl=64 time=52.9 ms
64 bytes from 10.0.178.2: icmp_seq=206 ttl=64 time=51.6 ms
64 bytes from 10.0.178.2: icmp_seq=207 ttl=64 time=49.9 ms
64 bytes from 10.0.178.2: icmp_seq=208 ttl=64 time=48.7 ms
64 bytes from 10.0.178.2: icmp_seq=209 ttl=64 time=56.7 ms
64 bytes from 10.0.178.2: icmp_seq=210 ttl=64 time=54.8 ms
64 bytes from 10.0.178.2: icmp_seq=211 ttl=64 time=53.9 ms
64 bytes from 10.0.178.2: icmp_seq=212 ttl=64 time=53.0 ms
64 bytes from 10.0.178.2: icmp_seq=213 ttl=64 time=51.7 ms
64 bytes from 10.0.178.2: icmp_seq=214 ttl=64 time=49.7 ms
64 bytes from 10.0.178.2: icmp_seq=215 ttl=64 time=47.6 ms
64 bytes from 10.0.178.2: icmp_seq=216 ttl=64 time=55.7 ms
64 bytes from 10.0.178.2: icmp_seq=217 ttl=64 time=54.8 ms
64 bytes from 10.0.178.2: icmp_seq=218 ttl=64 time=55.9 ms
64 bytes from 10.0.178.2: icmp_seq=219 ttl=64 time=51.8 ms
64 bytes from 10.0.178.2: icmp_seq=220 ttl=64 time=50.7 ms
64 bytes from 10.0.178.2: icmp_seq=221 ttl=64 time=48.9 ms
64 bytes from 10.0.178.2: icmp_seq=222 ttl=64 time=47.9 ms
64 bytes from 10.0.178.2: icmp_seq=223 ttl=64 time=46.6 ms
64 bytes from 10.0.178.2: icmp_seq=224 ttl=64 time=54.7 ms
64 bytes from 10.0.178.2: icmp_seq=225 ttl=64 time=52.7 ms
64 bytes from 10.0.178.2: icmp_seq=226 ttl=64 time=51.8 ms
64 bytes from 10.0.178.2: icmp_seq=227 ttl=64 time=110 ms
64 bytes from 10.0.178.2: icmp_seq=228 ttl=64 time=49.8 ms
64 bytes from 10.0.178.2: icmp_seq=229 ttl=64 time=48.8 ms
64 bytes from 10.0.178.2: icmp_seq=230 ttl=64 time=38.0 ms
64 bytes from 10.0.178.2: icmp_seq=231 ttl=64 time=46.2 ms
64 bytes from 10.0.178.2: icmp_seq=232 ttl=64 time=45.0 ms
64 bytes from 10.0.178.2: icmp_seq=233 ttl=64 time=43.9 ms
64 bytes from 10.0.178.2: icmp_seq=234 ttl=64 time=62.6 ms
64 bytes from 10.0.178.2: icmp_seq=235 ttl=64 time=117 ms
64 bytes from 10.0.178.2: icmp_seq=236 ttl=64 time=60.2 ms
64 bytes from 10.0.178.2: icmp_seq=237 ttl=64 time=58.0 ms
64 bytes from 10.0.178.2: icmp_seq=238 ttl=64 time=56.5 ms
64 bytes from 10.0.178.2: icmp_seq=239 ttl=64 time=54.9 ms
64 bytes from 10.0.178.2: icmp_seq=240 ttl=64 time=53.6 ms
64 bytes from 10.0.178.2: icmp_seq=241 ttl=64 time=56.2 ms
64 bytes from 10.0.178.2: icmp_seq=242 ttl=64 time=60.2 ms
64 bytes from 10.0.178.2: icmp_seq=243 ttl=64 time=58.9 ms
64 bytes from 10.0.178.2: icmp_seq=244 ttl=64 time=117 ms
64 bytes from 10.0.178.2: icmp_seq=245 ttl=64 time=55.8 ms
64 bytes from 10.0.178.2: icmp_seq=246 ttl=64 time=54.9 ms
64 bytes from 10.0.178.2: icmp_seq=247 ttl=64 time=61.7 ms
64 bytes from 10.0.178.2: icmp_seq=248 ttl=64 time=51.9 ms
64 bytes from 10.0.178.2: icmp_seq=249 ttl=64 time=50.8 ms
64 bytes from 10.0.178.2: icmp_seq=250 ttl=64 time=49.7 ms
64 bytes from 10.0.178.2: icmp_seq=251 ttl=64 time=48.6 ms
64 bytes from 10.0.178.2: icmp_seq=252 ttl=64 time=130 ms
64 bytes from 10.0.178.2: icmp_seq=253 ttl=64 time=55.2 ms
64 bytes from 10.0.178.2: icmp_seq=254 ttl=64 time=53.8 ms
64 bytes from 10.0.178.2: icmp_seq=255 ttl=64 time=41.8 ms
64 bytes from 10.0.178.2: icmp_seq=256 ttl=64 time=51.8 ms
64 bytes from 10.0.178.2: icmp_seq=257 ttl=64 time=50.8 ms
64 bytes from 10.0.178.2: icmp_seq=258 ttl=64 time=49.8 ms
64 bytes from 10.0.178.2: icmp_seq=259 ttl=64 time=48.7 ms
64 bytes from 10.0.178.2: icmp_seq=260 ttl=64 time=46.8 ms
64 bytes from 10.0.178.2: icmp_seq=261 ttl=64 time=106 ms
64 bytes from 10.0.178.2: icmp_seq=262 ttl=64 time=47.8 ms
64 bytes from 10.0.178.2: icmp_seq=263 ttl=64 time=56.9 ms
64 bytes from 10.0.178.2: icmp_seq=264 ttl=64 time=52.5 ms
64 bytes from 10.0.178.2: icmp_seq=265 ttl=64 time=53.9 ms
64 bytes from 10.0.178.2: icmp_seq=266 ttl=64 time=49.7 ms
64 bytes from 10.0.178.2: icmp_seq=267 ttl=64 time=50.6 ms
64 bytes from 10.0.178.2: icmp_seq=268 ttl=64 time=48.9 ms
64 bytes from 10.0.178.2: icmp_seq=269 ttl=64 time=47.9 ms
64 bytes from 10.0.178.2: icmp_seq=270 ttl=64 time=53.5 ms
64 bytes from 10.0.178.2: icmp_seq=271 ttl=64 time=132 ms
64 bytes from 10.0.178.2: icmp_seq=272 ttl=64 time=50.4 ms
64 bytes from 10.0.178.2: icmp_seq=273 ttl=64 time=48.8 ms
64 bytes from 10.0.178.2: icmp_seq=274 ttl=64 time=47.8 ms
64 bytes from 10.0.178.2: icmp_seq=275 ttl=64 time=46.6 ms
64 bytes from 10.0.178.2: icmp_seq=276 ttl=64 time=55.0 ms
64 bytes from 10.0.178.2: icmp_seq=277 ttl=64 time=54.0 ms
64 bytes from 10.0.178.2: icmp_seq=278 ttl=64 time=122 ms
64 bytes from 10.0.178.2: icmp_seq=279 ttl=64 time=60.6 ms
64 bytes from 10.0.178.2: icmp_seq=280 ttl=64 time=59.0 ms
64 bytes from 10.0.178.2: icmp_seq=281 ttl=64 time=57.8 ms
64 bytes from 10.0.178.2: icmp_seq=282 ttl=64 time=56.6 ms
64 bytes from 10.0.178.2: icmp_seq=283 ttl=64 time=55.0 ms
64 bytes from 10.0.178.2: icmp_seq=284 ttl=64 time=343 ms
64 bytes from 10.0.178.2: icmp_seq=285 ttl=64 time=52.7 ms
64 bytes from 10.0.178.2: icmp_seq=286 ttl=64 time=51.0 ms
64 bytes from 10.0.178.2: icmp_seq=287 ttl=64 time=69.4 ms
64 bytes from 10.0.178.2: icmp_seq=288 ttl=64 time=57.8 ms
64 bytes from 10.0.178.2: icmp_seq=289 ttl=64 time=56.4 ms
64 bytes from 10.0.178.2: icmp_seq=290 ttl=64 time=54.9 ms
64 bytes from 10.0.178.2: icmp_seq=291 ttl=64 time=53.6 ms
64 bytes from 10.0.178.2: icmp_seq=292 ttl=64 time=36.8 ms
64 bytes from 10.0.178.2: icmp_seq=293 ttl=64 time=49.9 ms
64 bytes from 10.0.178.2: icmp_seq=294 ttl=64 time=48.7 ms
64 bytes from 10.0.178.2: icmp_seq=295 ttl=64 time=111 ms
64 bytes from 10.0.178.2: icmp_seq=296 ttl=64 time=54.9 ms
64 bytes from 10.0.178.2: icmp_seq=297 ttl=64 time=53.8 ms
64 bytes from 10.0.178.2: icmp_seq=298 ttl=64 time=53.5 ms
64 bytes from 10.0.178.2: icmp_seq=299 ttl=64 time=59.1 ms
64 bytes from 10.0.178.2: icmp_seq=300 ttl=64 time=49.9 ms
64 bytes from 10.0.178.2: icmp_seq=301 ttl=64 time=49.6 ms
64 bytes from 10.0.178.2: icmp_seq=302 ttl=64 time=47.6 ms
64 bytes from 10.0.178.2: icmp_seq=303 ttl=64 time=54.7 ms
64 bytes from 10.0.178.2: icmp_seq=304 ttl=64 time=62.9 ms
64 bytes from 10.0.178.2: icmp_seq=305 ttl=64 time=129 ms
64 bytes from 10.0.178.2: icmp_seq=306 ttl=64 time=52.7 ms
64 bytes from 10.0.178.2: icmp_seq=307 ttl=64 time=48.7 ms
64 bytes from 10.0.178.2: icmp_seq=308 ttl=64 time=46.7 ms
64 bytes from 10.0.178.2: icmp_seq=309 ttl=64 time=54.7 ms
64 bytes from 10.0.178.2: icmp_seq=310 ttl=64 time=52.9 ms
64 bytes from 10.0.178.2: icmp_seq=311 ttl=64 time=51.7 ms
64 bytes from 10.0.178.2: icmp_seq=312 ttl=64 time=49.9 ms
64 bytes from 10.0.178.2: icmp_seq=313 ttl=64 time=48.7 ms
64 bytes from 10.0.178.2: icmp_seq=314 ttl=64 time=126 ms
64 bytes from 10.0.178.2: icmp_seq=315 ttl=64 time=45.9 ms
64 bytes from 10.0.178.2: icmp_seq=316 ttl=64 time=34.5 ms

 

And the same time to same destination from my Ubuntu-Desktop-Wireguard-Tunnel:

Spoiler 

root@alex-ubuntu-PC:/home/alex# ping 10.0.178.2
PING 10.0.178.2 (10.0.178.2) 56(84) bytes of data.
64 bytes from 10.0.178.2: icmp_seq=1 ttl=64 time=51.3 ms
64 bytes from 10.0.178.2: icmp_seq=2 ttl=64 time=45.5 ms
64 bytes from 10.0.178.2: icmp_seq=3 ttl=64 time=43.4 ms
64 bytes from 10.0.178.2: icmp_seq=4 ttl=64 time=42.1 ms
64 bytes from 10.0.178.2: icmp_seq=5 ttl=64 time=55.5 ms
64 bytes from 10.0.178.2: icmp_seq=6 ttl=64 time=39.0 ms
64 bytes from 10.0.178.2: icmp_seq=7 ttl=64 time=38.4 ms
64 bytes from 10.0.178.2: icmp_seq=8 ttl=64 time=51.1 ms
64 bytes from 10.0.178.2: icmp_seq=9 ttl=64 time=37.8 ms
64 bytes from 10.0.178.2: icmp_seq=10 ttl=64 time=37.8 ms
64 bytes from 10.0.178.2: icmp_seq=11 ttl=64 time=35.9 ms
64 bytes from 10.0.178.2: icmp_seq=12 ttl=64 time=40.9 ms
64 bytes from 10.0.178.2: icmp_seq=13 ttl=64 time=39.1 ms
64 bytes from 10.0.178.2: icmp_seq=14 ttl=64 time=42.0 ms
64 bytes from 10.0.178.2: icmp_seq=15 ttl=64 time=41.8 ms
64 bytes from 10.0.178.2: icmp_seq=16 ttl=64 time=42.8 ms
64 bytes from 10.0.178.2: icmp_seq=17 ttl=64 time=33.9 ms
64 bytes from 10.0.178.2: icmp_seq=18 ttl=64 time=38.2 ms
64 bytes from 10.0.178.2: icmp_seq=19 ttl=64 time=35.9 ms
64 bytes from 10.0.178.2: icmp_seq=20 ttl=64 time=45.5 ms
64 bytes from 10.0.178.2: icmp_seq=21 ttl=64 time=43.8 ms
64 bytes from 10.0.178.2: icmp_seq=22 ttl=64 time=41.7 ms
64 bytes from 10.0.178.2: icmp_seq=23 ttl=64 time=40.5 ms
64 bytes from 10.0.178.2: icmp_seq=24 ttl=64 time=41.7 ms
64 bytes from 10.0.178.2: icmp_seq=25 ttl=64 time=46.9 ms
64 bytes from 10.0.178.2: icmp_seq=26 ttl=64 time=36.7 ms
64 bytes from 10.0.178.2: icmp_seq=27 ttl=64 time=34.8 ms
64 bytes from 10.0.178.2: icmp_seq=28 ttl=64 time=45.2 ms
64 bytes from 10.0.178.2: icmp_seq=29 ttl=64 time=41.4 ms
64 bytes from 10.0.178.2: icmp_seq=30 ttl=64 time=41.0 ms
64 bytes from 10.0.178.2: icmp_seq=31 ttl=64 time=42.9 ms
64 bytes from 10.0.178.2: icmp_seq=32 ttl=64 time=37.9 ms
64 bytes from 10.0.178.2: icmp_seq=33 ttl=64 time=38.6 ms
64 bytes from 10.0.178.2: icmp_seq=34 ttl=64 time=40.0 ms
64 bytes from 10.0.178.2: icmp_seq=35 ttl=64 time=38.1 ms
64 bytes from 10.0.178.2: icmp_seq=36 ttl=64 time=37.9 ms
64 bytes from 10.0.178.2: icmp_seq=37 ttl=64 time=41.0 ms
64 bytes from 10.0.178.2: icmp_seq=38 ttl=64 time=45.7 ms
64 bytes from 10.0.178.2: icmp_seq=39 ttl=64 time=43.5 ms
64 bytes from 10.0.178.2: icmp_seq=40 ttl=64 time=43.6 ms
64 bytes from 10.0.178.2: icmp_seq=41 ttl=64 time=40.6 ms
64 bytes from 10.0.178.2: icmp_seq=42 ttl=64 time=38.8 ms
64 bytes from 10.0.178.2: icmp_seq=43 ttl=64 time=41.3 ms
64 bytes from 10.0.178.2: icmp_seq=44 ttl=64 time=35.7 ms
64 bytes from 10.0.178.2: icmp_seq=45 ttl=64 time=35.7 ms
64 bytes from 10.0.178.2: icmp_seq=46 ttl=64 time=43.0 ms
64 bytes from 10.0.178.2: icmp_seq=47 ttl=64 time=42.9 ms
64 bytes from 10.0.178.2: icmp_seq=48 ttl=64 time=57.1 ms
64 bytes from 10.0.178.2: icmp_seq=49 ttl=64 time=43.7 ms
64 bytes from 10.0.178.2: icmp_seq=50 ttl=64 time=38.9 ms
64 bytes from 10.0.178.2: icmp_seq=51 ttl=64 time=36.9 ms
64 bytes from 10.0.178.2: icmp_seq=52 ttl=64 time=50.3 ms
^C
--- 10.0.178.2 ping statistics ---
52 packets transmitted, 52 received, 0% packet loss, time 51071ms
rtt min/avg/max/mdev = 33.937/41.690/57.104/4.870 ms
root@alex-ubuntu-PC:/home/alex#

 

Both is without any traffic (beside ping) over the wg-tunnel. The Banana isn't overloaded. Just installed armbian bionic without desktop and first thing to try was the tunnel from clean setup. Also the MTU of the wireguard is set to 1300 for the test to prevent fragmentation.

 

Any ideas what's wrong and how to get wireguard-dkms-package or low-latency-Kernels onto the Banana PI? I think there is a problem with priority and realtime of the wireguard-protocol.

 

 

Edited by Igor
add spoilers
0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
4 hours ago, Alex83 said:

how to get wireguard-dkms-package or low-latency-Kernels onto the Banana PI? I think there is a problem with priority and realtime of the wireguard-protocol.

 

We (hopefully) fixed DKMS on Armbian (less than one day ago) and Wireguard that is shipped with the kernel was bumped to last version few day ago.  

https://github.com/armbian/build/commit/8970fc6730f972bc7f4c6a03fc6973c145e5ee36

https://github.com/armbian/build/pull/1697


Shortest way of testing will be that you make an image on your own and test. If you want real-time kernel, this will be more tricky, but its doable. You need to build from sources again while adding a RT patches https://wiki.linuxfoundation.org/realtime/start in the build process. If you got lucky, no adjustments of the code will be needed. If none of that will help, notify WG author with your findings. Perhaps he has some clues.

0
Link to comment
Share on other sites
  • 0
Alex83

Alex83

Posted
Posted

Hi Igor, thanks for your quick and nice response. 

 

Unfortunately I am not able to compile by myself. 

 

I guess the problem is something which is easier to fix. With this variations of latency noone can use wireguard for any useful services. So I guess there is am easier solution. 

 

With my old TPlink Wr841 the same wireguard link works fine and with constant latency. Unfortunately if there is load the router is to slow to keep the low latency, so I thought best idea is let routers simply be routers with proprietary software nowadays and take powerful Arm devices for wireguard tunnel and routing the traffic through. 

 

Anyway, how can we find the root cause of the latency problems? 

 

I have more informations if it helps 

 

Edit: I guess it has something to do with the governor and the CPU profile. I tried changing it from ondemand to performance and conservative. Also I tried changing the frequency to 912 MHz minimum and 960 MHz maximum. Nothing changed with the ping times...  

 

root@bananapi:/# armbianmonitor -u
System diagnosis information will now be uploaded to /usr/b
n/armbianmonitor: line 385: read: read error: 0: Connection
timed out
/usr/bin/armbianmonitor: line 386: [: 46.8: integer express
on expected
http://ix.io/25P4
Please post the URL in the forum where you've been asked fo
.

root@bananapi:/#

 

0
Link to comment
Share on other sites
  • 0
Igor

Igor

Posted
Posted
5 hours ago, Alex83 said:

and take powerful Arm devices for wireguard tunnel and routing the traffic through.


Well, Bananapi M1 is not exactly very powerful, actually among slowest we support :P ... but it should probably handle this better. Have you at least try different kernel versions 4.19.y and 5.3.y?

0
Link to comment
Share on other sites
  • 0
Alex83

Alex83

Posted
Posted (edited)

Hey Igor, thank you very much for your answer. 

 

I tried what you suggested and ended up to set up the whole system new.

 

Now I bought a Banana Pi M2+ with 4x960MHz.

 

After long research I noticed that an iperf3 measurement achieve directly from the device through my wireguard tunnel nearly the gross bandwidth of 34 Mbit/s and when I route over the M2+ the bandwidth drops to 10 Mbit/s.

 

Spoiler 

 


- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   2.00-3.00   sec  2.90 MBytes  24.3 Mbits/sec

[  7]   2.00-3.00   sec  1.35 MBytes  11.3 Mbits/sec

[  9]   2.00-3.00   sec  1.86 MBytes  15.6 Mbits/sec

[ 11]   2.00-3.00   sec  3.36 MBytes  28.2 Mbits/sec

[SUM]   2.00-3.00   sec  9.47 MBytes  79.5 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   3.00-4.00   sec  3.08 MBytes  25.8 Mbits/sec

[  7]   3.00-4.00   sec  2.04 MBytes  17.1 Mbits/sec

[  9]   3.00-4.00   sec  2.99 MBytes  25.1 Mbits/sec

[ 11]   3.00-4.00   sec  1.51 MBytes  12.7 Mbits/sec

[SUM]   3.00-4.00   sec  9.63 MBytes  80.8 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   4.00-5.00   sec  1.75 MBytes  14.6 Mbits/sec

[  7]   4.00-5.00   sec  1.86 MBytes  15.6 Mbits/sec

[  9]   4.00-5.00   sec  3.26 MBytes  27.4 Mbits/sec

[ 11]   4.00-5.00   sec  2.54 MBytes  21.3 Mbits/sec

[SUM]   4.00-5.00   sec  9.41 MBytes  78.9 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   5.00-6.00   sec  1.95 MBytes  16.3 Mbits/sec

[  7]   5.00-6.00   sec  2.19 MBytes  18.4 Mbits/sec

[  9]   5.00-6.00   sec  3.18 MBytes  26.7 Mbits/sec

[ 11]   5.00-6.00   sec  2.26 MBytes  18.9 Mbits/sec

[SUM]   5.00-6.00   sec  9.57 MBytes  80.3 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   6.00-7.00   sec  1.93 MBytes  16.2 Mbits/sec

[  7]   6.00-7.00   sec  2.64 MBytes  22.1 Mbits/sec

[  9]   6.00-7.00   sec  2.63 MBytes  22.1 Mbits/sec

[ 11]   6.00-7.00   sec  2.40 MBytes  20.2 Mbits/sec

[SUM]   6.00-7.00   sec  9.60 MBytes  80.5 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   7.00-8.00   sec  1.91 MBytes  16.0 Mbits/sec

[  7]   7.00-8.00   sec  1.86 MBytes  15.6 Mbits/sec

[  9]   7.00-8.00   sec  2.83 MBytes  23.7 Mbits/sec

[ 11]   7.00-8.00   sec  3.29 MBytes  27.6 Mbits/sec

[SUM]   7.00-8.00   sec  9.88 MBytes  82.9 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   8.00-9.00   sec  2.87 MBytes  24.1 Mbits/sec

[  7]   8.00-9.00   sec  2.20 MBytes  18.5 Mbits/sec

[  9]   8.00-9.00   sec  1.93 MBytes  16.2 Mbits/sec

[ 11]   8.00-9.00   sec  2.79 MBytes  23.4 Mbits/sec

[SUM]   8.00-9.00   sec  9.79 MBytes  82.1 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]   9.00-10.00  sec  2.91 MBytes  24.4 Mbits/sec

[  7]   9.00-10.00  sec  2.12 MBytes  17.8 Mbits/sec

[  9]   9.00-10.00  sec  2.16 MBytes  18.1 Mbits/sec

[ 11]   9.00-10.00  sec  2.14 MBytes  17.9 Mbits/sec

[SUM]   9.00-10.00  sec  9.32 MBytes  78.2 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[  5]  10.00-10.01  sec  19.8 KBytes  29.1 Mbits/sec

[  7]  10.00-10.01  sec  5.66 KBytes  8.32 Mbits/sec

[  9]  10.00-10.01  sec  0.00 Bytes  0.00 bits/sec

[ 11]  10.00-10.01  sec  15.6 KBytes  22.9 Mbits/sec

[SUM]  10.00-10.01  sec  41.0 KBytes  60.2 Mbits/sec

- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bandwidth
[  5]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec
        sender
[  5]   0.00-10.01  sec  24.0 MBytes  20.1 Mbits/sec
          receiver
[  7]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec
        sender
[  7]   0.00-10.01  sec  22.0 MBytes  18.4 Mbits/sec
          receiver
[  9]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec
        sender
[  9]   0.00-10.01  sec  24.6 MBytes  20.6 Mbits/sec
          receiver
[ 11]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec
        sender
[ 11]   0.00-10.01  sec  24.6 MBytes  20.7 Mbits/sec
          receiver
[SUM]   0.00-10.01  sec  0.00 Bytes  0.00 bits/sec
        sender
[SUM]   0.00-10.01  sec  95.1 MBytes  79.8 Mbits/sec
          receiver
-----------------------------------------------------------
Server listening on 5201
-----------------------------------------------------------

 

 

Here is the measurement from my device which is routed to the m2+

 

If you measure straight to M2+ it transmits in both directions around 82 Mbit/s and that is OK because of a 100 Mbit/s switch in between. I also tried it straight with 1 Gbe but the transmit through the tunnel is still 10 MBit/s average. 

 

The interesting thing is in the first second of measurement it's also 31 Mbit/s, second is 0 and then it continues which 7 to 10.

 

It is so annoying and strange.... 

 

Edited by TRS-80
put long output inside spoiler
0
Link to comment
Share on other sites
  • 0
ChriWo

ChriWo

Posted
Posted

Hello,

 

I'm trying to install wireguard on my HC1 with Linux 5.4.94-odroidxu4 but I cannot get it to work if 

 

here is the output:

 

root@hc1:~# apt-get install wireguard

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

 

The following packages have unmet dependencies:

wireguard : Depends: wireguard-tools (>= 1.0.20200827-1~bpo10+1) but 1.0.20200513-1~bpo10+1 is to be installed

E: Unable to correct problems, you have held broken packages.

 

Can anyone help me?

 

Regards

ChriWo

0
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to question listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept