What's new

[ 386.4 alpha Build(s) ] Testing available build(s)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Quick question: Is Asus implementation of Wireguard included in this version?

If you have latest scMerlin add-on you will see that WireGuard is in fact "lurking under the hood" - probably because it is in the stock GPL 386-45581 which has never been released as a compiled firmware version for any Asus Routers.

ASUS Wireless Router RT-AX86U - Network Map.png


These are "hidden" URL's from the normal webui released with Alpha2v3 - and are only visible under scMerlin.

I assume @RMerlin has no intention of supporting WireGuard at this time.
There was hardly any response from anyone when he asked a question about WireGuard use in another thread dealing with Asus stock releases which included WireGuard.
 
It is rumored to be in the RC3 release, but only for certain routers. Hence the answer given.

If the OP's router is compatible, there is the Wireguard Manager addon as well that can be expored.
 
Wireguard is not enabled in these builds because it's based on older beta code. These are just links to the old test pages, the kernel and userspace tools are not compiled in.
 
Had to revert on an AX-68U AIMesh node as it was going offline repeatedly. Reverted to stock firmware and stable so far.
 
Had to revert on an AX-68U AIMesh node as it was going offline repeatedly. Reverted to stock firmware and stable so far.
I have three AIMesh routers, one of which is an AX-68U. My main router is using Merlin (alpha 2), but I've always run the AIMesh units with Asus firmware. I'm having no problems with my mesh system using this scheme. Can't really see the point of Merlin on an AImesh unit.
 
Wireguard is not enabled in these builds because it's based on older beta code. These are just links to the old test pages, the kernel and userspace tools are not compiled in.
I just scored myself an (almost new) RT-AX86 for $50.00 CDN reset it & upgraded it to the latest Asus STOCK Firmware version 3.0.0.4.386.45898.
I didn't notice a BETA status within that software & quickly glanced at Wireguard just by checking for it.
So I'm somewhat surprised to hear you say "it's based on older beta code"
Anyways I was somewhat excited to try Wireguard for it's apparent speed increase & simplicity over OpenVPN...
But my usage-case will also require AsusWRT-Merlin.

Do you think Wireguard will be included in the NEAR future?
I understand that you are not a fortune-teller... but you are somewhat of a Wizard when it comes to firmware & most of these devices ;-)

Anyways Thanks again for the hard work & continued efforts.
All the Best
 
I just scored myself an (almost new) RT-AX86 for $50.00 CDN reset it & upgraded it to the latest Asus STOCK Firmware version 3.0.0.4.386.45898.
I didn't notice a BETA status within that software & quickly glanced at Wireguard just by checking for it.
So I'm somewhat surprised to hear you say "it's based on older beta code"
Anyways I was somewhat excited to try Wireguard for it's apparent speed increase & simplicity over OpenVPN...
But my usage-case will also require AsusWRT-Merlin.

Do you think Wireguard will be included in the NEAR future?
I understand that you are not a fortune-teller... but you are somewhat of a Wizard when it comes to firmware & most of these devices ;-)

Anyways Thanks again for the hard work & continued efforts.
All the Best

@capncybo

Check this addon. Your router may (may) be able to use it

 
I have three AIMesh routers, one of which is an AX-68U. My main router is using Merlin (alpha 2), but I've always run the AIMesh units with Asus firmware. I'm having no problems with my mesh system using this scheme. Can't really see the point of Merlin on an AImesh unit.

Yeah - I've had it both ways at times - this has always been a bit of a bar-room conversation, though.
 
So I'm somewhat surprised to hear you say "it's based on older beta code"
Asus is working on Wireguard in their RC3 branch (386_5xxxx). This Alpha is based on the RC2 branch (386_4xxxx) which contains early Wireguard code that predates RC3 where they are currently continuing its development

Do you think Wireguard will be included in the NEAR future?
No.
 
Asus is working on Wireguard in their RC3 branch (386_5xxxx). This Alpha is based on the RC2 branch (386_4xxxx) which contains early Wireguard code that predates RC3 where they are currently continuing its development


No.
I appreciate the clarification & honesty. I guess to satisfy my curiosity... I can "potentially" play with wireguard via entware. But so much for simplicity, Mehhh Simple is soooo boring. LOL
 
I appreciate the clarification & honesty. I guess to satisfy my curiosity... I can "potentially" play with wireguard via entware. But so much for simplicity, Mehhh Simple is soooo boring. LOL
The reason is that since Asus is still in beta stage on that code in the RC3 branch, that means they will first need to finalize it on their end (which can probably take a few weeks, if not a few months). Once that's done, I will need to merge that newer RC3 5xxxx code into my repo. And I will need to develop a web UI for it (since I cannot share the same VPN interface as Asus), plus the integration into VPN Director. So we have to wait for all of these to happen.

I might possibly start compiling with the userspace tools + kernel module enabled before that, which would at least allow third party developers to directly leverage it instead of having to install these through Entware. But a complete firmware integration is still a few months away on my end.
 
I have a strange problem with 386.4-alpha2-ga85421da82.

My file in /jffs/scripts/openvpn-even dissapear from time to time. I put it back and under coming day it get erased.
I have made a script to put it back every 10min. I have a copy in /jffs/openvpn-event and that get erased too.
I renamed it to open-event and renamed it when i move it to /jffs/scripts/ directory and that working.

cp /jffs/open-event /jffs/scripts/openvpn-event

Have anyone else seen this behave or are I'm hacked? I doubt it.
Or something new in alpha-build get it erased.
 
I have a strange problem with 386.4-alpha2-ga85421da82.

My file in /jffs/scripts/openvpn-even dissapear from time to time. I put it back and under coming day it get erased.
I have made a script to put it back every 10min. I have a copy in /jffs/openvpn-event and that get erased too.
I renamed it to open-event and renamed it when i move it to /jffs/scripts/ directory and that working.



Have anyone else seen this behave or are I'm hacked? I doubt it.
Or something new in alpha-build get it erased.
I wonder if Asus' security daemon is going overboard again?
 
The reason is that since Asus is still in beta stage on that code in the RC3 branch, that means they will first need to finalize it on their end (which can probably take a few weeks, if not a few months). Once that's done, I will need to merge that newer RC3 5xxxx code into my repo. And I will need to develop a web UI for it (since I cannot share the same VPN interface as Asus), plus the integration into VPN Director. So we have to wait for all of these to happen.

I might possibly start compiling with the userspace tools + kernel module enabled before that, which would at least allow third party developers to directly leverage it instead of having to install these through Entware. But a complete firmware integration is still a few months away on my end.
Gotta love a Man with a Plan... it actually sounds like a fun project. Hopefully you get some help along the way. I'm Looking forward to seeing it develop, but no-rush (on my part anyway).
 
Wireguard is not enabled in these builds because it's based on older beta code. These are just links to the old test pages, the kernel and userspace tools are not compiled in.
...YET.
And when they are, I'm sure they'll be current.
 
Status
Not open for further replies.

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top