Release Asuswrt-Merlin 386.7 is now available for all models

[Deleted member 22229]

Flashed 386.7_1 as always working good on AX58U. IPv6 worked good for me on both builds comcast native.

 

[Damit1]

Prefix should be left empty unless your ISP requires you to specify the prefix rather than let them automatically decide it for you.

This setting is only for special cases.

We are both (me and him) on the same ISP. Should just leave it blank and let it obtain.

In the new 386 7 FW it takes longer than 386 5 2 (there it takes not longer than 30 sec since boot time) but once it does, it seems to be stable for now.
In 386 7 whole the network crashed after about 30m- 1h. so far it works as should.

If you have any control over the time it takes to obtain the address to make it faster like in 386 5 2, that would be fantastic.
If not, will stick to it (it just takes about 2-5 mins to obtain the address, anyway that how fast it obtain for me).

 

[Deleted member 22229]

If you have any control over the time it takes to obtain the address to make it faster like in 386 5 2

Comcast Native V6 here and the router obtains a IPv6 address the second its booted no wait time.

 

[Damit1]

Comcast Native V6 here and the router obtains a IPv6 address the second its booted no wait time.

I appreciate the comment..
Maybe it is ISP related, but in the last stable-stable release it just obtained faster.
Because it takes more time to obtain, certain devices boot up obtain IPv4 only because the IPv6 is not obtained yet (like my VOIP adapter).
That is something that should be mentioned.

Anyway it works, for starters, it is fine.

 

[BlackIce]

Merlin,

I noticed when saving SETTINGS with 386.7_1 that it saved the settings file as Settings_RT-AC86U without the extension .CFG
Added the extension and tested the file and it was good once the .CFG was added. Just letting you know.

 

[Damit1]

Well
Last reboot for tonight, IPv6 is obtained in 1.5m like on 386 5 2, I can sleep tightly tonight
Now only stability I have to check for long run.

Thank you @RMerlin

Tested on AX88U.

 

[FLA_NL]

No I don't either, but it is bugging me what it means.

Anyone know?

Jun 25 09:21:55 kernel: ^[[0;33;41mFCACHEfc_vblog_list_add ERROR: Duplicate blog: list blog<0xffffffc02f840e40> JOIN blog<0xffffffc02f82e000>^[[0m

If I turn on "Hide DHCP/RA queries" under DHCP settings those errors seem to disappear too.

 

[Howard_inGA]

That makes absolutely no sense, because nothing was changed regarding DNS handling. Just the size of the requested prefix.

Are you using DNSFilter?

I know, Eric! The only thing that changed was the install of the test build. When I went back to the stable build, all cleared up???
I don't have, nor did I add a DNSFilter? There was absolutely no change in configuration when the weirdness started, other than IPv6 on/off and VPN on/off; all of which was tried after the initial install tests. It all caught me by total surprise...

 

[Wade Coxon]

The 386.7_1 test build now lets the ISP decide on the prefix length (by requesting a length of 0) rather than enforcing a prefix of 64. This reverts to the previous behaviour, and is also what stock firmware currently does.

Ahh thanks for that, that's good info!

I have been diving into my ISP's forums, and it looks like whatever the problem is that I am seeing (No IPv6 after reboot), other ISP clients are seeing it on different hardware too. Whatever my problem is, doesn't appear to be related to the router firmware.

 

[Skywise]

Anyone having issue with NTP sync after connecting to 386.7?

I did a dirty upgrade to 386.7 and none of ntpmerlin, connmon or skynet is working because NTP can't sync. I have been doing dirty upgrade for a while and this is the first time I am seeing this.

No - but in my case I was running unbound along with ntpmerlin and found that I had to unblock the ntp servers in the unbound config or I would randomly NOT get NTP syncs and the router wouldn't let me out to the internet.
EG:
domain-insecure: "pool.ntp.org"
domain-insecure: "time.hist.gov"

 

[scaramonga]

View attachment 42596


GT-AX11000 nothing important. Cosmetic error, but it would definitely be easier to run the speed test if the display area is larger.

Speed test all OK here with space

 

[Damit1]

Well
Last reboot for tonight, IPv6 is obtained in 1.5m like on 386 5 2, I can sleep tightly tonight
Now only stability I have to check for long run.

Thank you @RMerlin

Tested on AX88U.

8 hours later. Everything works as should.
Ring is working as expected.

VPN connection is working solid for 2h, just like before.

Seems like we are good to go for stable with this one.

 

[Ubimo]

Some people here are talking about version 386.7_1.
I guess this version only includes fixes for IPv6 related problems? Or does this version also include other features/bugfixes?

 

[iJorgen]

Some people here are talking about version 386.7_1.
I guess this version only includes fixes for IPv6 related problems? Or does this version also include other features/bugfixes?

Check here: https://www.snbforums.com/threads/a...ow-available-for-all-models.79450/post-774563

 

[L&LD]

Almost always, other fixes are included. Not everything is documented. And most times, at all.

 

[Tech9]

I have noticed IPv6 is still not working on Rogers network in Canada, at least last night around Toronto area. The router gets an IPv6 address, but no IPv6 traffic. If someone here is testing IPv6 in Canada and getting nowhere, it may be your ISP related issue. Rogers network is still not fully restored.

 

[Damit1]

Jul 10 15:02:49 kernel: CONSOLE: 085161.127 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1
Jul 10 15:02:51 kernel: CONSOLE: 085163.117 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1
Jul 10 15:02:53 kernel: CONSOLE: 085165.108 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1
Jul 10 15:02:53 kernel: CONSOLE: 085165.197 wl0: wlc_ampdu_recv_addba_resp: a8:40:7d:87:f8:68: Failed. status 37 wsize 16 policy 1
Jul 10 15:02:53 kernel: CONSOLE: 085165.198 wl0: wlc_ampdu_recv_addba_resp: a8:40:7d:87:f8:68: Failed. status 37 wsize 16 policy 1
Jul 10 15:02:54 kernel: CONSOLE: 085166.207 wl0: wlc_ampdu_recv_addba_resp: a8:40:7d:87:f8:68: Failed. status 37 wsize 16 policy 1
Jul 10 15:03:41 kernel: CONSOLE: 085212.881 wl0: wlc_ampdu_recv_addba_resp: 70:03:9f:7d:fb:7b: Failed. status 1 wsize 64 policy 1
Jul 10 15:03:42 kernel: CONSOLE: 085213.876 wl0: wlc_ampdu_recv_addba_resp: 70:03:9f:7d:fb:7b: Failed. status 1 wsize 64 policy 1
Jul 10 15:03:42 kernel: CONSOLE: 085213.973 wl0: wlc_ampdu_recv_addba_resp: 98:cd:ac:af:38:c0: Failed. status 1 wsize 0 policy 1
Jul 10 15:03:42 kernel: CONSOLE: 085213.973 wl0: wlc_ampdu_recv_addba_resp: 98:cd:ac:af:38:c0: Failed. status 1 wsize 0 policy 1
Jul 10 15:03:43 kernel: CONSOLE: 085214.889 wl0: wlc_ampdu_recv_addba_resp: 98:cd:ac:af:38:c0: Failed. status 1 wsize 0 policy 1
Jul 10 15:03:43 kernel: CONSOLE: 085214.889 wl0: wlc_ampdu_recv_addba_resp: 34:ab:95:91:d6:2c: Failed. status 1 wsize 0 policy 1
Jul 10 15:03:43 kernel: CONSOLE: 085214.890 wl0: wlc_ampdu_recv_addba_resp: 34:ab:95:91:d6:2c: Failed. status 1 wsize 0 policy 1
Jul 10 15:03:43 kernel: CONSOLE: 085214.890 wl0: wlc_ampdu_recv_addba_resp: 34:ab:95:91:d6:2c: Failed. status 1 wsize 0 policy 1
Jul 10 15:03:45 kernel: CONSOLE: 085216.866 wl0: wlc_ampdu_recv_addba_resp: 70:03:9f:7d:fb:7b: Failed. status 1 wsize 64 policy 1
Jul 10 15:03:49 kernel: CONSOLE: 085220.845 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1
Jul 10 15:03:51 kernel: CONSOLE: 085222.834 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1
Jul 10 15:03:53 kernel: CONSOLE: 085224.825 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d

Help!
The log is flooded with Failed statuses like the ones I attached.
Was not in 386 5 2.
Anyone knows if is resolvable?
It was in 386 7 beta and I think was not in Release stable.

 

[Tech9]

Help!

Do you have any connectivity issues? If not, just don't look at the logs. Diagnostic is enabled. Stock Asuswrt is the same.

 

[jb68]

Having Wi-Fi issues. Keep disconnecting and knocking every Wi-Fi Device on the AX88u. I have tried fresh install too and 30 mins later same issue. Flashed the previous firmware and having no issues with disconnections. No idea what’s happening.

 

[Damit1]

Do you have any connectivity issues? If not, just don't look at the logs. Diagnostic is enabled. Stock Asuswrt is the same.

Essentially nothing.
Hopefully diagnostic will be disabled for next round