[Release] Asuswrt-Merlin 384.14 (and 384.13_2) are now available

[Makaveli]

updated my 86u and no issues thus far. is it advisable to use AiProtect on a merlin firmware?

You should experiment with AI protect on your side.

Some of us prefer to just use Skynet and keep it off due to it using alot of resources in the router.

But others have it running and have no issues so you will have to test with it on and off in your environment and see how it performs for you.

 

[PeterV]

Asuswrt-Merlin 384.14

• Updated components: dnsmasq 2.80-95-g1aef66b.

Excuse me for a long silence mode, had several issues not related to the router. Only toay have a chance to visit forum ...
It's look like everysthing is fixed. Thanks!

 

[SheikhSheikha]

@SheikhSheikha can you try slightly moving your router (up/down/left/right/spin) to give some coverage to those dead spots?

Thanks for thinking about a solution but both AC5300 routers are located on a proper central spot each covering a floor. (Spinning does not provide any improvement). The significant differences in signal strenght were measured with WiFi Explorer (MacOS) that I use for years with two AC5300's side-by-side (384.13 & 384.14), both 384.14 and 384.14 & 384.13).

 

[StefanoN]

Hi
I have an Asus rt-ac86u, after the upgrade from .13 to .14 in the system log I see continuous:
Dec 14 20:03:48 inadyn[1873]: Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com
Dec 14 20:04:14 kernel: pgd = ffffffc0144b6000
Dec 14 20:04:14 kernel: [00000000] *pgd=0000000015164003, *pud=0000000015164003, *pmd=00000000151c3003, *pte=0000000000000000
Dec 14 20:04:24 crond[1002]: time disparity of 847559 minutes detected
Dec 14 20:04:56 inadyn[13433]: Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com
Dec 14 20:05:02 kernel: pgd = ffffffc0120ce000
Dec 14 20:05:03 kernel: [00000000] *pgd=0000000014568003, *pud=0000000014568003, *pmd=0000000012149003, *pte=0000000000000000
Dec 14 20:05:31 inadyn[16033]: Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com
Dec 14 20:05:32 kernel: pgd = ffffffc0113db000
Dec 14 20:05:32 kernel: [00000000] *pgd=000000001218f003, *pud=000000001218f003, *pmd=00000000144d1003, *pte=0000000000000000
Dec 14 20:06:02 kernel: pgd = ffffffc01203b000
Dec 14 20:06:02 kernel: [00000000] *pgd=00000000122ce003, *pud=00000000122ce003, *pmd=00000000125e5003, *pte=0000000000000000
Dec 14 20:06:32 kernel: pgd = ffffffc012089000
Dec 14 20:06:32 kernel: [00000000] *pgd=0000000012147003, *pud=0000000012147003, *pmd=000000001200b003, *pte=0000000000000000
Dec 14 20:07:02 kernel: pgd = ffffffc0146a9000
Dec 14 20:07:02 kernel: [00000000] *pgd=000000001449d003, *pud=000000001449d003, *pmd=000000001443c003, *pte=0000000000000000
Dec 14 20:07:32 kernel: pgd = ffffffc011066000
Dec 14 20:07:32 kernel: [00000000] *pgd=0000000012186003, *pud=0000000012186003, *pmd=00000000111a1003, *pte=0000000000000000
Dec 14 20:08:02 kernel: pgd = ffffffc012214000
Dec 14 20:08:02 kernel: [00000000] *pgd=0000000014555003, *pud=0000000014555003, *pmd=000000001214e003, *pte=0000000000000000
Dec 14 20:08:34 kernel: pgd = ffffffc014694000
Dec 14 20:08:34 kernel: [00000000] *pgd=0000000011487003, *pud=0000000011487003, *pmd=0000000012214003, *pte=0000000000000000
Dec 14 20:09:04 kernel: pgd = ffffffc011349000
Dec 14 20:09:04 kernel: [00000000] *pgd=000000001233d003, *pud=000000001233d003, *pmd=00000000111a7003, *pte=0000000000000000
Dec 14 20:09:34 kernel: pgd = ffffffc0112e1000
Dec 14 20:09:34 kernel: [00000000] *pgd=000000001140e003, *pud=000000001140e003, *pmd=00000000111b3003, *pte=0000000000000000

What is this ?

Thanks

 

[eddiez]

Hi
I have an Asus rt-ac86u, after the upgrade from .13 to .14 in the system log I see continuous:
Dec 14 20:03:48 inadyn[1873]: Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com
Dec 14 20:04:14 kernel: pgd = ffffffc0144b6000
Dec 14 20:04:14 kernel: [00000000] *pgd=0000000015164003, *pud=0000000015164003, *pmd=00000000151c3003, *pte=0000000000000000
Dec 14 20:04:24 crond[1002]: time disparity of 847559 minutes detected
Dec 14 20:04:56 inadyn[13433]: Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com
Dec 14 20:05:02 kernel: pgd = ffffffc0120ce000
Dec 14 20:05:03 kernel: [00000000] *pgd=0000000014568003, *pud=0000000014568003, *pmd=0000000012149003, *pte=0000000000000000
Dec 14 20:05:31 inadyn[16033]: Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com
Dec 14 20:05:32 kernel: pgd = ffffffc0113db000
Dec 14 20:05:32 kernel: [00000000] *pgd=000000001218f003, *pud=000000001218f003, *pmd=00000000144d1003, *pte=0000000000000000
Dec 14 20:06:02 kernel: pgd = ffffffc01203b000
Dec 14 20:06:02 kernel: [00000000] *pgd=00000000122ce003, *pud=00000000122ce003, *pmd=00000000125e5003, *pte=0000000000000000
Dec 14 20:06:32 kernel: pgd = ffffffc012089000
Dec 14 20:06:32 kernel: [00000000] *pgd=0000000012147003, *pud=0000000012147003, *pmd=000000001200b003, *pte=0000000000000000
Dec 14 20:07:02 kernel: pgd = ffffffc0146a9000
Dec 14 20:07:02 kernel: [00000000] *pgd=000000001449d003, *pud=000000001449d003, *pmd=000000001443c003, *pte=0000000000000000
Dec 14 20:07:32 kernel: pgd = ffffffc011066000
Dec 14 20:07:32 kernel: [00000000] *pgd=0000000012186003, *pud=0000000012186003, *pmd=00000000111a1003, *pte=0000000000000000
Dec 14 20:08:02 kernel: pgd = ffffffc012214000
Dec 14 20:08:02 kernel: [00000000] *pgd=0000000014555003, *pud=0000000014555003, *pmd=000000001214e003, *pte=0000000000000000
Dec 14 20:08:34 kernel: pgd = ffffffc014694000
Dec 14 20:08:34 kernel: [00000000] *pgd=0000000011487003, *pud=0000000011487003, *pmd=0000000012214003, *pte=0000000000000000
Dec 14 20:09:04 kernel: pgd = ffffffc011349000
Dec 14 20:09:04 kernel: [00000000] *pgd=000000001233d003, *pud=000000001233d003, *pmd=00000000111a7003, *pte=0000000000000000
Dec 14 20:09:34 kernel: pgd = ffffffc0112e1000
Dec 14 20:09:34 kernel: [00000000] *pgd=000000001140e003, *pud=000000001140e003, *pmd=00000000111b3003, *pte=0000000000000000

What is this ?

Thanks

Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com

Try renewing your certificate

 

[StefanoN]

Certificate verification error:num=10:certificate has expired:depth=0:/CN=ns1.asuscomm.com

Try renewing your certificate

Thanks for your answer, but How I can renewing the certificate ?
And also .... the kernel error is for the problem of the certificate ?

Thanks

 

[dave14305]

Thanks for your answer, but How I can renewing the certificate ?
And also .... the kernel error is for the problem of the certificate ?

Thanks

It's an expired certificate on ASUS' server, you can't do anything about it. But Inadyn DDNS tool should be ignoring it based on Merlin's last workaround.

 

[XIII]

Do you see dropped packets in the system log?

No, so I guess it's me or Apple...

Still no clue how to debug/fix this then

 

[TheOldMan]

Dirty upgrade from 384.14_b3 to 384.14 went good. Like others said, the update went a wee faster. No significant complaints in the system log. Another great release, @RMerlin and team.

 

[Jasso]

Upgraded to 384.14, DNSSEC resolver test fails and IPv6 test fails. Reverted to Beta 3 for a while seems OK so far.

 

[skeal]

Thanks for your answer, but How I can renewing the certificate ?
And also .... the kernel error is for the problem of the certificate ?

Thanks

Enable access to webui from both http and https. So set it to both. Do not enable webui access from WAN. Oh and reboot.

 

[#TY]

Everything seems to be running perfectly at this end after updating to .14.

Thank you @RMerlin for all the awesome value you continue to provide.

 

[martinr]

RT-AC68U: dirty upgrade from .13 to .14. Upgrade itself went fine but am now hit with this:

Went to the Administration->System page, no Network Monitoring was enabled. Tried Ping, no luck. Tried DNS Query, no luck. It appears to be a visual problem only, access to the internet is working.

Not seeing that on my RT-AC68U, which I upgraded from 384.11_2 to 384.14. I’m seeing the usual Connected and then my IP address and DDNS address.

 

[martinr]

Just upgraded the RT-AX88U I am testing from the
RT-AX88U_384.14_beta3-new-g6ed03020e2_ubi firmware I was running before.

Even though that version is 85.5 MB and the final 384.14 is 79.8 MB, I did not see any appreciable decrease in the time needed to do the upgrade. What I did notice though is that the WiFi was available quicker than any other flash I have performed on this new v1.1 (China) RT-AX88U in the short time I've had it.

Before flashing from the previous firmware noted above, I rebooted the router and waited 10 minutes for it to settle down. The indicated connection varied between 150/160 to 300 Mbps on my 2.4GHz device (didn't bother to get a 5GHz enabled device to test with) and at almost the furthest possible distance (almost 60' and 4 or 5 walls, depending on how the signal bounces to get to the corner I am at) I can test from in my home.

Fast.com showed this for my 1Gbps up/down connection on this device:
59Mbps download
44Mbps upload
3ms unloaded and 212ms loaded

Even with the less than stellar numbers above, the internet feels very fast on this old device.

After flashing 384.14 'dirty' and waiting the same 10 minutes for the router to settle down, the connection fluctuates between 170/270 and 300 Mbps.

Fast.com showed this for my 1Gbps up/down connection on this device after the upgrade:
57Mbps download
55Mbps upload
2ms unloaded and 307ms loaded

The browsing speed on my old 2.4GHz device doesn't feel much different at all from before the flash, honestly, it even seems quicker.

With the most 'worst-case' scenario I can come up with before I have a coffee, I don't see any issues on this final release.

Thanks to RMerlin and all the other behind the scene contributors for another fine release.

I upgraded from 384.11_2 to 384.14 using your dirty guide


https://www.snbforums.com/threads/r...-384-11-is-available.56501/page-2#post-488583

Only suggestion is to point out that flashing should be done with ethernet connection and with wireless turned off on the connected device.

Always get a nice warm feeling working to one of your guides.

Many thanks

 

[Stevens243]

Dirty upgrade from 14B3. Node first, then the router (with the USB removed). Zero issues, clean log and all seems to be performing optimally.

Thanks!

 

[L&LD]

@martinr thank you too for that.

I have never had an issue with flashing an RMerlin supported router via WiFi; Asus does things properly here as the image is verified before it continues to flash.

 

[martinr]

@martinr thank you too for that.

I have never had an issue with flashing an RMerlin supported router via WiFi; Asus does things properly here as the image is verified before it continues to flash.

Excellent. I know what it was: I was getting mixed up with the warnings over risks of updating firmware remotely. I’ll now go back to updating wirelessly, confident it’s not slap-dash.

 

[StefanoN]

Enable access to webui from both http and https. So set it to both. Do not enable webui access from WAN. Oh and reboot.

Ok

Enable access to webui from both http and https. So set it to both. Do not enable webui access from WAN. Oh and reboot.

Ok, I applied your suggestions, and the result is:
1) in ddns -> server certificate the Status show always the word updating
2) in ddns -> server certificate the date of expires is 2028/5/5
3) sometimes in the system log appears this messages :
Dec 14 22:54:59 modprobe: module nf_conntrack_proto_gre not found in modules.dep
Dec 14 22:54:59 modprobe: module nf_nat_proto_gre not found in modules.dep
Dec 14 22:54:59 modprobe: module nf_conntrack_pptp not found in modules.dep
Dec 14 22:54:59 modprobe: module nf_nat_pptp not found in modules.dep
4) the kernel error in the log appears when I reboot the router with the ssd usb is connect. I try to format the ssd but the problem isn’t solved. If I detach the ssd, and reboot the router and when the router is up I attach the ssd ... the kernel log doesn’t appears.

 

[skeal]

Ok


Ok, I applied your suggestions, and the result is:
1) in ddns -> server certificate the Status show always the word updating
2) in ddns -> server certificate the date of expires is 2028/5/5
3) sometimes in the system log appears this messages :
Dec 14 22:54:59 modprobe: module nf_conntrack_proto_gre not found in modules.dep
Dec 14 22:54:59 modprobe: module nf_nat_proto_gre not found in modules.dep
Dec 14 22:54:59 modprobe: module nf_conntrack_pptp not found in modules.dep
Dec 14 22:54:59 modprobe: module nf_nat_pptp not found in modules.dep
4) the kernel error in the log appears when I reboot the router with the ssd usb is connect. I try to format the ssd but the problem isn’t solved. If I detach the ssd, and reboot the router and when the router is up I attach the ssd ... the kernel log doesn’t appears.

Ok if you are going to use a ssd you're likely to need a swap file. I would install AMTM and use the tools inside it to both add a swap file and format the drive properly.

 

[StefanoN]

Ok if you are going to use a ssd you're likely to need a swap file. I would install AMTM and use the tools inside it to both add a swap file and format the drive properly.

This ssd is the same disk that I used with the previous version (.13). On the ssd I had installed the swap file + yazfi guest + diversion + amtm + entware.
After the format I just reinstalled amtm + swap file + yazfi guest + entware

With the previous version I never see this type of kernel log.