[Beta] Asuswrt-Merlin 384.12 Beta is now available

[jerry6]

I have back ups. I just have people I cannot afford downtime atm anything that saves me time is worth the time imo.

my 5300 shows the same as yours for network tools , I did a factory reset before loading 384-12 beta. went back to 384 11 release get the same as 12 beta 1 on network tools thoght goimng back wold fix it , but nothing changede

 

[Swistheater]

my 5300 shows the same as yours for network tools , I did a factory reset before loading 384-12 beta2

You mean beta 1 ?

 

[Vexira]

You mean beta 1 ?

he could have compiled beta 2, some people do compile updates to test things early.

 

[Swistheater]

I know this vexira, but he would have had to compile only the master unless he merged it with the mainline and resolved the merge complaints.

 

[skeal]

@skeal, are you still able to reproduce your original issue? If so, could you try with this wanup2 test build in the Test Builds folder? Send me the resulting syslog generated during boot, so I can review the wan_up() calls and their timing relative to ntpd and OpenVPN starting. Initial results with another tester looked good, tho the wanup2 build contains one additional fix that hasn't been tested yet.

Sorry, I dumped my static IP and went with a dynamic IP, and a switch instead of a modem in front of my router. I no longer have that issue, nor know of a way to recreate the same result.

 

[Vexira]

I know this vexira, but he would have had to compile only the master unless he merged it with the mainline and resolved the merge complaints.

either that or its a typo, like you first pointed out, from what I can see beta two looks good, and I hope asus will soon drop that qos fix merlin mentioned and it makes it to alpha 2 or 3 even.
but then again merlin did mention something about some special tester and a specific issue

 

[Swistheater]

either that or its a typo, like you first pointed out, from what I can see beta two looks good, and I hope asus will soon drop that qos fix merlin mentioned and it makes it to alpha 2 or 3 even.
but then again merlin did mention something about some special tester and a specific issue

Yea I forked it and fixed the merge complaints myself and can confirm the beta 2 version fixes the issue with netools.

 

[scjr]

Nearly 6 days uptime on beta 1 and rock solid performance. DoT, DNSSEC using Cloudflare working perfectly. Another fine release by RMerlin. Thank you.

 

[RMerlin]

I upgraded to the AX88U about two months back because I got a good deal at a computer shop on one, my old 88u with my family now.
The 192.168.50.1 tripped me out the first time I tried to login to it.

lol I forgot to update my signature.

The issue seems to mostly happen on firmware upgrades, tho it can also be triggered by a reboot.

 

[RMerlin]

Sorry, I dumped my static IP and went with a dynamic IP, and a switch instead of a modem in front of my router. I no longer have that issue, nor know of a way to recreate the same result.

No problem. At least I was able to resolve most of the issues with the other user. Still a few more service restarts than I would have liked, but considering the event model used by Asuswrt, I'll have to consider it "good enough" with the latest changes.

 

[jerry6]

You mean beta 1 ?

yes sorry about that , edited post , get the same with 384.11 release no change in nettools gui shows as yours does on 38412.beta1

 

[L&LD]

my 5300 shows the same as yours for network tools , I did a factory reset before loading 384-12 beta. went back to 384 11 release get the same as 12 beta 1 on network tools thoght goimng back wold fix it , but nothing changede

You need to do the reset to factory defaults followed by a minimal and manual configuration (do not use a backup config file to restore from) AFTER flashing the firmware you want to use.

 

[Swistheater]

You need to do the reset to factory defaults followed by a minimal and manual configuration (do not use a backup config file to restore from) AFTER flashing the firmware you want to use.

no it is a bug in his version of firmware merlin fixed it for new batch that isn't out yet, a factory reset wont fix his issue, but you are correct, it is important to reset "AFTER" you update.

Note: some people do one before and after, but this seems like to much wear on the flash for me, after-all you are beta testing and flash aloootttt

 

[cmkelley]

no it is a bug in his version of firmware merlin fixed it for new batch that isn't out yet, a factory reset wont fix his issue, but you are correct, it is important to reset "AFTER" you update.

Note: some people do one before and after, but this seems like to much wear on the flash for me, after-all you are beta testing and flash aloootttt

As an aside, Merlin has noted that the flash in the routers is rated for some ungodly number of read/write cycles for just that reason. It is not the cheap flash found in many flash drives.

 

[jerry6]

You need to do the reset to factory defaults followed by a minimal and manual configuration (do not use a backup config file to restore from) AFTER flashing the firmware you want to use.

I LOSDED 384.12 beta on a router that was reset to factory defaultds before loading 384-12beta1 , did not use a bacup cofig set everything manualy

 

[L&LD]

I LOSDED 384.12 beta on a router that was reset to factory defaultds before loading 384-12beta1 , did not use a bacup cofig set everything manualy

Yes, the order you're doing it is wrong, if I'm understanding your post correctly.

 

[Delusion]

Just compiled Beta 2 . Works great. However , after the the update I had to remove my DNS settings ( I use 'secure dns' with dot and DNSSEC , much faster resolving than cloudflare ,at least for me) because WAN didn't connect, usb showed unmounted and the clock was not set . I re-applied DNS settings after the connection was established. I guess this happened because DNS cache was set to YES on tools page?

 

[skeal]

I guess this happened because DNS cache was set to YES on tools page?

Yep!

 

[Delusion]

Yep!

I asked because I don't remember I had this issue when I used Cloudflare servers for DoT . I noticed also that it takes about 30 seconds for SecureDNS server to connect (not firmware\Merlin related ) so I thought this delay might have caused no connection after flashing... I guess I will turn off DNS cache

 

[Swistheater]

Just compiled Beta 2 . Works great. However , after the the update I had to remove my DNS settings ( I use 'secure dns' with dot and DNSSEC , much faster resolving than cloudflare ,at least for me) because WAN didn't connect, usb showed unmounted and the clock was not set . I re-applied DNS settings after the connection was established. I guess this happened because DNS cache was set to YES on tools page?

how did you compile beta 2 did you fix any complaints when merging master and mainline?

EDIT:: NVM i see merlin has been busy again... can't keep a good dev down.