I notice that RT-AC86U RC2-2,3,4 are the exact same file size 67.6 MB (70,909,972 bytes), and RC2-5,6,7 are the exact same file size 68.0 MB (71,303,188 bytes). Hmmm... am I wasting my time?
View attachment 27057
OE
Run md5 hashes, you'll see.
I notice that RT-AC86U RC2-2,3,4 are the exact same file size 67.6 MB (70,909,972 bytes), and RC2-5,6,7 are the exact same file size 68.0 MB (71,303,188 bytes). Hmmm... am I wasting my time?
View attachment 27057
OE
Now testing RC2-7... node backhaul drooped to 2.4 and log showed VLAN issues until system reboot. System reboot after clean install is advisable, imo.
Port 0 still only Closed on grc.com ShieldsUp! WAN test (?).
OE
This may be very helpful. Would it be possible to write everything to a device on the network instead of a USB drive attached to the router?Moabdave,
This is normally what I do, as I like to do Factory Reset for each new Firmware I installed. I am lazy, I have about 40+ devices that I manually assign IP address. The assumption here is there is a Thumbdrive (with name "ASUS") plugged into one of the USB port of the AiMesh Router. I saved about 10 other NVRAM items. I normally take about 15-30 minutes to setup my AiMesh network from scratch, hope it is useful for you.
First item, saved the DHCP_staticlist, Second item saved the icons you assigned to each device. I think these are the 2 most time consuming items.
Code:———————————————————————————————————————————- Save values: ———————————————————————————————————————————- nvram get dhcp_staticlist > /tmp/mnt/ASUS/dhcplist.txt nvram get custom_clientlist > /tmp/mnt/ASUS/custom_clientlist.txt cp -r /jffs/usericon /tmp/mnt/ASUS/ ———————————————————————————————————————————- Restore values: ———————————————————————————————————————————- cd /mnt/ASUS nvram set dhcp_staticlist="`cat /tmp/mnt/ASUS/dhcplist.txt`" nvram set custom_clientlist="`cat /tmp/mnt/ASUS/custom_clientlist.txt`" cp -r /tmp/mnt/ASUS/usericon /jffs/ nvram commit && reboot
Edit: I added "custom_clientlist" that maps USER DEFINE DEVICE NAME to MAC ADDRESS, whereas the "dhcp_staticlist" maps MAC ADDRESS to USER ASSIGNED IP ADDRESS.
nothing is open, that's good, no?
[edit, oh, i see what you mean, it would be better if it was stealthed. parsed your sentence wrongly]
Yeah, it comes and goes... it's been just Closed for awhile now. I don't know if it's the router or the ISP or grc.com.
OE
Now testing RC2-7... node backhaul drooped to 2.4 and log showed VLAN issues until system reboot. System reboot after clean install is advisable, imo.
Port 0 still only Closed on grc.com ShieldsUp! WAN test (?).
View attachment 27059
OE
yes,they are reset to factory default, but the problem remains. The node cannot connect to any client.Have you done factory reset?
I have not enjoyed the same level of connection stability for my 2.4 mobile client while working around the property, now and before I switched to using Smart Connect. TuneIn regularly stops streaming with a connection error when normally it does not. If feels like RC2-6 has a connection management issue.
Here's an abbreviated snip from the General Log:
Oct 18 12:06:15 kernel: D84:3C:0A:7A:A4 not mesh client, can't update it's ip
Oct 18 12:06:15 kernel: pgd = ffffffc011703000
Oct 18 12:06:15 kernel: [f6953510] *pgd=0000000011758003, *pud=0000000011758003, *pmd=00000000153c1003, *pte=0000000000000000
Oct 18 12:06:15 kernel: CPU: 0 PID: 31262 Comm: amas_lib Tainted: P O 4.1.27 #2
Oct 18 12:06:15 kernel: Hardware name: Broadcom-v8A (DT)
Oct 18 12:06:15 kernel: task: ffffffc01e86a080 ti: ffffffc013ef0000 task.ti: ffffffc013ef0000
Oct 18 12:06:15 kernel: PC is at 0xf6998a58
Oct 18 12:06:15 kernel: LR is at 0xf6996728
Oct 18 12:06:15 kernel: pc : [<00000000f6998a58>] lr : [<00000000f6996728>] pstate: 600f0010
Oct 18 12:06:15 kernel: sp : 00000000f69534f8
Oct 18 12:06:15 kernel: x12: 0000000000000000
Oct 18 12:06:15 kernel: x11: 00000000f6955ad4 x10: 0000000000000002
Oct 18 12:06:15 kernel: x9 : 00000000f6d82c92 x8 : 00000000f6a91000
Oct 18 12:06:15 kernel: x7 : 00000000f6955b20 x6 : 00000000f6a91cc0
Oct 18 12:06:15 kernel: x5 : 00000000f6a91cc0 x4 : 00000000f69535c0
Oct 18 12:06:15 kernel: x3 : 00000000000f7db0 x2 : 00000000f6955ae8
Oct 18 12:06:15 kernel: x1 : 00000000f6d82c92 x0 : 00000000fbad8004
<snip>
Oct 18 12:07:08 rc_service: amas_lib 31300:notify_rc restart_firewall
Oct 18 12:58:03 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link DOWN.
Oct 18 12:58:06 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) Link UP 1000 mbps full duplex
Oct 18 13:15:09 roamast: determine candidate node [D4:5D:64:7B:5F:61](rssi: -52dbm) for client [90:C78:90:85:59](rssi: -68dbm) to roam
Oct 18 13:15:09 roamast: Roam a client [90:C78:90:85:59], status [0]
Oct 18 13:15:10 wlceventd: wlceventd_proc_event(469): eth5: Deauth_ind 90:C78:90:85:59, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Oct 18 13:15:10 wlceventd: wlceventd_proc_event(486): eth5: Disassoc 90:C78:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 18 13:23:31 wlceventd: wlceventd_proc_event(505): eth5: Auth 90:C78:90:85:59, status: Successful (0)
Oct 18 13:23:31 wlceventd: wlceventd_proc_event(534): eth5: Assoc 90:C78:90:85:59, status: Successful (0)
Oct 18 13:26:48 wlceventd: wlceventd_proc_event(486): eth5: Disassoc 90:C78:90:85:59, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Oct 18 13:26:48 wlceventd: wlceventd_proc_event(505): eth5: Auth 90:C78:90:85:59, status: Successful (0)
Oct 18 13:26:48 wlceventd: wlceventd_proc_event(534): eth5: Assoc 90:C78:90:85:59, status: Successful (0)
Oct 18 13:26:48 kernel: 90:C78:90:85:59 not mesh client, can't update it's ip
Oct 18 13:26:48 kernel: pgd = ffffffc0117a6000
Oct 18 13:26:48 kernel: [f77cf510] *pgd=0000000009e0d003, *pud=0000000009e0d003, *pmd=000000001163b003, *pte=0000000000000000
Oct 18 13:26:48 kernel: CPU: 0 PID: 18021 Comm: amas_lib Tainted: P O 4.1.27 #2
Oct 18 13:26:48 kernel: Hardware name: Broadcom-v8A (DT)
Oct 18 13:26:48 kernel: task: ffffffc017671480 ti: ffffffc010d4c000 task.ti: ffffffc010d4c000
Oct 18 13:26:48 kernel: PC is at 0xf6f2ca58
Oct 18 13:26:48 kernel: LR is at 0xf6f2a728
Oct 18 13:26:48 kernel: pc : [<00000000f6f2ca58>] lr : [<00000000f6f2a728>] pstate: 600f0010
Oct 18 13:26:48 kernel: sp : 00000000f77cf4f8
Oct 18 13:26:48 kernel: x12: 0000000000000000
Oct 18 13:26:48 kernel: x11: 00000000f77d1ad4 x10: 0000000000000002
Oct 18 13:26:48 kernel: x9 : 00000000f7316c92 x8 : 00000000f7025000
Oct 18 13:26:48 kernel: x7 : 00000000f77d1b20 x6 : 00000000f7025cc0
Oct 18 13:26:48 kernel: x5 : 00000000f7025cc0 x4 : 00000000f77cf5c0
Oct 18 13:26:48 kernel: x3 : 00000000000f7db0 x2 : 00000000f77d1ae8
Oct 18 13:26:48 kernel: x1 : 00000000f7316c92 x0 : 00000000fbad8004
<snip>
Oct 18 13:54:01 rc_service: amas_lib 18035:notify_rc restart_firewall
I've made bold some suspicious entries... the first D84:3C:0A:7A:A4 is a SONY AVR wired to the root node... the second 90:C78:90:85:59 is my 2.4 mobile client. There is only one weak 2.4 ch9 20MHz WiFi signal overlapping my ch11 signals.
OE
placebo?I notice that RT-AC86U RC2-2,3,4 are the exact same file size 67.6 MB (70,909,972 bytes), and RC2-5,6,7 are the exact same file size 68.0 MB (71,303,188 bytes). Hmmm... am I wasting my time?
View attachment 27057
OE
placebo?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!