What's new

Release Asuswrt-Merlin 386.7 is now available for all 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!

Status
Not open for further replies.
Maybe related (or not?): it just occurred to me that I “forward” the router’s log to that Pi. These are the last entries:

Code:
2022-07-24T17:20:56+02:00 ac86u kernel: usb 2-2: USB disconnect, device number 2
2022-07-24T17:20:57+02:00 ac86u kernel: Aborting journal on device sda1-8.
2022-07-24T17:20:57+02:00 ac86u kernel: JBD2: Error -5 detected when updating journal superblock for sda1-8.
2022-07-24T17:20:57+02:00 ac86u kernel: EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
2022-07-24T17:20:57+02:00 ac86u kernel: EXT4-fs (sda1): Remounting filesystem read-only
2022-07-24T17:20:57+02:00 ac86u kernel: EXT4-fs (sda1): previous I/O error to superblock detected
2022-07-24T17:20:57+02:00 ac86u kernel: Read-error on swap-device (8:0:310168)
2022-07-24T17:20:57+02:00 ac86u kernel: Read-error on swap-device (8:0:310176)

Looks like an issue with the USB flash drive that I use for Entware?

However, I thought the public key was stored on JFFS, so I’m not sure this is related?
 
So have the channel selection options have changed from 386.6 to 386.7? The only 160MHz block available in Band B (U-NII-2C) is channels 100 to 128.


My (UK) RT-AX86U does include selectable channels 120 to 128, but doesn't include any combination that would include channels higher than 140 (as per EU regulations).
Without rolling back I cant tell if this is a change from 386.6 to 386.7, and with getting screamed at, I probably won't get the opportunity to check till later in the week.

Anyway, these are the selection options available, and I'm pretty sure those upper channels when selected, are able to use an 80MHz bandwidth.
channesel.png
 
Last edited:
What VOIP adapter issues were you experiencing? I began noticing some things after updating to the release build of 386.7 with my ATA which were resolved by disabling the SIP Passthrough option. The default setting had never been changed in any other f/w.

Simply not registering any of my lines.
That has been configured this way for many FW to be, and never had any issues before.
That was incredibly weird.


1658688944141.png
 
Simply not registering any of my lines.
That has been configured this way for many FW to be, and never had any issues before.
That was incredibly weird.
I had problems with SIP Passthrough many asus routers and years ago (May have been when I still had Vonage) and it's one of the items on my list to 'Disable' everytime after a full reset.... Using a OBI202 with Google Voice, Sipgate and Callcentric and no problems with it disabled
 
Anyway, these are the selection options available, and I'm pretty sure those upper channels when selected, are able to use an 80MHz bandwidth.
View attachment 43041
That looks the same as mine (no channel 144) except I also have channels 120 to 128 visible. Your control channel is 116 so if you go to System Log - Wireless Log you can see what bandwidth is actually being used. 116/80 would be the same as 116 to 128.
 
Both connection attempts use the same private key of which the public key is stored on the router. This key worked fine a few hours ago.

I can still ping the router. A reboot usually solves this, but I can’t do that right now.
After rebooting I saw the public key of an old SSH private key on the admin page, instead of the one I used earlier today...

How is this possible?

(After re-uploading the public key of my newest private key I could finally SSH into the router again)
 
386.7_2 is now available.

Code:
386.7_2 (24-July-2022)
- UPDATED: openssl to 1.1.1q.
- UPDATED: RT-AX86U driver + SDK updated to latest upstream version
- UPDATED: RT-AX88U and GT-AX11000 radio firmware downgraded to the
           previous version.
- FIXED: Some ISPs would fail to allocate a proper IPv6 prefix (tvlz)
- FIXED: Packet checksum errors logged when using DNSFilter in Router
         mode.  Router mode will no longer use DNAT, except for newer
         HND 5.04 models like the GT-AX6000 or XT12, which work
         properly.  Non-Router mode on HND will still use
         the new DNAT support added in 386.7.
- FIXED: Some SSH clients would end up with an incorrect PATH
         value for the default search path.
- FIXED: OpenVPN clients wouldn't get updated routing tables
         if an OpenVPN server was stopped/started while an
         OpenVPN client was connected
 
386.7_2 is now available.

Code:
386.7_2 (24-July-2022)
- UPDATED: openssl to 1.1.1q.
- UPDATED: RT-AX86U driver + SDK updated to latest upstream version
- UPDATED: RT-AX88U and GT-AX11000 radio firmware downgraded to the
           previous version.
- FIXED: Some ISPs would fail to allocate a proper IPv6 prefix (tvlz)
- FIXED: Packet checksum errors logged when using DNSFilter in Router
         mode.  Router mode will no longer use DNAT, except for newer
         HND 5.04 models like the GT-AX6000 or XT12, which work
         properly.  Non-Router mode on HND will still use
         the new DNAT support added in 386.7.
- FIXED: Some SSH clients would end up with an incorrect PATH
         value for the default search path.
- FIXED: OpenVPN clients wouldn't get updated routing tables
         if an OpenVPN server was stopped/started while an
         OpenVPN client was connected



Lool
And I just thought about it 1m ago.
Its madness

Running to update
 
Are these fixed in 386.7.2
CVE-2022-23970, CVE-2022-23971, CVE-2022-23972, CVE-2022-23973, CVE-2022-25595, CVE-2022-25596, CVE-2022-25597, CVE-2022-26376,CVE-2021-34174,CVE-2018-1160, CVE-2022-26376,CVE-2022-0778.Fixed Stored XSS vulnerability.
 
Are these fixed in 386.7.2
CVE-2022-23970, CVE-2022-23971, CVE-2022-23972, CVE-2022-23973, CVE-2022-25595, CVE-2022-25596, CVE-2022-25597, CVE-2022-26376,CVE-2021-34174,CVE-2018-1160, CVE-2022-26376,CVE-2022-0778.Fixed Stored XSS vulnerability.
Changes are in the included Changelog.
 
Weird after 386.7.2 firmware update and reboot, firmware version did not change. Tried one more time, still shows 386.7_1-gd1340bd88e after update and reboot. Hmm Update, transposed 68 for 86 for the AX model, my bad not having my glasses on. Disregard error.

Updated successfully. :)
 
Last edited:
Weird after 386.7.2 firmware update and reboot, firmware version did not change. Tried one more time, still shows 386.7_1-gd1340bd88e after update and reboot. Hmm
What router? Try rebooting without any USB drive(s), and try again.
 
Updating Now thank you sir.
 
Upgraded and smoothly running on AX88U + AC5300 AiMesh node.

Does anybody know what were the supposed improvements of the radio firmware for AX88U that have had to be downgraded in this latest build? Is that a problem on Asus's side?
 
All AX58U / AC68U Units great so far.
Thanks
 
First time I ever updated the same router twice on the same day. LOL

Both versions seem to do their jobs. Thanks, RMerlin!
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

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