Menu
What's new
By:
Filters Better Search

Release Asuswrt-Merlin 386.11 is now available for AC models

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RT-AC68U

Quick & dirty updated from 386.10 to 386.11. Everything was fine except all WiFi connections were briefly disconnecting every 24 hours since the time it was updated. Didn't consider checking RAM/NVRAM usage. Maybe firmware related, maybe not. I'll probably wait until the next release and factory reset and manually re-enter everything.

(Reading the comments here, possibly something to do with "scheduling a restart of the firewall"?)
 
RMerlin said:
- FIXED: DDNS was being refreshed every time IPv6 bound6() event
occured even if IPv6 DDNS update was disabled.
Click to expand...
Just to clarify on this one.
I am still getting DDNS update messages every 30 minutes on the this 386.11 version.
I had thought that this fix was to stop a DDNS refresh from happening every time there is a IPv6 bound6() event, but re-reading, was the fix there just to stop the DDNS update from occurring is the IPv6 DDNS update is disabled?

A shame because this log entry only started appearing for me in 386.10, and my IPv6 address isn't actually changing every 30 minutes.

I was hoping the fix would stop the spammy DDNS log entries for me. Is this instead a sign that my ISP and/or router is misbehaving?
 
Wade Coxon said:
I had thought that this fix was to stop a DDNS refresh from happening every time there is a IPv6 bound6() event, but re-reading, was the fix there just to stop the DDNS update from occurring is the IPv6 DDNS update is disabled?
Click to expand...
That's only if your issue is related to IPv6. If you IPv4 DDNS isn't updating properly, it will still get refreshed.
 
Dirty update from 386.10 to 386.11 on RT-AC66U B1.
386.10 NVRAM usage: 61733 / 65536 bytes
386.11 NVRAM usage after f/w update: 61669 bytes
386.11 NVRAM usage after clear_vpnclients.sh: 59327 bytes
All seems to be OK.
Thanks @RMerlin
 
Does this version 386.11 FW have the security updates from the ASUS RT-AC86U Firmware version 3.0.0.4.386.51529?

RT-AC86U｜WiFi Routers｜ASUS Global

ASUS has a range of wireless routers suitable for every purpose. Whether it's for your home, for business trips, or for any other need or environment, there's an ASUS router for you.
www.asus.com www.asus.com
 
kokolo said:
Does this version 386.11 FW have the security updates from the ASUS RT-AC86U Firmware version 3.0.0.4.386.51529?

RT-AC86U｜WiFi Routers｜ASUS Global

ASUS has a range of wireless routers suitable for every purpose. Whether it's for your home, for business trips, or for any other need or environment, there's an ASUS router for you.
www.asus.com www.asus.com
Click to expand...
read the changelog; link in the top post.
Looks to me like this is based on 50757...you'd need to diff the two, but follow along there and observe how there have been other updates to components the firmware uses that may meet or exceed 51529
 
Tried the stable 386.11 release with the same endlessly repeating log entries. After the install and reboot this evening, here is what is showing:

May 21 23:42:23 kernel: gro disabled
May 21 23:42:25 kernel: updateservice/1370: potentially unexpected fatal signal 4.
May 21 23:42:25 kernel: Pid: 1370, comm: updateservice
May 21 23:42:25 kernel: CPU: 0 Tainted: P (2.6.36.4brcmarm #1)
May 21 23:42:25 kernel: PC is at 0x5d364
May 21 23:42:25 kernel: LR is at 0x7ada4
May 21 23:42:25 kernel: pc : [<0005d364>] lr : [<0007ada4>] psr: 20000010
May 21 23:42:25 kernel: sp : 7eb4bc78 ip : cafebabe fp : 005e3828
May 21 23:42:25 kernel: r10: 005e4d18 r9 : 00000000 r8 : 005e4f30
May 21 23:42:25 kernel: r7 : 00000014 r6 : 00000000 r5 : 00000000 r4 : 00000000
May 21 23:42:25 kernel: r3 : 00000000 r2 : 7eb4be19 r1 : 7eb3c0b8 r0 : 00000000
May 21 23:42:25 kernel: Flags: nzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 21 23:42:25 kernel: Control: 10c53c7d Table: 4f58404a DAC: 00000015
May 21 23:42:27 avahi-daemon[1410]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 21 23:42:32 kernel: lighttpd-arppin/1344: potentially unexpected fatal signal 11.
May 21 23:42:32 kernel: Pid: 1344, comm: lighttpd-arppin
May 21 23:42:32 kernel: CPU: 1 Tainted: P (2.6.36.4brcmarm #1)
May 21 23:42:32 kernel: PC is at 0xd860
May 21 23:42:32 kernel: LR is at 0xd84c
May 21 23:42:32 kernel: pc : [<0000d860>] lr : [<0000d84c>] psr: a0000010
May 21 23:42:32 kernel: sp : 7ecddbd8 ip : 0001a254 fp : 7ecddd74
May 21 23:42:32 kernel: r10: 7ecdddb8 r9 : 0000e1c4 r8 : 00008f08
May 21 23:42:32 kernel: r7 : 7ecddf2b r6 : 00000003 r5 : 7ecdde44 r4 : 2b60f4f8
May 21 23:42:32 kernel: r3 : 00000000 r2 : 00000000 r1 : 7ecddc42 r0 : ffffffc7
May 21 23:42:32 kernel: Flags: NzCv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
May 21 23:42:33 kernel: Control: 10c53c7d Table: 4f88c04a DAC: 00000015
May 21 23:42:36 kernel: SHN Release Version: 2.0.2 3a73e78
May 21 23:42:36 kernel: UDB Core Version: 0.2.20
May 21 23:42:36 kernel: sizeof forward pkt param = 192
May 21 23:42:41 crond[607]: time disparity of 2653837 minutes detected
May 21 23:45:06 kernel: out_fd is a pipe
May 21 23:45:06 kernel: out_fd is a pipe
May 21 23:45:06 kernel: out_fd is a pipe
May 21 23:45:06 kernel: out_fd is a pipe
May 21 23:45:06 kernel: out_fd is a pipe
May 21 23:45:06 kernel: out_fd is a pipe
May 21 23:45:07 kernel: out_fd is a pipe
May 21 23:45:07 kernel: out_fd is a pipe

These kernel: 'out_fd is a pipe' just keep coming. This was the same issue that caused me to roll back to .10 stable after trying to use the alpha in the 11 cycle.

Here are the stored post results (May 5) in the firmware:

May 5 01:05:16 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06, pc=0x8000f9d8 lr=0x8000f9cc ignored.
May 5 01:05:16 kernel: Mount-cache hash table entries: 512
May 5 01:05:16 kernel: CPU1: Booted secondary processor
May 5 01:05:16 kernel: Found a AMD NAND flash:
May 5 01:05:16 kernel: Total size: 128MB
May 5 01:05:16 kernel: Block size: 128KB
May 5 01:05:16 kernel: Page Size: 2048B
May 5 01:05:16 kernel: OOB Size: 64B
May 5 01:05:16 kernel: Sector size: 512B
May 5 01:05:16 kernel: Spare size: 16B
May 5 01:05:16 kernel: ECC level: 8 (8-bit)
May 5 01:05:16 kernel: Device ID: 0x 1 0xf1 0x80 0x1d 0x 1 0xf1
May 5 01:05:16 kernel: bio: create slab <bio-0> at 0
May 5 01:05:16 kernel: PCI: no core
May 5 01:05:16 kernel: PCI: no core
May 5 01:05:16 kernel: PCI: Fixing up bus 0
May 5 01:05:16 kernel: PCI: Fixing up bus 0
May 5 01:05:16 kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
May 5 01:05:16 kernel: PCIE 0001:01:0000: ASMedia UpPort mem_base 0x08000000, mem_limit 0x09ffffff
May 5 01:05:16 kernel: PCI: Fixing up bus 1
May 5 01:05:16 kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
May 5 01:05:16 kernel: PCIE 0001:02:0018: ASMedia DownPort mem_base 0x0b000000, mem_limit 0x0cffffff
May 5 01:05:16 kernel: PCIE 0001:02:0018: ASMedia DownPort Link speed is GEN2
May 5 01:05:16 kernel: PCIE 0001:02:0018: ASMedia DownPort Link status 0x7012
May 5 01:05:16 kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
May 5 01:05:16 kernel: PCIE 0001:02:0038: ASMedia DownPort mem_base 0x0e000000, mem_limit 0x0fffffff
May 5 01:05:16 kernel: PCIE 0001:02:0038: ASMedia DownPort Link speed is GEN2
May 5 01:05:16 kernel: PCIE 0001:02:0038: ASMedia DownPort Link status 0x7012
May 5 01:05:16 kernel: PCI: Fixing up bus 2
May 5 01:05:16 kernel: PCI: Fixing up bus 3
May 5 01:05:16 kernel: PCI: Fixing up bus 4
May 5 01:05:16 kernel: PCI: Fixing up bus 0
May 5 01:05:16 kernel: PCI: Fixing up bus 1
May 5 01:05:16 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
May 5 01:05:16 kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
May 5 01:05:16 kernel: PCIE: Doing ASMedia switch Init...Test Read = 20010002
May 5 01:05:16 kernel: pflash: found no supported devices
May 5 01:05:16 kernel: bcmsflash: found no supported devices
May 5 01:05:16 kernel: Boot partition size = 524288(0x80000)
May 5 01:05:16 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
May 5 01:05:16 kernel: === PPTP init ===
May 5 01:05:16 kernel: Spare area=64 eccbytes 56, ecc bytes located at:
May 5 01:05:16 kernel: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 18 19 20 21 22 23 24 25 26 27 28 29 30 31 34 35 36 37 38 39 40 41 42 43 44 45 46 47 50 51 52 53 54 55 56 57 58 59 60 61 62 63
May 5 01:05:16 kernel: Available 7 bytes at (off,len):
May 5 01:05:16 kernel: (1,1) (16,2) (32,2) (48,2) (0,0) (0,0) (0,0) (0,0)
May 5 01:05:16 kernel: Options: NO_AUTOINCR,NO_READRDY,BBT_SCAN2NDPAGE,
May 5 01:05:16 kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
May 5 01:05:16 kernel: ctf: module license 'Proprietary' taints kernel.
May 5 01:05:16 kernel: Disabling lock debugging due to kernel taint
May 5 01:05:16 kernel: et_module_init: passivemode set to 0x0
May 5 01:05:16 kernel: et_module_init: txworkq set to 0x0
May 5 01:05:16 kernel: et_module_init: et_txq_thresh set to 0xce4
May 5 01:05:16 kernel: et_module_init: et_rxlazy_timeout set to 0x3e8
May 5 01:05:16 kernel: et_module_init: et_rxlazy_framecnt set to 0x20
May 5 01:05:16 kernel: et_module_init: et_rxlazy_dyn_thresh set to 0
May 5 01:05:16 kernel: et0: bhdr_sz 0 bhdr_roff 0
May 5 01:05:16 kernel: fwd0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.303 (r666427)
May 5 01:05:16 kernel: et1: bhdr_sz 0 bhdr_roff 0
May 5 01:05:16 kernel: fwd1: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.303 (r666427)
May 5 01:05:16 kernel: robo_eee_advertise_init: GPHY0: EEE advertisement is disabled
May 5 01:05:16 kernel: robo_eee_advertise_init: GPHY1: EEE advertisement is disabled
May 5 01:05:16 kernel: robo_eee_advertise_init: GPHY2: EEE advertisement is disabled
May 5 01:05:16 kernel: robo_eee_advertise_init: GPHY3: EEE advertisement is disabled
May 5 01:05:16 kernel: robo_eee_advertise_init: GPHY4: EEE advertisement is disabled
May 5 01:05:16 kernel: agg_attach: bhdr_enable 1
May 5 01:05:16 kernel: et2: bhdr_sz 4 bhdr_roff 12
May 5 01:05:16 kernel: et2: vlan1map 0xbe
May 5 01:05:16 kernel: et2: vlan2map 0x1
May 5 01:05:16 kernel: eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.303 (r666427)
May 5 01:05:16 kernel: dpsta_init: Jun 12 2019 19:06:52 msglevel 0x1
May 5 01:05:16 kernel: PCI_PROBE: bus 3, slot 0,vendor 14E4, device 4365(good PCI location)
May 5 01:05:16 kernel: PCI: Enabling device 0001:03:00.0 (0140 -> 0142)
May 5 01:05:16 kernel: dhd_attach(): thread:dhd_watchdog_thread:81 started
May 5 01:05:16 kernel: dhd_detach(): thread:dhd_watchdog_thread:81 terminated OK
May 5 01:05:16 kernel: dhd_attach(): thread:dhd_watchdog_thread:82 started
May 5 01:05:16 kernel: Dongle Host Driver, version 1.363.2 (r665954)
May 5 01:05:16 kernel: Compiled in drivers/net/wireless/bcmdhd on Dec 26 2022 at 16:38:58
May 5 01:05:16 kernel: Register interface [eth1] MAC: 60:45:cb:cc:bb:90
May 5 01:05:16 kernel: PCI_PROBE: bus 4, slot 0,vendor 14E4, device 4365(good PCI location)
May 5 01:05:16 kernel: PCI: Enabling device 0001:04:00.0 (0140 -> 0142)
May 5 01:05:16 kernel: dhd_attach(): thread:dhd_watchdog_thread:86 started
May 5 01:05:16 kernel: Dongle Host Driver, version 1.363.2 (r665954)
May 5 01:05:16 kernel: Compiled in drivers/net/wireless/bcmdhd on Dec 26 2022 at 16:38:58
May 5 01:05:16 kernel: Register interface [eth2] MAC: 60:45:cb:cc:bb:94
May 5 01:05:16 kernel: PCI_PROBE: bus 1, slot 0,vendor 14E4, device 4365(good PCI location)
May 5 01:05:16 kernel: PCI: Enabling device 0002:01:00.0 (0140 -> 0142)
May 5 01:05:16 kernel: dhd_attach(): thread:dhd_watchdog_thread:8a started
May 5 01:05:16 kernel: Dongle Host Driver, version 1.363.2 (r665954)
May 5 01:05:16 kernel: Compiled in drivers/net/wireless/bcmdhd on Dec 26 2022 at 16:38:58
May 5 01:05:16 kernel: Register interface [eth3] MAC: 60:45:cb:cc:bb:98
May 5 01:05:16 kernel: Register interface [wl0.1] MAC: 60:45:cb:cc:bb:90
May 5 01:05:17 kernel: Register interface [wl1.1] MAC: 60:45:cb:cc:bb:94
May 5 01:05:21 acsd: selected channel spec: 0x1007 (7)
May 5 01:05:21 acsd: Adjusted channel spec: 0x1007 (7)
May 5 01:05:21 acsd: selected channel spec: 0x1007 (7)
May 5 01:05:21 acsd: acs_set_chspec: 0x1007 (7) for reason APCS_INIT
May 5 01:05:22 avahi-daemon[656]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May 5 01:05:22 acsd: selected channel spec: 0xe22a (44/80)
May 5 01:05:22 acsd: Adjusted channel spec: 0xe22a (44/80)

After these post entries, the sequence first noted begins and just rolls on...

It looks like a roll back to .10 again, but I sure would like to know what is causing all this.
 
Last edited:
Howard_inGA said:
Tried the stable 386.11 release with the same endlessly repeating log entries.
Click to expand...
Your router is infected with a malware. Factory default reset and reconfigure.
 
Can someone kindly post the content of the clear_vpnclients.sh script?

I'm running Asus-standard version of the firmware on my parent's RT-AC66U_B1 so I don't have access to it and would like to see the content of the script.

Many thanks
 
RMerlin said:
Your router is infected with a malware. Factory default reset and reconfigure.
Click to expand...
Thanks, Eric!
I'll get it done, but I don't understand how things are fine in .10, but the upgrade triggers the errors? Any illumination on why?
 
Howard_inGA said:
Thanks, Eric!
I'll get it done, but I don't understand how things are fine in .10, but the upgrade triggers the errors? Any illumination on why?
Click to expand...
Please go to https://www.asuswrt-merlin.net/download and note the SHA256 signatures table below the download links.
Everybody should be using the appropriate one to verify the integrity of downloaded firmware BEFORE installing it.
There isn't a tutorial/sticky (that I'm aware of or have seen) about running a check with published signature here on this forum, but a web search should sort you out quickly; use it when/wherever you can with any software/computer when offered the option to do so. The process itself doesn't take long (in comparison to sorting out router etc issues and resolving them), and should give you some peace of mind that an upgrade will proceed smoothly/correctly.
Trust but verify.

But first, is your router/network secure from outside meddling?
Securing your router is well documented on this forum, and you know how to find info here...
If you've done these two things, you will have prevented 99% of troubles like this from happening again.
 
maxbraketorque said:
After going from 386.10_a1 to 386.11, I'm getting the following new entries in the log file:

Code: 
May 14 19:34:58 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x1
May 14 19:34:58 kernel: bcm63xx_nand ff801800.nand: intfc status f80000e0
May 14 19:41:12 kernel: bcm63xx_nand ff801800.nand: timeout waiting for command 0x4
May 14 19:41:12 kernel: bcm63xx_nand ff801800.nand: intfc status c80000e0

Seems that this may be related to USB devices, of which I have several connected to the router.
Click to expand...

After updating to AMTM 3.6 and rebooting, these errors have not reappeared. I suspect that the errors were caused by an older version of the AMTM disk check utility.
 
Howard_inGA said:
Any illumination on why?
Click to expand...
Who knows when you rrouter got infected. All I can say is that updaterservice that's crashing is part of a known malware.
 
Lost all VPN username/password info after a forced powercycle (electricity was cut off). Surprisingly I restored the last configuration I saved after the last update 6 days ago and usernames/passwords did NOT come back.

Anybody else exprerienced this? Will load older config saved directly before updating to 386.11 later to see if I am able to restore correctly
 
Hi
back to my problem with ssh command, I did a reset to my router and tried to access with ssh
that was the result:
What should I do now ?
 

Attachments

  • Screenshot 2023-05-23.jpg
    Screenshot 2023-05-23.jpg
    109.4 KB · Views: 166
You must log in or register to reply here.

Similar threads

RMerlin
Release Asuswrt-Merlin 386.14 is now available for AC models
8 9 10
Replies
186
Views
28K
bibikalka
B
RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
2
Replies
28
Views
2K
Tech9
Tech9
RMerlin
  • Locked
Release Asuswrt-Merlin 3004.388.8_2 is now available
22 23 24
Replies
469
Views
58K
aitor_mtb
A
RMerlin
  • Locked
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
2 3 4
Replies
70
Views
11K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models
2 3 4
Replies
79
Views
19K
Tech9
Tech9
Similar threads
Thread starter Title Forum Replies Date
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
RMerlin Release Asuswrt-Merlin 386.14 is now available for AC models Asuswrt-Merlin 186
RMerlin Beta Asuswrt-Merlin 386.14 beta is now available Asuswrt-Merlin 35
RMerlin Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models Asuswrt-Merlin 79
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Release Asuswrt-Merlin 386.12_6 is now available for AC models Asuswrt-Merlin 168
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 28
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2
Yota How to enable port randomization in Asuswrt-Merlin? Asuswrt-Merlin 4
RMerlin Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices Asuswrt-Merlin 70

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 730 (members: 27, guests: 703)
Top