Release Asuswrt-Merlin 386.11 is now available for AC models

[Lost Dog]

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 ?

You did a reset of the router and then this happened? Sounds like the key changed when the router reset. From the screenshot it looks like you are using windows... No idea how to delete the old key on Windows but here's how to do it on linux (and it may point you in the right direction):

3 ways to fix Host key verification failed in ssh - howtouselinux

Whenever we connect to a server via SSH, that server's public key is stored in our home directory. The file is called known_hosts.When we reconnect to the same server, the SSH connection will verify the current public key matches the one we have saved in our known_hosts file.If the server's key...

www.howtouselinux.com

 

[RMerlin]

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 ?

Edit the known_hosts file mentioned in that error message, and remove line 3 it mentions. Your router generated a new hostkey, and your SSH client needs to be told to forget the old key.

 

[John Adler]

thks LostDog, I´ll give a try

 

[John Adler]

Edit the known_hosts file mentioned in that error message, and remove line 3 it mentions. Your router generated a new hostkey, and your SSH client needs to be told to forget the old key.

I don´t know how to access to the known_host file.
or is that in windows?

 

[Twiglets]

It is in windows .... C:\\Users\\<username>/.ssh

 

[RMerlin]

I don´t know how to access to the known_host file.

The path to the file was right in the screenshot you posted. Open it within notepad, it`s just a text file.

 

[Howard_inGA]

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.

Thanks! I have work to do...

 

[Howard_inGA]

Who knows when you rrouter got infected. All I can say is that updaterservice that's crashing is part of a known malware.

As noted, I have work to do! None of these items are present when the router is rolled back to .10; and I guess that is what is messing with my head.
I'm going to verify my .11 download, then reset to default with .10 installed, upload the new clean software, and reconfigure. I hope that gets things running right...
Any problem with this course of action to set it straight?

 

[redbird71]

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

Managed to restore it from a previous version. So - this MIGHT be related with the fact that I reseted VPN Server 1. Was not expecting this behavior as VPN Server 2 was active.

 

[GunnarH]

Zero wifi changes between 386.10 and 386.11. Changes are mostly related to OpenVPN.

$ git log --oneline 386.10..386.11
4bd516ba63 (HEAD -> 386_x, tag: 386.11, origin/386_x) Bumped revision to 386.11 final
0110c092ee Updated documentation
d70162f6f5 Updated documentation
3594bcd8a8 dnsmasq: Fix possible SEGV when no servers defined.
cbe51d77bc httpd: backport from upstream
59b2c6fea3 rom: Clear a few legacy variables for OpenVPN clients 3/4/5 that may still be present
c011310d25 openvpn: updated to 2.6.3
a5d87460eb Updated documentation
971947b898 rom: added OpenVPN client 3/4/5 settings removal script
dcac01bf74 rc: only refresh DDNS on bound6()/deconfig6() events if IPv6 DDNS updates are enabled
54c1516cba httpd: webui: display all client IPv6 addresses on Wireless Log
e27f64de30 curl: updated to 8.0.1
c6ca2ac912 openvpn: updated to 2.6.2
e0b9f53c72 openvpn: updated to 2.6.1
177500f72c Updated documentation
400184649e Merge branch 'ovpnlimit' into 386_x
957e0089de (ovpnlimit) Reduce max OpenVPN client to 2 for RT-AC68U and DSL-AC68U
62d39e1a52 tools: synced copy-prebuilt from master with 386_x branch
0c9c1c7102 wlcevent: move to model-specific, added missing models
727f4bcd5f Bumped revision to 386.11 alpha 1
674071fc9f Bumped revision to 386.11 alpha 1

After second try no problems have been seen .

 

[doczenith1]

reset to default with .10 installed, upload the new clean software, and reconfigure.

Typically you should do the reset after installing the new firmware version but in your case it wouldn't be a bad idea to do it before and after.

 

[Vyzzini]

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
...

I have the exact same issue on AC88U.
I upgraded to 11 on the day of the release and everything went well till today then this problem happened and the wifi connection is now terrible.

EDIT: I did a factory reset and everything's back to normal

 

[Mario64]

I’m currently running 386.7 on an AX68. Should I remain on the 386 branch or move up to the 388 branch? Thanks

 

[L&LD]

Move to 388.

 

[Howard_inGA]

Typically you should do the reset after installing the new firmware version but in your case it wouldn't be a bad idea to do it before and after.

That sounds like a great addition to the plan...

 

[GunnarH]

Lost connectivity to the router (rt-86U) shortly after a scheduled reboot which was performed at 06:00.

May 26 06:29:40 networkmap: Error locking /var/lock//usr/networkmap/nmp_conv_type.js.lock: 2 No such file or directory
May 26 06:29:40 networkmap: Error unlocking -1: 9 Bad file descriptor
May 26 06:29:40 networkmap: Error locking /var/lock//usr/networkmap/nmp_vendor_type.js.lock: 2 No such file or directory
May 26 06:29:40 networkmap: Error unlocking -1: 9 Bad file descriptor
May 26 06:29:40 networkmap: Error locking /var/lock//usr/networkmap/nmp_bwdpi_type.js.lock: 2 No such file or directory
May 26 06:29:40 networkmap: Error unlocking -1: 9 Bad file descriptor

Logging in showed that /usr/networkmap/nmp_bwdpi_type.js.lock did exist.
Where did the prefix /var/lock/ come from ?

 

[drinkingbird]

Only once, unless you flash back to an older version at some point. What the script does is remove the nvram settings from the removed clients. I made it a manual step in case someone flashes this release, was using clients 3-5, then realizes he should have read the bloody changelog before flashing it and wants to downgrade back, without having lost his previous configuration.

If a hard factory reset is done after loading 386.11 does it remove the NVRAM stuff or is the script still needed?

 

[RMerlin]

If a hard factory reset is done after loading 386.11 does it remove the NVRAM stuff or is the script still needed?

A factory default reset would remove all existing settings, so no need to run the script afterwards.

 

[drinkingbird]

A factory default reset would remove all existing settings, so no need to run the script afterwards.

Wasn't sure if the reset would just clear the variables/reset them to default or remove them completely (i.e. would it see that they weren't present in the firmware anymore). Thanks for confirming.

 

[drinkingbird]

A factory default reset would remove all existing settings, so no need to run the script afterwards.

Hard reset -> upgrade -> hard reset again. So far so good, about 6k of NVRAM free, with 4 DHCP reservations and 3 custom client list names.