[Release] Asuswrt-Merlin 384.15 (and 384.13_4) are now available

[immi803]

@immi803 I would suggest a full M&M Config and Nuclear Reset be done on your router.

It is not acting normally at all.

Do not use a backup config file to reconfigure it (do it minimally and manually). Do not blindly input your current setting either. Take it a step at a time until the router proves itself stable. It may be a misconfiguration, intra-code mismatch between firmware or simply hardware failure. Test until each device/client is proven stable and not a problem on the newly configured network.

Please see the link in my signature below for further details and those guides to help you get your router back to a good/known state.

Thanks for your prompt response
I read your nuclear reset post as well as m&m configuration, i already did wps nvram clear and did all manual configurations from scratch, but it's of no avail
What i didn't do yet is firmware restoration utility option, will it help though i don't have any problem with changing firmware etc
If it's hardware failure, is it any way to make sure it's hardware and not software thingy??
Any suggestions are highly appreciated

 

[Annihilator]

Spoiler: log

Feb 25 09:34:33 rc_service: httpds 970:notify_rc restart_ddns_le
Feb 25 09:34:34 start_ddns: update WWW.NO-IP.COM default@no-ip.com, wan_unit 0
Feb 25 09:34:34 inadyn[11312]: In-a-dyn version 2.5 -- Dynamic DNS update client.
Feb 25 09:34:34 inadyn[11312]: Update forced for alias ******.ddns.net, new IP# *6.***.2*.*7
Feb 25 09:34:35 inadyn[11312]: Updating cache for ******.ddns.net
Feb 25 09:34:35 kernel: [Tue Feb 25 09:34:35 GMT 2020]
Feb 25 09:34:35 kernel: Renew: '****.ddns.net'
Feb 25 09:34:36 kernel: [Tue Feb 25 09:34:36 GMT 2020]
Feb 25 09:34:36 kernel: Standalone mode.
Feb 25 09:34:37 kernel: [Tue Feb 25 09:34:37 GMT 2020]
Feb 25 09:34:37 kernel: Registering account
Feb 25 09:34:39 kernel: [Tue Feb 25 09:34:39 GMT 2020]
Feb 25 09:34:39 kernel: Already registered
Feb 25 09:34:39 kernel: [Tue Feb 25 09:34:39 GMT 2020]
Feb 25 09:34:39 kernel: ACCOUNT_THUMBPRINT='***************'
Feb 25 09:34:39 kernel: [Tue Feb 25 09:34:39 GMT 2020]
Feb 25 09:34:39 kernel: Single domain='*************.ddns.net'
Feb 25 09:34:39 kernel: [Tue Feb 25 09:34:39 GMT 2020]
Feb 25 09:34:39 kernel: Getting domain auth token for each domain
Feb 25 09:34:41 kernel: [Tue Feb 25 09:34:41 GMT 2020]
Feb 25 09:34:41 kernel: Getting webroot for domain='**********.ddns.net'
Feb 25 09:34:41 kernel: [Tue Feb 25 09:34:41 GMT 2020]
Feb 25 09:34:41 kernel: Verifying: *********.ddns.net
Feb 25 09:34:41 kernel: [Tue Feb 25 09:34:41 GMT 2020]
Feb 25 09:34:41 kernel: Standalone mode server
Feb 25 09:34:47 kernel: [Tue Feb 25 09:34:47 GMT 2020]
Feb 25 09:34:47 kernel: *******.ddns.net:Verify error:Fetching http://********.ddns.net/.well-known/acme-challenge/*************: Connection refused
Feb 25 09:34:47 kernel: [Tue Feb 25 09:34:47 GMT 2020]
Feb 25 09:34:47 kernel: Please add '--debug' or '--log' to check more details.
Feb 25 09:34:47 kernel: [Tue Feb 25 09:34:47 GMT 2020]
Feb 25 09:34:47 kernel: See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh

Again Problems with Let's Encrypt?

Issued by :
Let's Encrypt Authority X3
Expires on :
2020/2/25

 

[RMerlin]

Heads up - I will be locking this thread in the coming days, since the initial feedback has quieted down, and posts are more about general support requests now. I strongly suggest starting a separate thread if you need help with an issue.

 

[Centrifuge]

I installed alpha 16

Check this thread for alpha build.

 

[L&LD]

Thanks for your prompt response
I read your nuclear reset post as well as m&m configuration, i already did wps nvram clear and did all manual configurations from scratch, but it's of no avail
What i didn't do yet is firmware restoration utility option, will it help though i don't have any problem with changing firmware etc
If it's hardware failure, is it any way to make sure it's hardware and not software thingy??
Any suggestions are highly appreciated

If you follow the guides I suggested and the router still isn't responding as it should, it's RMA time or trash.

But, make sure you follow all the steps.

 

[telUK]

10 days 17hrs uptime since updating from 384.13.

I thought 384.13 was rock solid, 384.15 so far is just as stable.

I did a reset after updating and followed some of @L&LD reset/setup guide.

Thanks

 

[fg64]

Dirty upgrade from 14_2. up 11 Days, 2+ hours with no issues.

Thanks again.

 

[amd7674]

Quick and dirty upgrade from 14_2 to 15_0 on 1900P. 3+ days with no issues to report.

Thank You

 

[rivera]

Can anyone provide any info regarding this error flooding a log in AC68U?
kernel: osl_pktfastfree: free skb for NULL ctfpool

 

[Luizlp10]

Just passed the 14 days milestone with no problems at all. The router automatically rebooted itself because I was playing with Tx power at the 5 GHz band but so far, so good. My log is pretty clean, only advertising Diversion messages and wireless changes when I tweak them. AC86U with 384.15 with L&LD config manual is working solid.

 

[Butterfly Bones]

Can anyone provide any info regarding this error flooding a log in AC68U?
kernel: osl_pktfastfree: free skb for NULL ctfpool

Forum search for the error sting gets a few hits. First is your post, the rest might be worth checking.
https://www.snbforums.com/search/13...:+free+skb+for+NULL+ctfpool&o=date&c[node]=42

 

[rivera]

Forum search for the error sting gets a few hits. First is your post, the rest might be worth checking.

Surely I tried it - with no result.
Mostly this error is mentioned in association with IPv6 & hardware NAT acceleration.
But in my setup there is no IPv6 support - neither on PC nor in ASUS settings (iPv6 disabled).
Of course I can switch hardware NAT acceleration OFF - and yes, these errors do not present in the log, but then speedtest.net shows both DL / UL speeds TWICE less.

 

[r3dDaWn]

Hello, I'm hoping someone can point me to the correct answer. I am trying to do the following:

Enable DNS Rebind Protection (AC-68U), lastest Merlin firmware. My home plex server goes from a local server to remote, so I check the log entries and find:
Feb 24 10:17:24 dnsmasq[13772]: possible DNS-rebind attack detected: 192-168-1-235.abcdefghijklrstuvwxyz012345.plex.direct
So from what I've read I must edit the dnsmasq script to whitelist the plex domain. So do I do the following:
Enable: Enable JFFS custom scripts and configs option
I login to the router
What command do I enter here, must I create a script first or at this point do I type:
/jffs/configs/dnsmasq.conf.add rebind-domain-ok=/plex.direct/
Reboot router
I've never created or enabled any scripts on this router, so I'm lost on the above step. The only thing I wish to do is fix the problem of my home plex server showing remote when connected to it locally. And everything I read shows this is the solution, I just need to know the correct commands to get this done. Thanks!

 

[dave14305]

For simplicity, once you’re logged into the router over ssh, try running these two commands:

echo "rebind-domain-ok=/plex.direct/" >> /jffs/configs/dnsmasq.conf.add

service restart_dnsmasq

No need to reboot if those work.

 

[RMerlin]

I'm going to lock this thread now, since it has run its course (gathering feedback on this specific new release).

Please start a new thread if you need support with any specific feature.