[Release] Asuswrt-Merlin 384.12 is now available

[PeterDNA]

Stock Asus firmware runs fairly well on AX-88U but now on this one I'm getting some weird issues, which require reboot for internet to comeback online, i think it's related more to WAN Aggregations since my WAN is overprovisioned and I'm getting around 1.3GB/s download via this method. Here is the last part of the log before router requires reboot for WAN to comeback online.

Jun 30 12:13:52 kernel: Init chrdev /dev/idp with major 190
Jun 30 12:13:52 kernel: tdts: tcp_conn_max = 8000
Jun 30 12:13:52 kernel: tdts: tcp_conn_timeout = 300 sec
Jun 30 12:13:54 kernel: SHN Release Version: 2.0.1 0679c74
Jun 30 12:13:54 kernel: UDB Core Version: 0.2.18
Jun 30 12:13:54 kernel: Init chrdev /dev/idpfw with major 191
Jun 30 12:13:54 kernel: IDPfw: flush fc
Jun 30 12:13:54 kernel: IDPfw: IDPfw is ready
Jun 30 12:13:54 kernel: sizeof forward pkt param = 280
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:54 BWDPI: fun bitmap = 3
Jun 30 12:13:59 kernel: net_ratelimit: 16582 callbacks suppressed
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:13:59 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: net_ratelimit: 9190 callbacks suppressed
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1
Jun 30 12:14:04 kernel: protocol 0800 is buggy, dev eth1

 

[Delusion]

Stock Asus firmware runs fairly well on AX-88U but now on this one I'm getting some weird issues, which require reboot for internet to comeback online, i think it's related more to WAN Aggregations since my WAN is overprovisioned and I'm getting around 1.3GB/s download via this method. Here is the last part of the log before router requires reboot for WAN to comeback online.

Happens to me when I enable IPV6 Passthrough. Disabling ipv6 passthrough solves this "protocol 0800 is buggy" issue for me .But WAN Aggregation is something else. I hope there will be a fix

 

[RT-N66U]

• Jul 1 02:27:22 watchdog: start ddns.
• Jul 1 02:27:22 rc_service: watchdog 244:notify_rc start_ddns
• Jul 1 02:27:22 start_ddns: update FREEDNS.AFRAID.ORG default@freedns.afraid.org, wan_unit 0
• Jul 1 02:27:23 inadyn[12023]: In-a-dyn version 2.5 -- Dynamic DNS update client.
• Jul 1 02:27:25 inadyn[12023]: Update forced for alias 123123123.blahblah.com, new IP# 123.123.123.132
• Jul 1 02:27:29 inadyn[12023]: HTTP(S) Transaction failed, error 36: Temporary network error (HTTPS send)

Any idea? Started happening after the update.

 

[Mathieu]

Dirty upgrade from 11_2
Usual complaints during the disconnect/reconnect phases (forgive them for they know not...). At present, all seems quiet on the western front.
Thank you Eric.

Upgraded Diversion and AMTM too, courtesy of @thelonelycoder.
btw , I have an addless snbforums.com page, and although I am not especially bothered, I thought Diversion was by default allowing adds from this forum.

Cheers big ears
[Edited for clarity of the post]

 

[dosborne]

Transaction failed, error 36: Temporary network error

My guess would be exactly what the error message says.

 

[Jumpstarter]

• Jul 1 02:27:22 watchdog: start ddns.
• Jul 1 02:27:22 rc_service: watchdog 244:notify_rc start_ddns
• Jul 1 02:27:22 start_ddns: update FREEDNS.AFRAID.ORG default@freedns.afraid.org, wan_unit 0
• Jul 1 02:27:23 inadyn[12023]: In-a-dyn version 2.5 -- Dynamic DNS update client.
• Jul 1 02:27:25 inadyn[12023]: Update forced for alias 123123123.blahblah.com, new IP# 123.123.123.132
• Jul 1 02:27:29 inadyn[12023]: HTTP(S) Transaction failed, error 36: Temporary network error (HTTPS send)

Any idea? Started happening after the update.

there is possibly a setting inside your inadyn.conf that is not working with afraid setup like it should or shouldn't recommendations is to review your config file for unnecessary or incomplete settings.

 

[orion44]

ProtonVPN client no longer works on 384.12 and hangs indefinitely while attempting to connect. "Error check configuration"
Changing new Inbound Firewall settings to Allow/Block have no effect.

Currently using @Jack Yaz's YazFi 3.2.2 to redirect VPN Client (ProtonVPN) traffic to guest wireless SSID. Is this a known issue?

 

[SNBForums User]

Anyone else Noticing issues with samba sharing ?

I can see the router fine but the drive doesn't always show here and you can't map the drive

No issues on the pc end as i can map my freenas drives fine.

Yep, same issue. Attempting to access existing maps in Win 10 results in error message that connection has not been reestablished. Android-based media server reports that Samba shares not connected. Reversion to 384.11_2 fixes all issues.

 

[hotsauce2007]

What kind of drops? I am still on older firmware , but also on 86u

The router just get stuck with the connection and drop it, I have to restart it to get it working again, I have no idea about what this happen, but looks like it happens after a few days, the longest time that I got with no drops was 25 days ( I use uptime robot to measure it )

 

[Kingp1n]

Do you use Diversion? run the command : top
and check what process is eating your cpu. I had some issues with diversion before, where even with diversion shell history disabled, after flashing a FW , the process of shell history was eating CPU.
Run the command top and kill the process . (kill -9 PID_NUMBER)
PID_NUMBER = the process number on the first column that corresponds to the process you want to kill)

Delusion thansk for the information...it was Diversion causing this which I use the conmand to stop it. Does this deactivate diversion?

 

[Delusion]

Delusion thansk for the information...it was Diversion causing this which I use the conmand to stop it. Does this deactivate diversion?

No ... you can disable the diversion shell history by typing : sh in Diversion main menu.
You can always go to Diversion main menu, type d, disable diversion and then enable it to be sure it is working and active (or just check if ads are blocked without any ad blocker extension) .

 

[Xentrk]

ProtonVPN client no longer works on 384.12 and hangs indefinitely while attempting to connect. "Error check configuration"
Changing new Inbound Firewall settings to Allow/Block have no effect.

Currently using @Jack Yaz's YazFi 3.2.2 to redirect VPN Client (ProtonVPN) traffic to guest wireless SSID. Is this a known issue?

Look in the system log for clues.

 

[Magnus33]

Yep, same issue. Attempting to access existing maps in Win 10 results in error message that connection has not been reestablished. Android-based media server reports that Samba shares not connected. Reversion to 384.11_2 fixes all issues.

There certainly is a bug in this version which is preventing things from communicating correctly.

 

[Pergola Fabio]

upgraded fro 389.9 to 389.12 , all OK
besides still dcd crashes in log, but thats normal i think ?

 

[TeHashX]

Yep, same issue. Attempting to access existing maps in Win 10 results in error message that connection has not been reestablished. Android-based media server reports that Samba shares not connected. Reversion to 384.11_2 fixes all issues.

Same here, can't connect anymore from win10 with share name only by ip and only with smbv1 not v2

 

[WET]

upgraded fro 389.9 to 389.12 , all OK
besides still dcd crashes in log, but thats normal i think ?

Yes normal I still get them constantly if I keep any of the TrendMicro stuff turned on my RT-AC86U.

 

[Diamond67]

Yep, same issue. Attempting to access existing maps in Win 10 results in error message that connection has not been reestablished.

After updating to fw 384.12, I have had some trouble (especially just after rebooting Windows 10 computers because of installed Windows Updates etc.) connecting to mapped drives (router samba shares).

 

[ColinTaylor]

After updating to fw 384.12, I have had some trouble (especially just after rebooting Windows 10 computers because of installed Windows Updates etc.) connecting to mapped drives (router samba shares).

This sounds similar to this post. Can you check that the "netbios name" is set correctly in /etc/smb.conf and also that the nmbd process is running.

 

[ItsMeDude]

After updating to fw 384.12, I have had some trouble (especially just after rebooting Windows 10 computers because of installed Windows Updates etc.) connecting to mapped drives (router samba shares).

I had an issue like this awhile ago that was cause by a Windows 10 update. I added this as one line

pc_replace "store dos attributes = yes" "store dos attributes = no" $CONFIG

to my smb.postconf script on the router, and added it to my other smb configs on all of my Linux based rigs. It all works after that. Give it a try, and see if that works for ya.

 

[BobbyFlobby]

There certainly is a bug in this version which is preventing things from communicating correctly.

I was wondering why infuse on apple tv wouldnt connect to the NAS any longer, thought it was a NAS update that caused the issue, so thanks for sharing.