386.5 Alpha1?

[shabbs]

I wouldn't get too overly excited: for any of us that already installed the 386.5 Alpha 2, I don't see any changes on Github in the less than 72 hours since the release of that version. Yes, support was completed for the new AX-11000, but if your model was already included in Alpha 2, there were no changes.

Yeah figured it was likely just a rev bump.

 

[aex.perez]

Been running 386.5 alpha1 on the AX88 and both AX86 AImesh nodes, for a week or so.

WAN:
Under 386.4 lost WAN connectivity randomly, only happened a couple of times. The only way I found to recover from it, even with SCMerlin restarting WAN, was a reboot. The AT&T Gateway during the loss of WAN Connectivity was all green, using a backup wired connection I have on the Gateway, still had connectivity. Have not seen that happen yet under 386.5 alpha 1

WiFi:
The other issue is with WiFi, where my Nest cams, Android Tablets I use to monitor them were dropping connectivity randomly. After going through the Router settings, and not seeing anything standing out. All the other devices using WiFI seemed fine. After rebooting the Tablets the connectivity has been solid.

Upgrade:
Dirty upgrade, flawless. Found a quiet morning on the weekend as the family was sleeping and not watching TV, took about 15m to hit the nodes, then the router, best part

Got alpha 2 loaded up earlier today, and it's been solid as well. Jumping on the Beta later this evening after Wife's Telenovelas

 

[Ubimo]

The Bandwidth Monitor page requires certain Trend Micro components to temporarily load in order to gather the per-device and App Analysis data. When Adaptive QoS is enabled, no extra action is required, so no log messages would appear. When it’s not enabled, it loads what it needs and forces QoS and the Firewall to restart.

Thank you for the explanation.
I've enabled Adaptive QoS (Cake) and this is still happening.
Every time I click on the "Adaptive QoS" button, the log messages appear. (firewall restart etc.)
Can anyone confirm this behaviour? I don't think that this is normal?

 

[dave14305]

I've enabled Adaptive QoS (Cake) and this is still happening.

Cake is not Adaptive QoS.

 

[Ubimo]

OK, so I can express myself correctly:
I've enabled QoS Cake.
Now, I still get these log entries, by only clicking on the "Adaptive QoS" button in the GUI.
Is that a normal behaviour? I mean, why all these entries and firewall restart, by only clicking on this "Adaptive QoS" menu button?

 

[dave14305]

Is that a normal behaviour? I mean, why all these entries and firewall restart, by only clicking on this "Adaptive QoS" menu button?

Yes, it’s normal for the reasons I mentioned in my other post. Normal, but not desirable.

 

[zakfromevil]

Hello to all. Anyone can help me, I need firmware RT-AX86U 386.5_alpha1-g67f583ce46, I don't save it when flashed up new 386.5 (on this build VPN doesn't work correctly for me)

 

[eibgrad]

Hello to all. Anyone can help me, I need firmware RT-AX86U 386.5_alpha1-g67f583ce46, I don't save it when flashed up new 386.5 (on this build VPN doesn't work correctly for me)

You want to go back to an *alpha* build due to an issue w/ the release?! Wouldn't it make a lot more sense to either find the problem w/ the release, or go back to the prior release? IMO, no alpha build should ever be used in a production environment, even a home environment.

 

[zakfromevil]

I used VPN antizapret, and on alpha1 it works about month without problems for torrents and other blocked sites, and on newer 386.5 it doesn't work normally

 

[eibgrad]

I used VPN antizapret, and on alpha1 it works about month without problems for torrents and other blocked sites, and on newer 386.5 it doesn't work normally

Then you should start a new thread, post the details, and see if anyone can help you figure out the problem. Resorting to an alpha build is NOT recommended. Whatever problems you found w/ the 386.5 release are likely to persist well beyond it. So you don't want to be left permanently stuck on an alpha build.

 

[zakfromevil]

Then you should start a new thread, post the details, and see if anyone can help you figure out the problem. Resorting to an alpha build is NOT recommended. Whatever problems you found w/ the 386.5 release are likely to persist well beyond it. So you don't want to be left permanently stuck on an alpha build.

problems starts since 386.4, and only alpha was good for me. My question just about link for alpha firmware if anyone have it, may be in PM