Jump to content


Photo

Request for WireGuard VPN implementation

WireGuard VPN

  • Please log in to reply
107 replies to this topic

Re: Request for WireGuard VPN implementation #61 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 27 October 2020 - 21:50

We'll see how it goes.

 

I've prepared all PR's and am about the send them out, I expect Neo to do the rest soon as well.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #62 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 28 October 2020 - 11:49

Fingers crossed.


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Request for WireGuard VPN implementation #63 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 28 October 2020 - 15:23

Just did a BSP update, still waiting for a few vendors to merge the PR's.

 

A test build is running, which probably takes about 2-3 days, given the fact that the changes will cause a full kernel rebuild, which in turn will trigger a rebuild of anything kernel related.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #64 AllMassive

  • Member
  • 21 posts

0
Neutral

Posted 4 November 2020 - 03:42

nice - thank you so much for your efforts.

/me keeps his fingers and toes crossed.



Re: Request for WireGuard VPN implementation #65 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 4 November 2020 - 03:46

We're down to two manufacturers, the others have merged, and the builds went fine.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #66 AllMassive

  • Member
  • 21 posts

0
Neutral

Posted 6 November 2020 - 09:01

I'm so happy that you have managed to achieve this.

Since i mainly use VU+ - are there already downloadable Images available which include wireguard?

 

 



Re: Request for WireGuard VPN implementation #67 Frenske

  • Forum Moderator
    PLi® Core member
  • 27,394 posts

+394
Excellent

Posted 6 November 2020 - 10:59

AFAIK this is only committed in Develop. As soon as OpenPLi 8 is public then this is available for all.


Mijn schotel is een T90 met 10 LNB's. Daarnaast voor de fun nog een draaibaar systeem met een Triax TD 78.

Dreamboxen heb ik niet meer echt actief. Verder heb ik ook nog een een VU+ duo2 met 500Gb harddisk + een VU+ Uno, Zero, Solo 4K, Ultimo 4K, Zero 4K, Uno 4Kse. + ook nog een Xtrend ET7x00. Daarnaast heb ik ook nog diverse andere modellen w.o. een Formuler F4, ET8500, ET7500, Mut@nt 2400HD, Xsarius Fusion HD se en verder nog wel het e.e.a. waarmee op verzoek vanalles wordt getest. Iemand moet het tenslotte doen. ;) :)
Los van de eerder genoemde modellen heb ik nog wel een rits aan testsamples als Mut@nt 2400HD, HD60, GB UE4K, GB Trio4K, Maxitec Multibox combo en Twin, Octagon sf8008, sf8008 mini en last but nog least enkele modellen van het Grieks Duitse Edision.

Voor centrale opslag van media gebruik ik een Qnap 219P 
met tweemaal 2 Tb harddisks + een Synology DS414 met 12 Tb Totale opslag.

-------------------------------------------------------------------------------------------
Many answers to your question can be found in our wiki: Just one click away from this "solutioncentre".

Als ik alles al wist hoefde ik ook niets te vragen. If I had all the knowledge I had no questions at all.


Re: Request for WireGuard VPN implementation #68 dolphs

  • Senior Member
  • 983 posts

+8
Neutral

Posted 7 November 2020 - 08:41

I sincerely doubt it.

For starters, no box currently runs on 5.6, and most never will.

And as long as most endpoints (NAS boxes, routers, firewalls) don't support it, it will not catch on very quickly.

 

 

Great to see views appeared to be changed, might raiseET8000 from the ranks ( not sure about kernel and accompanying modules bu will see ),

Also my good old, but still working, Vu+ solo ( Linux vusolo 3.9.6 #1 Wed Jul 1 11:39:10 CEST 2020 mips GNU/Linux ), should be upgraded to at least 7.3 I suppose.

Will see anytime soon, cheers chaps!



Re: Request for WireGuard VPN implementation #69 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 7 November 2020 - 14:18

OpenPLi 8 will have wireguard support for:

./alphatriplehd/kernel-module-wireguard-4.1.24_1.0.20200413-r0.11_alphatriplehd.ipk
./e4hd/kernel-module-wireguard-4.10.12_1.0.20200413-r0.9_e4hd.ipk
./et10000/kernel-module-wireguard-4.10.6_1.0.20200413-r0.13_et10000.ipk
./et1x000/kernel-module-wireguard-4.1.37_1.0.20200413-r0.11_et1x000.ipk
./et4x00/kernel-module-wireguard-4.10.6_1.0.20200413-r0.13_et4x00.ipk
./et7000mini/kernel-module-wireguard-4.1.21_1.0.20200413-r0.12_et7000mini.ipk
./et7x00/kernel-module-wireguard-4.4.8_1.0.20200413-r0.12_et7x00.ipk
./et8000/kernel-module-wireguard-4.10.6_1.0.20200413-r0.13_et8000.ipk
./et8500/kernel-module-wireguard-4.4.8_1.0.20200413-r0.12_et8500.ipk
./formuler1/kernel-module-wireguard-4.10.6_1.0.20200413-r0.11_formuler1.ipk
./formuler3/kernel-module-wireguard-4.10.6_1.0.20200413-r0.11_formuler3.ipk
./formuler4/kernel-module-wireguard-4.10.6_1.0.20200413-r0.11_formuler4.ipk
./formuler4turbo/kernel-module-wireguard-4.10.6_1.0.20200413-r0.11_formuler4turbo.ipk
./fusionhd/kernel-module-wireguard-4.2.1_1.0.20200413-r0.8_fusionhd.ipk
./fusionhdse/kernel-module-wireguard-4.2.1_1.0.20200413-r0.8_fusionhdse.ipk
./galaxy4k/kernel-module-wireguard-3.14.28_1.0.20200413-r0.9_galaxy4k.ipk
./gbquad4k/kernel-module-wireguard-4.1.20-1.9_1.0.20200413-r0.9_gbquad4k.ipk
./gbtrio4k/kernel-module-wireguard-4.4.35_1.0.20200413-r0.12_gbtrio4k.ipk
./gbue4k/kernel-module-wireguard-4.1.20-1.9_1.0.20200413-r0.9_gbue4k.ipk
./h10/kernel-module-wireguard-4.4.35_1.0.20200413-r0.13_h10.ipk
./h3/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_h3.ipk
./h4/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_h4.ipk
./h5/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_h5.ipk
./h6/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_h6.ipk
./h7/kernel-module-wireguard-4.10.12_1.0.20200413-r0.11_h7.ipk
./h9/kernel-module-wireguard-4.4.35_1.0.20200413-r0.14_h9.ipk
./h9combo/kernel-module-wireguard-4.4.35_1.0.20200413-r0.14_h9combo.ipk
./hd11/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd11.ipk
./hd1100/kernel-module-wireguard-4.10.12_1.0.20200413-r0.9_hd1100.ipk
./hd1200/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd1200.ipk
./hd1265/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd1265.ipk
./hd1500/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd1500.ipk
./hd2400/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd2400.ipk
./hd500c/kernel-module-wireguard-4.10.12_1.0.20200413-r0.9_hd500c.ipk
./hd51/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd51.ipk
./hd530c/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_hd530c.ipk
./hd60/kernel-module-wireguard-4.4.35_1.0.20200413-r0.11_hd60.ipk
./i55/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_i55.ipk
./i55plus/kernel-module-wireguard-4.4.35_1.0.20200413-r0.14_i55plus.ipk
./lc/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_lc.ipk
./lunix/kernel-module-wireguard-4.2.1_1.0.20200413-r0.7_lunix.ipk
./lunix3_4k/kernel-module-wireguard-3.14.28_1.0.20200413-r0.7_lunix3_4k.ipk
./lunix4k/kernel-module-wireguard-4.1.20_1.0.20200413-r0.7_lunix4k.ipk
./mbmicro/kernel-module-wireguard-4.0.1_1.0.20200413-r0.11_mbmicro.ipk
./mbmicrov2/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_mbmicrov2.ipk
./mbtwinplus/kernel-module-wireguard-4.1.24_1.0.20200413-r0.11_mbtwinplus.ipk
./multibox/kernel-module-wireguard-4.4.35_1.0.20200413-r0.12_multibox.ipk
./osmega/kernel-module-wireguard-4.11.0_1.0.20200413-r0.10_osmega.ipk
./osmini/kernel-module-wireguard-4.11.0_1.0.20200413-r0.10_osmini.ipk
./osmini4k/kernel-module-wireguard-5.5.16_1.0.20200413-r0.6_osmini4k.ipk
./osmini4k/kernel-module-wireguard-5.9.0_5.9-r0.4_osmini4k.ipk
./osminiplus/kernel-module-wireguard-4.11.0_1.0.20200413-r0.10_osminiplus.ipk
./osmio4k/kernel-module-wireguard-5.9.0_5.9-r0.4_osmio4k.ipk
./osmio4k/kernel-module-wireguard-5.5.16_1.0.20200413-r0.6_osmio4k.ipk
./osmio4kplus/kernel-module-wireguard-5.5.16_1.0.20200413-r0.6_osmio4kplus.ipk
./osmio4kplus/kernel-module-wireguard-5.9.0_5.9-r0.4_osmio4kplus.ipk
./osnino/kernel-module-wireguard-4.8.17_1.0.20200413-r0.10_osnino.ipk
./osninoplus/kernel-module-wireguard-4.8.17_1.0.20200413-r0.10_osninoplus.ipk
./osninopro/kernel-module-wireguard-4.8.17_1.0.20200413-r0.10_osninopro.ipk
./purehd/kernel-module-wireguard-4.2.1_1.0.20200413-r0.8_purehd.ipk
./purehdse/kernel-module-wireguard-4.2.1_1.0.20200413-r0.8_purehdse.ipk
./revo4k/kernel-module-wireguard-3.14.28_1.0.20200413-r0.9_revo4k.ipk
./sf8008/kernel-module-wireguard-4.4.35_1.0.20200413-r0.14_sf8008.ipk
./sf8008m/kernel-module-wireguard-4.4.35_1.0.20200413-r0.8_sf8008m.ipk
./sh1/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_sh1.ipk
./spycat/kernel-module-wireguard-4.11.0_1.0.20200413-r0.11_spycat.ipk
./spycatmini/kernel-module-wireguard-4.11.0_1.0.20200413-r0.10_spycatmini.ipk
./spycatminiplus/kernel-module-wireguard-4.11.0_1.0.20200413-r0.10_spycatminiplus.ipk
./ustym4kpro/kernel-module-wireguard-4.4.35_1.0.20200413-r0.7_ustym4kpro.ipk
./vipercombo/kernel-module-wireguard-4.10.6_1.0.20200413-r0.9_vipercombo.ipk
./vipercombohdd/kernel-module-wireguard-4.10.6_1.0.20200413-r0.9_vipercombohdd.ipk
./viperslim/kernel-module-wireguard-4.10.6_1.0.20200413-r0.9_viperslim.ipk
./vipert2c/kernel-module-wireguard-4.10.6_1.0.20200413-r0.9_vipert2c.ipk
./vs1000/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_vs1000.ipk
./vs1500/kernel-module-wireguard-4.10.12_1.0.20200413-r0.10_vs1500.ipk
./vuduo4k/kernel-module-wireguard-4.1.45-1.17_1.0.20200413-r0.12_vuduo4k.ipk
./vuduo4kse/kernel-module-wireguard-4.1.45-1.17_1.0.20200413-r0.4_vuduo4kse.ipk
./vusolo4k/kernel-module-wireguard-3.14.28-1.8_1.0.20200413-r0.9_vusolo4k.ipk
./vuultimo4k/kernel-module-wireguard-3.14.28-1.12_1.0.20200413-r0.9_vuultimo4k.ipk
./vuuno4k/kernel-module-wireguard-3.14.28-1.12_1.0.20200413-r0.9_vuuno4k.ipk
./vuuno4kse/kernel-module-wireguard-4.1.20-1.9_1.0.20200413-r0.11_vuuno4kse.ipk
./vuzero4k/kernel-module-wireguard-4.1.20-1.9_1.0.20200413-r0.11_vuzero4k.ipk
./xp1000/kernel-module-wireguard-4.10.12_1.0.20200413-r0.9_xp1000.ipk
./xpeedc/kernel-module-wireguard-4.1.21_1.0.20200413-r0.11_xpeedc.ipk

 


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #70 AllMassive

  • Member
  • 21 posts

0
Neutral

Posted 25 November 2020 - 02:19

Just stumbled about the Versioning.

 

/vuuno4kse/kernel-module-wireguard-4.1.20-1.9_1.0.20200413-r0.11_vuuno4kse.ipk

 

On Debian/Arch the Wireguard-Version is currently at 1.0.20201112.

 



Re: Request for WireGuard VPN implementation #71 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 25 November 2020 - 02:42

Quite possible. But that is not going into OpenPLi 8.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #72 Erik Slagter

  • PLi® Core member
  • 46,951 posts

+541
Excellent

Posted 26 November 2020 - 10:22

Now if this version would bring a ground-breaking world-changing feature or bugfix we could try to backport it. But probably not, so sense in always trying to have the latest version "because of".


* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.


Re: Request for WireGuard VPN implementation #73 ReceiverM

  • Member
  • 14 posts

0
Neutral

Posted 11 December 2020 - 13:56

@WanWizard mentioned ./multibox/kernel-module-wireguard-4.4.35_1.0.20200413-r0.12_multibox.ipk as supported in OpenPLI8.

 

So I downloaded the newest release candidate for maxytec, flashed it and tried to install wireguard.

 

I tried like everything, but always got the same error:

[#] ip link add wg0 type wireguard
RTNETLINK answers: Operation not supported
Unable to access interface: Protocol not supported

 

Literally tried everything in opkg list | grep wireguard + additional stuff (like new iptables etc.) looked up in wireguard dependencies.

But nothing helped.

 

Btw. thats the exact same behavior as in openatv.
 

 

Any hints to get wireguard running?
Thx :)

 

\\EDIT: Do I need kernel-module-xt-hashlimit ? Cause its not in the feed.


Edited by ReceiverM, 11 December 2020 - 13:58.


Re: Request for WireGuard VPN implementation #74 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 11 December 2020 - 13:59

Did you do a "modprobe wireguard" to load the driver?


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #75 ReceiverM

  • Member
  • 14 posts

0
Neutral

Posted 11 December 2020 - 14:26

Fast reply :)

 

root@maxytecmulti:~# modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': Unknown symbol in module, or unknown parameter (see dmesg)

root@maxytecmulti:~# dmesg
wireguard: Unknown symbol udp_sock_create4 (err 0)
wireguard: Unknown symbol udp_tunnel6_xmit_skb (err 0)
wireguard: Unknown symbol udp_tunnel_sock_release (err 0)
wireguard: Unknown symbol setup_udp_tunnel_sock (err 0)
wireguard: Unknown symbol udp_sock_create6 (err 0)
wireguard: Unknown symbol udp_tunnel_xmit_skb (err 0)


 



Re: Request for WireGuard VPN implementation #76 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 11 December 2020 - 14:29

Is this 8.0-rc? Or 7.3?

 

I thought this was fixed for all boxes with a BSP update from the vendor...


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #77 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 11 December 2020 - 14:44

The kernel driver udp-tunnel is missing, even though the defconfig in the BSP says it should be build. Looking at it.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #78 ReceiverM

  • Member
  • 14 posts

0
Neutral

Posted 11 December 2020 - 14:46

Yes 8.0-rc - flashed it once again and tried:

 

 

opkg update && opg upgrade
...

root@multibox:~# opkg list | grep wireguard
kernel-module-wireguard - 1.0.20200413-r0.0 - WireGuard is an extremely simple yet fast and modern VPN
kernel-module-wireguard-4.4.35 - 1.0.20200413-r0.0 - wireguard kernel module
wireguard-module-dbg - 1.0.20200413-r0.0 - WireGuard is an extremely simple yet fast and modern VPN - Debugging files
wireguard-module-dev - 1.0.20200413-r0.0 - WireGuard is an extremely simple yet fast and modern VPN - Development files
wireguard-tools - 1.0.20200319-r0.0 - WireGuard is an extremely simple yet fast and modern VPN
wireguard-tools-bash-completion - 1.0.20200319-r0.0 - WireGuard is an extremely simple yet fast and modern VPN
wireguard-tools-dbg - 1.0.20200319-r0.0 - WireGuard is an extremely simple yet fast and modern VPN - Debugging files
wireguard-tools-dev - 1.0.20200319-r0.0 - WireGuard is an extremely simple yet fast and modern VPN - Development files
wireguard-tools-doc - 1.0.20200319-r0.0 - WireGuard is an extremely simple yet fast and modern VPN - Documentation files

root@multibox:~# opkg install wireguard-tools
Installing kernel-module-wireguard-4.4.35 (1.0.20200413) on root
Downloading http://downloads.ope....0_multibox.ipk.
Installing wireguard-tools (1.0.20200319) on root
Downloading http://downloads.ope...-neon-vfpv4.ipk.
Configuring kernel-module-wireguard-4.4.35.
Configuring wireguard-tools.

root@multibox:~# modprobe wireguard
modprobe: ERROR: could not insert 'wireguard': Unknown symbol in module, or unknown parameter (see dmesg)

root@multibox:~# dmesg
wireguard: Unknown symbol udp_sock_create4 (err 0)
wireguard: Unknown symbol udp_tunnel6_xmit_skb (err 0)
wireguard: Unknown symbol udp_tunnel_sock_release (err 0)
wireguard: Unknown symbol setup_udp_tunnel_sock (err 0)
wireguard: Unknown symbol udp_sock_create6 (err 0)
wireguard: Unknown symbol udp_tunnel_xmit_skb (err 0)


 

 

I just saw that a new version was uploaded two hours ago. Does this help?

Or the new recovery?



Re: Request for WireGuard VPN implementation #79 WanWizard

  • PLi® Core member
  • 68,588 posts

+1,738
Excellent

Posted 11 December 2020 - 15:18

No, as I wrote before, for some reason the udp-tunnel driver isn't being build.


Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Pro (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)

Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.

Many answers to your question can be found in our new and improved wiki.


Re: Request for WireGuard VPN implementation #80 ReceiverM

  • Member
  • 14 posts

0
Neutral

Posted 11 December 2020 - 15:38

Not quite but must it be = m or = y in this commit https://github.com/O...2bdeb40b79ce50a ?




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users