Release Asuswrt-Merlin 386.7 is now available for all models

[RMerlin]

I already heard back from Mozilla/Bugzilla...this bug was known and is already fixed. Should be out in the next version I believe...103

Can you link the Bugzilla ID please? That way we can refer users to it when asked about the issue.

 

[paul0363]

Can you link the Bugzilla ID please? That way we can refer users to it when asked about the issue.

https://bugzilla.mozilla.org/show_bug.cgi?id=1778620

 

[John Fitzgerald]

Can you link the Bugzilla ID please? That way we can refer users to it when asked about the issue.

Firefox v103.0 is out now, just upgraded. It's still saving as .txt

NOT FIXED!!!

 

[clweb]

Tested with Firefox 103 and Ubuntu 22.04. I have still 386.7 and the config was saved with a .txt extension.
I'll try again with 386.7_2, but I think it is a Firefox problem.

 

[paul0363]

Tested with Firefox 103 and Ubuntu 22.04. I have still 386.7 and the config was saved with a .txt extension.
I'll try again with 386.7_2, but I think it is a Firefox problem.

From the linked Bugzilla report above (post #1814)
"Good news is that it works well on Nightly 104.0a1, but issue is still there on latest Beta 103.0b8."

So looks like a Firefox issue that *may* be fixed in 104

 

[ColDen]

Performed a dirty upgrade from 386.7 50 minutes ago on my RT-AC86U:

View attachment 43109

I did not observed any issues so far.

Thanks Éric!

As a side note, not related to this upgrade, my router was crashing about every 25 days when I had my USB WD My Book 4 TB connected to the 3.0 USB port. 60 days ago it became MIA (without any prior indication nor warning) and replaced it with a Synology DS220+ NAS (with 2 WD Red Plus 6 TB) 40 days ago. Since then my router did not had a sigle "hickup".

 

[AntonK]

Totally smooth update, and rock solid reliability for days now.

But as you can see, my AX86U is set to AP behind a firewall-router, so I'm not sure what all this means... but there we are.

 

[jeff3820]

I already heard back from Mozilla/Bugzilla...this bug was known and is already fixed. Should be out in the next version I believe...103

Update: Just got Firefox 103...this bug is fixed!!

 

[kakaiba]

AC86U from 386.5_2 to 386.7_2. I didn't unplug the flash drive that is connected to the USB port.

Running for more than 24 hours now. No issues whatsoever.

 

[RMerlin]

https://bugzilla.mozilla.org/show_bug.cgi?id=1778620

Thanks.

While randomly renaming files is still a bug on Firefox's end, one person in that thread had a valid point that Asuswrt tries to use an invalid mimetype for some of its file, and this should probably be addressed, to prevent future issues. I'll discuss it with upstream.

 

[Ubimo]

AC86U, I've just flashed beta 2, but the yellow exclamation mark is still blinking. Why?

Edit: Silly me, there is a new release, not beta.

 

[RMerlin]

AC86U, I've just flashed beta 2, but the yellow exclamation mark is still blinking. Why?

Because 386.7_2 is a final release, while 386.7 beta 2 is actually 386.7_0 beta 2, and therefore quite older.

 

[jata]

I noticed one strange thing. My channel for 5ghz changed from 36 (fixed) to automatically with the update. Anyone else had the same? Could it be possible also other settings got changed?

Thanks.

I have seen this too (5Ghz changed to auto from fixed) when updating between 386.5 to 386.7 on my AX86S. No other settings have been impacted.

 

[John Fitzgerald]

I have seen this too (5Ghz changed to auto from fixed) when updating between 386.5 to 386.7 on my AX86S. No other settings have been impacted.

I had this issue during the Alpha or Beta phase, can't remember. Went back to 386.5_2 then 386.7_2 and it didn't happen again. I also tried 386.7 and did a factory reset and rolled back to 386.5_2.

Hard to remember where it first happened but I think it was during the Alpha stage.

It has not happened since. I was surprised when I discovered it by accident.
I also changed from 80MHz fixed to 20/40/80 and saw a good bump in ROKU speed.
I kept some of the defaults instead of changing them when I did the factory rest.

 

[livefeed]

RT-AX92U is not supported correct?
I have a few 92’s nodes meshed of a GT-AX11000 and want to make sure.

 

[icanfly]

I'm already on 386.7 and will look to upgrade to 7_2 but just wondering about this change:

RT-AX88U and GT-AX11000 radio firmware downgraded to the previous version.

were there issues with the radio firmware in 386.7? I did notice sometimes wifi clients would have no internet until reboot the router does this fix that?

Saw a lot of comments about unplugging the usb before upgrading. I have a USB 4g modem in one and a USB disk in the other but I never removed them before when I upgraded. Should I be?

thanks

 

[Morpheus2020]

AX86U upgraded from 386.5.2 to 386.7.2.
1. WiFi is stable. I don't see any WiFi disconnects.
2. 160MHz will drop to 80MHz when the router has no 160MHz device connected and there is an 80MHz device connected. When a 160MHz device is connected, the router will automatically return to 160MHz after about 2 minutes. This requires you to set the channel to Auto+DFS. Same as 386.7 , 386.49447 and 386.49599.
3. If I keep a 160MHz device connected, the router's 160MHz is stable.

Thanks for your work.

The duration of my previous test was too short. There are new reports now.
If I keep the router at 80MHz for a long time, the router may switch to channel 149 which does not support 160MHz. Connecting a 160MHz device at this time cannot make the router go back to 160MHz.
So I'm back to 386.5.2 which can stay at 160MHz for a long time.

 

[Dedel66]

Maybe I found another issue:
If I turn Networkmonitoring off my connection is stable shown as "connected" at Network Map Overview.

If I turn monitoring on either "DNS Query" or "Ping" or both, the Internetstatus at Network Map Overview toggles sometimes from "connected" to "disconnected" and back, though it is stable all time.

Somebodyelse realized this behavior?

 

[TheLegendary87]

Upgraded to 386.7_2 from 386.7 on AX88U and now I'm receiving the "Setup Wizard" on every reboot since. First time ever experiencing this after an upgrade.

 

[juiceof2limes]

Anyone seen odd behaviour with DDNS ignoring values for checking if change of WAN IP?
It should do a forced update every 10 days and a check every 2 hours. But as can be seen from log, its checking very frequently and my IP is not changing yet it forces an update.

Currently running latest FW 386.7_2 on AX86U but this has been happening on previous F/W.

Jul 27 09:52:35 inadyn[17929]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 09:52:35 inadyn[17929]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 09:52:36 inadyn[17929]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 10:30:20 inadyn[22366]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 10:30:21 inadyn[22366]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 10:30:21 inadyn[22366]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 11:30:21 inadyn[29346]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 11:30:21 inadyn[29346]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 11:30:22 inadyn[29346]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 11:53:05 inadyn[32002]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 11:53:05 inadyn[32002]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 11:53:06 inadyn[32002]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 12:30:21 inadyn[3966]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 12:30:21 inadyn[3966]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 12:30:22 inadyn[3966]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 13:30:21 inadyn[10938]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 13:30:22 inadyn[10938]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 13:30:22 inadyn[10938]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 13:53:35 inadyn[13627]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 13:53:35 inadyn[13627]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 13:53:36 inadyn[13627]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 14:30:22 inadyn[17963]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 14:30:22 inadyn[17963]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 14:30:23 inadyn[17963]: Updating cache for xxxxxxxxxxxxxxxxx
Jul 27 15:30:22 inadyn[26233]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Jul 27 15:30:22 inadyn[26233]: Update forced for alias xxxxxxxxxxxxxxxxx, new IP# xx.xx.xx.102
Jul 27 15:30:23 inadyn[26233]: Updating cache for xxxxxxxxxxxxxxxxx