Beta Asuswrt-Merlin 386.3 beta is now available

[Clark Griswald]

RE: VPN Director
Disclosure, previously I have not run a vpn on router and I do not currently use any vpn service. I have been watching the VPN Director thread to current beta. I read the quirks of specific services getting quick fixes (as usual) by RMerlin!
My question to the VPN Director users
Would you say this is Griswald proof

Edit: @jsbeddow Casa Griswald has been utilizing the QR addition, since introduced
We have used a vpn, just not on router. I even watched This Thread but didn't want The Wife to ask:
What's your father doing?
His reading about accessing pornhub

 

[L&LD]

Clark, Clark! Nothing is Griswald proof!

But this is as close as it gets.

 

[jsbeddow]

RE: VPN Director
Disclosure, previously I have not run a vpn on router and I do not use any vpn service. I have been watching the VPN Director thread to current beta. I read the quirks of specific services getting quick fixes (as usual) by RMerlin!
My question to the VPN Director users
Would you say this Griswald proof

All kidding aside, if you aren't using any VPN client configuration, the only portion of this upgrade that will be visible to you will be the QR code generators for the WiFi passwords. Pretty safe, as all of the other updates are to underlying services (not visible UI elements).

 

[Howard_inGA]

Easy upgrade. Only change was to route all traffic through VPN to keep out leaks. Otherwise, flawless!!
Thanks, Eric!

 

[atomicRPM]

Installed beta on a two unit RT-AX86U mesh. No issues here.

 

[John Fitzgerald]

Clark, Clark! Nothing is Griswald proof!

But this is as close as it gets.

Cousin Eddie is pulling up in the drive now to help!

 

[Deleted member 62525]

Experiencing problems with Unbound and 386.3 beta, doesn't seem to work for me, anyone else?

It would help if you give us more details. Run unbound -d and check the log. Post it here.

 

[Clark Griswald]

Thank you for the responses, should have learned by this time, RMerlin "beta" is Good To Go!
I will experiment with VPN Director in the middle of the night, so I don't disturb the gentle nature of my Family's Internet Experience.

 

[HeadBanger]

Looks like ASUS have changed some other bits of code as their AiMesh is partly broken for me with this release.

I have AX88U with two AX86U nodes - one wired one 5G backhaul.

With 386.3 the 5G node falls back to 2.4G backhaul after 12-24 hours (same with official ASUS 386.3). A reboot fires up 5G backhaul but this just repeats. 5G backhaul under 386.2 works fine without issues. Strength is reported by AiMesh as ‘good’ at around -62dB.

I know this is all closed source and Merlin won’t be able to fix this so staying on 386.2 for now.

HB

 

[L&LD]

@HeadBanger, flash all to the 386.3 Beta 1 and then reset the nodes. Then re-associate each one.

Their settings need to be updated to the new changes.

 

[dave14305]

Looks like ASUS have changed some other bits of code as their AiMesh is partly broken for me with this release.

I have AX88U with two AX86U nodes - one wired one 5G backhaul.

With 386.3 the 5G node falls back to 2.4G backhaul after 12-24 hours (same with official ASUS 386.3). A reboot fires up 5G backhaul but this just repeats. 5G backhaul under 386.2 works fine without issues. Strength is reported by AiMesh as ‘good’ at around -62dB.

I know this is all closed source and Merlin won’t be able to fix this so staying on 386.2 for now.

HB

What minor version of 386.2? There were no Asus component updates between 386.2_6 and 386.3.

 

[RMerlin]

How good Are they at keeping their GPL releases in line with binary release

It varies. Sometimes it's out the next day, sometimes it takes 2 months. In my case it's different, as they build special tarballs for me (as I need the same codebase for all supported models, so they generate GPL releases even for models which didn't get a firmware release for that specific codebase). GPL releases have been on hold for a few weeks now as they need to address some issues with the generated archives.

I was looking at your source and correct me if I'm wrong but it seems like All I'd have to do is overwrite some precompiled binaries and headers .

It's not that simple. For instance, a firmware image contains fully linked kernel modules (*.ko files), while for building a firmware you need the pre-linked object files (*.o). You need the actual GPL archives with those object files so they can be properly linked within the generated firmware filesystem. And a lot of components interact with one another, so you can't just blindly replace one single file, and expect it to work properly. SDK changes for instance may also require code changes within libshared or rc, which will require the proprietary object files that have been generated to work with that updated SDK. Trying to do that kind of frankenbuilding is generally a large waste of time, and I don't want to do it anymore.

 

[Maasamda]

It would help if you give us more details. Run unbound -d and check the log. Post it here.

Sorry for the late response. Fixed the problem with new install. Thx for follow up!

 

[HeadBanger]

@HeadBanger, flash all to the 386.3 Beta 1 and then reset the nodes. Then re-associate each one.

Their settings need to be updated to the new changes.

OK thanks - I will give that a try tomorrow.

HB

 

[HeadBanger]

What minor version of 386.2? There were no Asus component updates between 386.2_6 and 386.3.

386.2_6 on the AX86U nodes is fine and 5G backhaul is solid. Any version of 386.3 (ASUS or Merlin) results in back haul dropping to 2.4G.

I will try L&LD’s suggestion tomorrow.

HB

 

[Pitchounet]

Great QR-Code option! Very cool and very good idea.

 

[RMerlin]

386.2_6 on the AX86U nodes is fine and 5G backhaul is solid. Any version of 386.3 (ASUS or Merlin) results in back haul dropping to 2.4G.

386.3 Wifi code is 100% identical to 386.2_6.

 

[SomeWhereOverTheRainBow]

386.3 Wifi code is 100% identical to 386.2_6.

By how much identical are we talking? is it identical to 386.1 as well? Because I am sure I remember you committing this acsd driver update/addition

HND502ax-675x: Update acsd · RMerl/asuswrt-merlin.ng@b638371

Third party firmware for Asus routers (newer codebase) - HND502ax-675x: Update acsd · RMerl/asuswrt-merlin.ng@b638371

github.com

That is the only thing I could think maybe caused buggy stability issues. Acsd restarting. But this would require LOGS to identify. Not "oh hey my AiMesh is acting up."

 

[RMerlin]

By how much identical are we talking? is it identical to 386.1 as well?

No. I said 386.2_6, and I did mean 386.2_6. 386.2_6 contained SDK changes for the Fragattack fixes, and 386.2_0 contained the 386_42095 GPL merge.

Because I am sure I remember you committing this acsd driver update/addition

That was part of the fragattack patches of 386.2_6. Acsd only handles automatic channel selection.

 

[SomeWhereOverTheRainBow]

No. I said 386.2_6, and I did mean 386.2_6. 386.2_6 contained SDK changes for the Fragattack fixes, and 386.2_0 contained the 386_42095 GPL merge.


That was part of the fragattack patches of 386.2_6. Acsd only handles automatic channel selection.

My main point is that maybe the user should inspect their logs around the time issues arise, if it seems non-firmware related, create a new thread asking about the discovered issues found in their logs.