Release Asuswrt-Merlin 386.7 is now available for all models

[lepa71]

If you are asking what changes or updates were made in the 386.7_1 test builds I think RMerlin explained it in the following post earlier in the thread:

Release - Asuswrt-Merlin 386.7 is now available for all models

Are the changes significant enough to either stay on the original or the test version for IPV6 purposes? Up to you. This also contains fixes for DNSFilter in IPv6 mode, and the dropbear PATH not being properly set by some SSH clients. merlin@ubuntu-dev:~/amng$ git log --oneline 386.7..HEAD...

www.snbforums.com

I can't find that post.

 

[Jeffrey Young]

I can't find that post.

You don't have to find it, just click on the link @bennor provided you. It will take you right there.

 

[lepa71]

You're welcome.

Some recent FF feedback:

Release - Asuswrt-Merlin 386.7 is now available for all models

The answer to this question is perhaps firmware specific. I would use Notice/Info in 386.7 firmware. I would actually prefer a log server and filter whatever I need in the mess generated. Sorry, I'm done testing 386.7 on my AX86U router since better and more stable firmware exists for this...

www.snbforums.com

New MS Edge has been fine and Google-free for me.

OE

MS Edge is based on chromium. So it is kind of Google Chrome

 

[lepa71]

You don't have to find it, just click on the link @bennor provided you. It will take you right there.

It takes me here

 

[OzarkEdge]

MS Edge is based on chromium. So it is kind of Google Chrome

Yes, Chromium is open source. The point was 'it's not Google'.

OE

 

[Clark Griswald]

@lepa71
That is the correct post.
RMerlin states "this also contains fixes for..."

 

[lepa71]

Yes, Chromium is open source. The point was 'it's not Google'.

OE

So is a FF.
for Edge, it is just MS is watching you instead of Google. LOL

 

[OzarkEdge]

So is a FF.
for Edge, it is just MS is watching you instead of Google. LOL

FF is the problem in this thread.

Yes, that was the point, not Google.

What's so funny?

OE

 

[lepa71]

@lepa71
That is the correct post.
RMerlin states "this also contains fixes for..."

Then I'm confused. I expected to see the text about AC68U but it talks about IPv6 and DNSFilter

 

[Jeffrey Young]

Then I'm confused. I expected to see the text about AC68U but it talks about IPv6 and DNSFilter
View attachment 42651

If there is a 7_1 build for the AC68U, then the the fixes described includes that model. If no build - no fix.

 

[lepa71]

If there is a 7_1 build for the AC68U, then the the fixes described includes that model. If no build - no fix.

There is a build for ac68u but based on that post it does not fix the client's speed when ac68u is in bridge mode.

 

[ColinTaylor]

Then I'm confused. I expected to see the text about AC68U but it talks about IPv6 and DNSFilter
View attachment 42651

Ignore the quoted text in posts that link to other posts. Click on the link to go to the actual post. The quoted text is from the top of the web page that is being linked to. It is not from the linked post (unless that coincidentally happens to be at the top of the page).

 

[Clark Griswald]

@ColinTaylor is correct for what is stated in post #877, BUT the initial inquiry by @lepa71 was where to find the post regarding the changes to the 7.1 test build (Post 864).
Current RMerlin fw working well in my environment!
Have A Great Day Everyone!

 

[JohnSmith]

Does anybody see this when looking for logs?
View attachment 42639

Yes, I cleared my logs a couple of days ago, came back and looked in the logs and saw this. ASUS RT-AX88U with FW V386.7, uptime 4days 21 hours 38 minutes

 

[N/A]

2. [Asus router as client] If the OpenVPN profile enables IPv6, Asus router enables IPv6, and OpenVPN client on Asus router sets DNS to exclusive, the expected behavior should be that all DNS queries will go through the VPN. However, currently DNS will go through both the VPN's IPv4 DNS and client router's IPv6 DNS. Usually client router's IPv6 DNS responds faster and the response is used causing DNS leak. I suspect that the DNS redirection for VPN is only set on IPv4. My temporary solution is setting client router's IPv6 DNS to client router's IPv4 DNS encoded in IPv6 format.

After further testing, "setting client router's IPv6 DNS to client router's IPv4 DNS encoded in IPv6 format" somehow still leaks. I'll try 386.7_1 later.

 

[Morpheus2020]

In 386.7 or 386.49447 of AX86U, "160MHz+ch36" will make your router lose 160MHz when an 80MHz device is pluged in.
"20/40/80/160MHz + Enable 160MHz + ch auto + DFS” will make your router boost to 160MHz automatically when a 160MHz device is pluged in. When your last 160MHz device disconnects, your router will drop to 80MHz. And a 160MHz device is pluged in, your router boost to 160MHz automatically again.

Although both versions of the firmware can achieve 160MHz 5G WiFi, the following two things make me irritable:
1. 5G bandwidth of the AiMesh node is always the same as the AiMesh router. This means your AiMesh node is always at 80MHz if your AiMesh router drop to 80MHz.
2. A 160mhz device connects to the AiMesh router when the the AiMesh router is at 80MHz. Then the AiMesh router boost to 160MHz after 1-2 min. But the 5G WiFi disconnects for a split second so that this 160MHz device is connected to the AiMesh node. AiMesh router that lose 160MHz devices drops to 80MHz. Then this 160MHz device connects back to the AiMesh router by AiMesh or 802.11K/V. And the AiMesh router boost to 160MHz after 1-2 min.....................This 160MHz device "jumps" between the AiMesh router and the AiMesh node. Sometimes, it ends up connecting to the AiMesh router with 160MHz. Sometimes, it ends up disconnecting.

I hope ASUS can provide a new Source Code soon to fix this 5G bandwidth issue.

 

[tyspeed42]

@RMerlin Is there any reason to go to 386.7 first, then update to the beta or is going to the beta directly 386.7_1 ok without having to reset on AX86U.

 

[RMerlin]

@RMerlin Is there any reason to go to 386.7 first, then update to the beta or is going to the beta directly 386.7_1 ok without having to reset on AX86U.

No reason to, you can go directly to 386.7_1 (or 386.7_2 once that's released).

 

[jerry6]

working well on my rt5300 thanks aain

 

[busch09]

I have 2 rt-ax88 and a rt-ax58. When I flash & mesh 386.7_1 Ethernet Backhaul does not work. Routers stay on Wi-Fi backhaul.