[Nicky]

I suppose it’s a case of “If it works don’t mend it”. When you say “It becomes more interesting if you are using multiple AiMesh nodes”, in what way. I have 3 nodes connected, all of which are hard wired. Is there something else I need to do or look out for?

You need to login in order to vote

[Nicky]

To reboot or not to reboot, that is the question (I feel a Shakespeare moment coming on)?

 

Is it good practice to reboot your router and nodes on a regular basis or only if you start to notice traffic slowing down?

If it is good practice to reboot on a regular basis, then how often and via which method, scheduled or manual?

Liked by:

You need to login in order to vote

[Nicky]

It looks like “3.0.0.4.388_25041-g19153cb” has been released for the ZenWiFi AX Mini .

Firmware version 3.0.0.4_388_25041
– Release Note –

[Security Fixes]
– Resolved command injection vulnerability.
– Resolved DoS vulnerabilities in HTTPD and firewall configuration pages.
– Addressed ARP poisoning vulnerability.
– Addressed information disclosure vulnerability.
– Corrected code execution issue in custom OVPN.
– Corrected an OpenVPN vulnerability categorized as CWE-134.
– Corrected null pointer dereference vulnerabilities.
– Patched OpenSSL vulnerabilities.
– Fix CVE-2022-46871 and CVE-2023-35720.
– Fix CVE-2023-28702 and CVE-2023-28703.
– Fix XSS and self-reflected HTML injection vulnerabilities.
– Enabled and supported ECDSA certificates for Let’s Encrypt.
– Enhanced system stability.
– Enhanced FFmpeg vulnerabilities.
– Enhanced protection for OTA firmware updates and credentials.
– Improved several curl vulnerabilities.
– Improved the cfg server vulnerability.
– Improved WireGuard performance.
– Strengthened defenses against SSH brute force attacks.

• This reply was modified 1 year, 9 months ago by Nicky.

Liked by:

You need to login in order to vote

[Nicky]

The Check Firmware button has worked in the past, it’s only been the past few days it’s been reporting that it’s unable to connect to the server, normally it would report “The router’s current firmware is the latest version”. When I checked via the App, it said “Your AiMesh system is up to date”.

With regards to the DNS, I’ve always set my routers to Cloudflare 1.1.1.1 & 1.0.0.1 which has never been an issue in the past, but out of interest I changed it back to “Get the DNS IP from your ISP automatically” and the result was the same.

Update. Something didn’t feel right so I rebooted my Virgin Media hub and now it’s working. Note to self, when you reboot your router remember to also reboot your Modem.

Liked by:

You need to login in order to vote

[Nicky]

I do (see screenshot).

 

Attachments:

1. 

   Screenshot-1.jpg
   

You need to login in order to vote

[Nicky]

Are there issues with the ASUS servers, because for the past few days I’ve been getting this error when checking for updates for my ZENWiFi AX?

“The router cannot connect to ASUS server to check for the firmware update. Please download the latest firmware from ASUS Product Support Site and do manually upgrade. Check on FAQ for more instructions.”

You need to login in order to vote

[Nicky]

Back in February with “FW_ZENWIFI_XT8_300438822525” and it was a pain in the arse, having to set it up with all the nodes, let it settle down for an hour or so and then setup the fixed IPs and port forwarding’s. Not something I relish doing too often.

You need to login in order to vote

[Nicky]

I’ll send them feedback straight away.

Yes I am seeing the client list not updating on both the main router and the three nodes (hardwired) and as previously mentioned, I know the client list has always been a bit flaky, but on this build, devices (both hardwired and Wi-Fi) are dropping on and off the list quite regularly, but they do remain accessible.

Liked by:

You need to login in order to vote

[Nicky]

Everything seems to be stable, but I’m still getting these entries in the system log:

Apr 14 02:38:50 kernel: swap_free: Bad swap file entry 100133cb
Apr 14 02:38:50 kernel: BUG: Bad page map in process asusdiscovery pte:0099e5a0 pmd:13ef6831
Apr 14 02:38:50 kernel: addr:b6b30000 vm_flags:00000075 anon_vma: (null) mapping:df04f74c index:0
Apr 14 02:38:50 kernel: file:libssl.so.1.1 fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
Apr 14 02:38:50 kernel: CPU: 1 PID: 24433 Comm: asusdiscovery Tainted: P B O 4.1.52 #2
Apr 14 02:38:50 kernel: Hardware name: Generic DT based system
Apr 14 02:38:50 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Apr 14 02:38:50 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Apr 14 02:38:50 kernel: [<c04c76bc>] (dump_stack) from [<c00ab4b0>] (print_bad_pte+0x138/0x1a0)
Apr 14 02:38:50 kernel: [<c00ab4b0>] (print_bad_pte) from [<c00acb0c>] (unmap_single_vma+0x430/0x520)
Apr 14 02:38:50 kernel: [<c00acb0c>] (unmap_single_vma) from [<c00ad9b4>] (unmap_vmas+0x54/0x68)
Apr 14 02:38:50 kernel: [<c00ad9b4>] (unmap_vmas) from [<c00b371c>] (exit_mmap+0xdc/0x1dc)
Apr 14 02:38:50 kernel: [<c00b371c>] (exit_mmap) from [<c002c8d4>] (mmput+0x38/0xe4)
Apr 14 02:38:50 kernel: [<c002c8d4>] (mmput) from [<c002fd34>] (do_exit+0x238/0x934)
Apr 14 02:38:50 kernel: [<c002fd34>] (do_exit) from [<c00311fc>] (do_group_exit+0x38/0xbc)
Apr 14 02:38:50 kernel: [<c00311fc>] (do_group_exit) from [<c0031290>] (__wake_up_parent+0x0/0x18)
Apr 14 02:38:50 kernel: BUG: Bad rss-counter state mm:c732e3c0 idx:0 val:1
Apr 14 02:38:50 kernel: BUG: Bad rss-counter state mm:c732e3c0 idx:2 val:-1

 

You need to login in order to vote

[Nicky]

They where after the latest firmware update and I did a a system reboot (as I always do after an update) via the system setting tab.

You need to login in order to vote

[Nicky]

I had a number of devices bound (bind) to some nodes and after the upgrade they showed as greyed out and not connected. Also, they didn’t show on the routers client list, even though they were accessible from the network. I had to un-bind them from their nods before they would appear on the client list.

I know the client list as always been a bit flaky, but on this build devices (both hard wired and WiFi) are dropping on and off the list quite regularly, but they do remain accessible.

I’m also getting these errors in the system log:-

Apr 12 16:30:08 kernel: CPU: 1 PID: 8719 Comm: ping Tainted: P B O 4.1.52 #2
Apr 12 16:30:08 kernel: Hardware name: Generic DT based system
Apr 12 16:30:08 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Apr 12 16:30:08 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Apr 12 16:30:08 kernel: [<c04c76bc>] (dump_stack) from [<c0093188>] (bad_page+0xcc/0x11c)
Apr 12 16:30:08 kernel: [<c0093188>] (bad_page) from [<c00933f4>] (free_pages_prepare+0x21c/0x264)
Apr 12 16:30:08 kernel: [<c00933f4>] (free_pages_prepare) from [<c0093f68>] (free_hot_cold_page+0x30/0x158)
Apr 12 16:30:08 kernel: [<c0093f68>] (free_hot_cold_page) from [<c00940bc>] (free_hot_cold_page_list+0x2c/0x48)
Apr 12 16:30:08 kernel: [<c00940bc>] (free_hot_cold_page_list) from [<c009a368>] (release_pages+0x204/0x20c)
Apr 12 16:30:08 kernel: [<c009a368>] (release_pages) from [<c00b3760>] (exit_mmap+0x120/0x1dc)
Apr 12 16:30:08 kernel: [<c00b3760>] (exit_mmap) from [<c002c8d4>] (mmput+0x38/0xe4)
Apr 12 16:30:08 kernel: [<c002c8d4>] (mmput) from [<c002fd34>] (do_exit+0x238/0x934)
Apr 12 16:30:08 kernel: [<c002fd34>] (do_exit) from [<c00311fc>] (do_group_exit+0x38/0xbc)
Apr 12 16:30:08 kernel: [<c00311fc>] (do_group_exit) from [<c0031290>] (__wake_up_parent+0x0/0x18)
Apr 12 16:30:08 kernel: BUG: Bad rss-counter state mm:ccf18900 idx:0 val:-1

Apr 12 19:33:26 kernel: BUG: Bad page map in process dhcpc_lease pte:00000001 pmd:13ef6831
Apr 12 19:33:26 kernel: page:dfbf8000 count:0 mapcount:-1 mapping: (null) index:0x0
Apr 12 19:33:26 kernel: flags: 0x400(reserved)
Apr 12 19:33:26 kernel: page dumped because: bad pte
Apr 12 19:33:26 kernel: addr:b6d30000 vm_flags:00000075 anon_vma: (null) mapping:df04f8cc index:15f
Apr 12 19:33:26 kernel: file:libcrypto.so.1.1 fault:filemap_fault mmap:generic_file_readonly_mmap readpage:squashfs_readpage
Apr 12 19:33:26 kernel: CPU: 0 PID: 16830 Comm: dhcpc_lease Tainted: P B O 4.1.52 #2
Apr 12 19:33:26 kernel: Hardware name: Generic DT based system
Apr 12 19:33:26 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Apr 12 19:33:26 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Apr 12 19:33:26 kernel: [<c04c76bc>] (dump_stack) from [<c00ab4b0>] (print_bad_pte+0x138/0x1a0)
Apr 12 19:33:26 kernel: [<c00ab4b0>] (print_bad_pte) from [<c00acb50>] (unmap_single_vma+0x474/0x520)
Apr 12 19:33:26 kernel: [<c00acb50>] (unmap_single_vma) from [<c00ad9b4>] (unmap_vmas+0x54/0x68)
Apr 12 19:33:26 kernel: [<c00ad9b4>] (unmap_vmas) from [<c00b371c>] (exit_mmap+0xdc/0x1dc)
Apr 12 19:33:26 kernel: [<c00b371c>] (exit_mmap) from [<c002c8d4>] (mmput+0x38/0xe4)
Apr 12 19:33:26 kernel: [<c002c8d4>] (mmput) from [<c002fd34>] (do_exit+0x238/0x934)
Apr 12 19:33:26 kernel: [<c002fd34>] (do_exit) from [<c00311fc>] (do_group_exit+0x38/0xbc)
Apr 12 19:33:26 kernel: [<c00311fc>] (do_group_exit) from [<c0031290>] (__wake_up_parent+0x0/0x18)
Apr 12 19:33:26 kernel: BUG: Bad rss-counter state mm:c71f8040 idx:0 val:-1

You need to login in order to vote

[Nicky]

Thank you so much.

There is a lot of useful information here, particularly with regards to the theoretical maximums.

You need to login in order to vote

[Nicky]

Hi,

The two posts are not the same entry, they have been cut and pasted as was in the log. The router has not crashed (yet). It’s just the error log, I’ve never seen this before and was getting a little curious as to what and why?

I’ve just checked the log again and it’s not reoccurred since.

You need to login in order to vote

[Nicky]

It’s there again?

The CPU and Ram are not maxed out.

Mar 22 17:45:49 kernel: CPU: 1 PID: 19422 Comm: asd Tainted: P O 4.1.52 #2
Mar 22 17:45:49 kernel: Hardware name: Generic DT based system
Mar 22 17:45:49 kernel: task: d91b8400 ti: d19b0000 task.ti: d19b0000
Mar 22 17:45:49 kernel: PC is at 0xb6892ec0
Mar 22 17:45:49 kernel: LR is at 0xb6893bb0
Mar 22 17:45:49 kernel: pc : [<b6892ec0>] lr : [<b6893bb0>] psr: 80000010
Mar 22 17:45:49 kernel: sp : bebea340 ip : b68a7150 fp : b68961f8
Mar 22 17:45:49 kernel: r10: 00024164 r9 : b68960c0 r8 : 00000000
Mar 22 17:45:49 kernel: r7 : 01fd7c18 r6 : 01fd79c0 r5 : bebea360 r4 : 01ff4428
Mar 22 17:45:49 kernel: r3 : b6502428 r2 : 00000000 r1 : 00000080 r0 : 00000000
Mar 22 17:45:49 kernel: Flags: Nzcv IRQs on FIQs on Mode USER_32 ISA ARM Segment user
Mar 22 17:45:49 kernel: Control: 10c5387d Table: 0e2b404a DAC: 00000015
Mar 22 17:45:49 kernel: CPU: 1 PID: 19422 Comm: asd Tainted: P O 4.1.52 #2
Mar 22 17:45:49 kernel: Hardware name: Generic DT based system
Mar 22 17:45:49 kernel: [<c00270a0>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Mar 22 17:45:49 kernel: [<c0022cf8>] (show_stack) from [<c04c76bc>] (dump_stack+0x8c/0xa0)
Mar 22 17:45:49 kernel: [<c04c76bc>] (dump_stack) from [<c003ad2c>] (get_signal+0x490/0x558)
Mar 22 17:45:49 kernel: [<c003ad2c>] (get_signal) from [<c0022290>] (do_signal+0xc8/0x3ac)
Mar 22 17:45:49 kernel: [<c0022290>] (do_signal) from [<c0022718>] (do_work_pending+0x94/0xa4)
Mar 22 17:45:49 kernel: [<c0022718>] (do_work_pending) from [<c001f58c>] (work_pending+0xc/0x20)
Mar 22 17:45:49 rc_service: service 21670:notify_rc restart_firewall

This is my current set up, all  hard wired.

ZenWiFi AX
Current Version : 3.0.0.4.388_22525-gd35b8fe

AiMesh Node
ZenWiFi AX Mini
Current Version : 3.0.0.4.386_49599-g8352df7

ZenWiFi AX Mini
Current Version : 3.0.0.4.386_49599-g8352df7

ZenWiFi AX
Current Version : 3.0.0.4.388_22525-gd35b8fe

You need to login in order to vote

[Nicky]

Mine is normally around 118MB, It maybe because I have around 72 devices connected, most of which are just IoT devices?

You need to login in order to vote

[Author]

Posts