Release Asuswrt-Merlin 3006.102.5 is now available

[YumeHatsuyuki]

Yes, I have already undergone a hard reset, and what I see now is the result after the new configuration. Or should I do it again?

Tried same Advice as above in post #23?

 

[MDM]

Yes, I have already undergone a hard reset, and what I see now is the result after the new configuration. Or should I do it again?

Read the post 23, not the Router, but the Modem (ONT)!

P.S.
If not, try the hard reset Again (but maybe the WPS method this time?)...

 

[Clark Griswald]

Dirty upgrades through betas to final with zero issues regarding ipv6, DDNS, GNP IoT, WG server, zero network issues with latest RMerlin on our GT-AX6000.
Thank You RMerlin!

 

[YumeHatsuyuki]

Read the post 23, not the Router, but the Modem (ONT)!

P.S.
If not, try the hard reset Again (but maybe the WPS method this time?)...

Oh my god, you're right, I've been ignoring my mediator! My IPv6 has been 'disappeared' by the ISP. Sorry to disturb everyone.

 

[YumeHatsuyuki]

Wait, it doesn't seem to be entirely true, but my router still obtained a valid IPv6? It's really strange, I can test a valid IPv6 address in the router SSH.

Read the post 23, not the Router, but the Modem (ONT)!

P.S.
If not, try the hard reset Again (but maybe the WPS method this time?)...

 

[YumeHatsuyuki]

Read the post 23, not the Router, but the Modem (ONT)!

P.S.
If not, try the hard reset Again (but maybe the WPS method this time?)...

I have decided to reset the router and mediator separately again to see if this issue can be resolved.

 

[Rik Stigter]

Dirty upgrade on RT-BE88U. No issues so far. I like the new connections page a lot!

 

[shabbs]

Let's GO!

EDIT: Filthy upgrade from Beta 3. So far, so good. No issues off the hop. DDNS good, DNS Director good, VPN Director good. IPTV/IOT/Nest/Google/TP-Link devices all good.

Internet speed as expected...

Will give the system a final restart across the gear and let it settle.

As always thank you to @RMerlin and team!

 

[Traveler2100]

After upgrade some ip addresses not available to a NAS on the 2.5G port LAN 3 on GT-BE98 Pro. IT is not something I have seen before. Moved NAS to a switch connected to 10G port on the router and all ip's available. I could not find anything in the logs so I went back to 3006.102.4 and everything is available on LAN 3 again. I am going to stay on 102.4 for now until I can have a better understanding of the issue. The ip addresses in question were all on two POE switches connected to a 2.5 switch connected 10G to a 10G port on the router. I did not do an exhaustive test, but it seemed I could ping the addresses from the other machines on the router connected directly to the router through 10G ports. In other words, this is the only port that seemed to have an issue. I restarted everything, switches, router and NAS and the issue persisted until I went back to 102.4.

 

[YumeHatsuyuki]

I upgraded from 3006.102.4 to 3006.102.5 and performed a hard reset, but I've encountered an issue. Neither my primary network nor my custom network (with IPv6 enabled) is successfully assigning publicly routable IPv6 addresses to any wireless devices. This problem wasn't present in version 3006.102.4
View attachment 67145
View attachment 67146

I performed a hard reset again. This time, effective global IPv6 was successfully assigned to subordinate devices.
Unlike the last time, I turned off the IPv6 option in the network allocation in Network>GUEST NETWORK PRO>Advanced Settings.

 

[teo1966]

Hello.
I have an RT-AX88U_Pro router and two RT-AX88U_Pro mesh routers.
What's the best update sequence? Currently, 3004.388.8 is running, first to 3006_102.4, and then to 3006_102.5 with a Dirty flash or a Clean install and a hard reset
or straight to 3006_102.5 Dirty flash or a Clean install and a hard reset
If I read the readme it is best to update in 2 steps. Does anyone have experience with this?

this is in the README

NOTE: resetting to factory default after flashing is
strongly recommended for the following cases:

- Updating from a firmware version that is more than a few releases older
- Switching from another third party firmware
- Switching from Asus' original firmware, and you were using VPN features

If you run into any issue after an upgrade and you haven't done so,
try doing a factory default reset as well.

Always read the changelog, as mandatory resets will be mentionned
there when they are necessary.

In all of these cases, do NOT load a saved copy of your settings!
This would be the same thing as NOT resetting at all, as you will
simply re-enter any invalid setting you wanted to get rid of. Make
sure to create a new backup of your settings after reconfiguring.

I did this:

3004.388.8 is running, first two mesh RT-AX88U_Pros to 3006_102.4, then the mesh master to 3006_102.4, then two mesh RT-AX88U_Pros to 3006_102.5, then the RT-AX88U_Pro to 3006_102.5, and everything with a dirty flash.
No problems encountered yet.
Thanks, RMerlin, for the good work.

This is definitely worth a donation for all the time and work.
The donation is on its way.

 

[emwgee]

Updated to Asuswrt-Merlin 3006.102.5 from 3006.102.4. Hard reset and re-configured from scratch.


I have noticed that setting AP isolation in any Guest Network (different subnet address) seems to have triggered AP isolation in the main network also, I have my desktop and Raspberry Pi connected directly to LAN ports of the router. As long as AP isolation is set on with any one of the guest networks, I can no longer access the Raspberry Pi from my desktop, either via browser or SSH; pinging is also lost on both ends.

 

[Dedel66]

Updated to Asuswrt-Merlin 3006.102.5 from 3006.102.4. Hard reset and re-configured from scratch.


I have noticed that setting AP isolation in any Guest Network (different subnet address) seems to have triggered AP isolation in the main network also, I have my desktop and Raspberry Pi connected directly to LAN ports of the router. As long as AP isolation is set on with any one of the guest networks, I can no longer access the Raspberry Pi from my desktop, either via browser or SSH; pinging is also lost on both ends.

I can't confirm that. Both the guest network and the IoT network are isolated, and I can access and ping everything in lan from the main network from all nodes.

 

[NiklasO]

"Good" to see more people reporting the client # problem. Good in the sense its probably nothing wrong in my network.
The fw has been very stable on the latest betas, just that you can't trust the connected client count. But it will run fine even if it tells you that you have 230-250+ connected clients.