What's new

[ 386.7 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!

Did you brick your RT-AX86U when upgrading to 386.7 Alpha1


  • Total voters
    26
  • Poll closed .
Status
Not open for further replies.
Why do you say that?

We're talking about software development here. Bugs happen, and they require time to be resolved.

Sure, I can wait, I understand that supporting 40 models is too much, on that I meant that they do not give you an easy life, I was used to new versions coming out more quickly, honestly in the past I was more enthusiastic about the new features, now a little less, also due to some new bugs which you do not like to encounter or expect. (RT-AX88U)
 
Dirty flash to my router and node. Node seemed to reboot or wireless went down after about 10 mins after flash but seems stable after an hour (router) and 50 mins (node). Noticed the wireless driver has been updated again to May 7.
 
Any ETA for other models i got 2 that need updating ? I know be patient right. :oops:
 
Updated RT-AC66U B1 main router with two USB attached drives (dirty flash with drives mounted), and two Nodes... no issues... GUI seems a bit more snappy.
 
Updated RT-AC66U B1 main router with two USB attached drives (dirty flash with drives mounted), and two Nodes... no issues... GUI seems a bit more snappy.
The "snappy GUI" is a well observed placebo effect from a fresh reboot, many users report it after each new release.
 
There are many placebo effects when updating code. Its not a bad thing.
Agreed, just wanted to point it out.

I'm sure most of us here feel that installing the latest point release will result in some sort of improvement, even if that improvement is sometimes hard to quantify. Warm fuzzy feeling aside...

Edit: I do acknowledge and recognize the importance of the security updates rolled into each new release, and do personally install every new version. I'm just pointing a little fun at the sometimes perceived "performance" benefits of EVERY new release.
 
Last edited:
Perceived or not node wireless seems stable but only run for 2d 2h.
 
Some models aren't ready yet for a GPL release, so I asked them to at least provide me for now for the RT-AC68U GPL so I could begin work on merging the open-sourced parts while they work on issues affecting some of the other models.

This is why I don't support 40 different models. The more models I support, the harder it is to get them all aligned. So I limit support to a few select models of my choice.

No, I have no ETA as to when they will have debugged the affected models.
That is to be expected. I think you are lucky just to be able support the models you are able to. With that same note, you are lucky just to have access to gpls early when you do.
I already readded it when I merged the GPL (and I also skipped all the others "security hardening changes" that I felt made no sense for this project), however there was a typo in the install recipe that prevented the applet from being symlinked. Already fixed locally, but I haven't tested the fix yet so it's not on Github yet.
So it sounds like they are battening down the ladies room again?

I imagine when waiting on gpls it just takes patience. @RMerlin
Thank you
For everything!
 
@RMerlin posted an alpha1 image for the XT12 a couple of hours ago (as indicated in edit to first post of this thread by OP). Changelog updated to include:

"- UPDATED: Merged with 386_48966 GPL."​
 
Last edited:
Well my 68 node wireless managed to stay up for 6d before curiously disconnecting. Usually it is the Binding Update in the log that does it but that seems fixed now but nothing in the log around the disconnect (5ghz) time other than a deauth due to station leaving. :|
 
@RMerlin Could you take a look at this long standing bug that's been reported here and here.

The issue is specifically with NAT lookback for UDP when CTF is enabled. CTF doesn't work with UDP so there's an iptables rule that's meant to disable CTF for UDP traffic. Unfortunately the rule is placed too late in the flow (mangle/FORWARD) so never gets executed. John fixed it in his firmware by moving the rule to mangle/PREROUTING.

 
I had compiled my own 386.6 for my RT-AX56U several months back and did a dirty upgrade to the new 386.7 alpha. So far so good. Will post if I encounter any issues.
 
Dirty upgrade from 386.5_2, no errors in the syslog, all devices reconnected and work as intended. Thanks @RMerlin!
 
Just flashed 386.7_A1 Working excellent !! Thanks Merlin.
 
Status
Not open for further replies.

Latest threads

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