What's new
By:

  • 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!

ASUS RT-AC66U_B1 All AiMesh Nodes Stopped Working

garycnew

garycnew

Senior Member
ASUS RT-AC66U_B1 All AiMesh Nodes Stopped Working. Link + Data Lights on Router Ethernet Ports Still Function.

WAN (eth0), Wi-Fi (br0), and VPN (tun12) Still Working. LAN Ethernet & Wi-Fi use the same interface br0.

DHCP seems to work with Wi-Fi. DHCP Range 192.168.0.193 - 192.168.0.253. Everything Lower Than 192.168.0.193 is Statically Assigned.

Statically Assigning IP Address to Remote Ethernet Desktop Interface Not Working.

Layer-2 Seems to Work.

Layer-3 Seems to Work for WAN (eth0), Wi-Fi (br0), and VPN (tun12), but Not for LAN Ethernet.

# robocfg showports
Switch: enabled
Port 0: 1000FD enabled stp: none vlan: 2 jumbo: off mac: 00:22:8e:d1:12:00
Port 1: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:10:3e:82:c2:93
Port 2: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:91:82:33:04:0c
Port 3: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:56:27:c8:56:10
Port 4: 1000FD enabled stp: none vlan: 1 jumbo: off mac: 00:10:3e:18:3a:c2
Port 5: 1000FD enabled stp: none vlan: 2 jumbo: off mac: 00:96:93:e0:af:a4
Port 7: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00
Port 8: DOWN enabled stp: none vlan: 1 jumbo: off mac: 00:00:00:00:00:00

# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
81.75.145.20 35.148.40.1 255.255.255.255 UGH 0 0 0 eth0
10.10.0.69 * 255.255.255.255 UH 0 0 0 tun12
35.148.40.1 * 255.255.255.255 UH 0 0 0 eth0
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
35.148.40.0 * 255.255.248.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 35.148.40.1 0.0.0.0 UG 0 0 0 eth0

# arp -a
? (192.168.0.251) at 00:38:80:a9:f1:a9 [ether] on br0
? (192.168.0.31) at <incomplete> on br0
? (192.168.0.61) at <incomplete> on br0
? (192.168.0.217) at 00:d5:bd:f7:dc:9e [ether] on br0
? (192.168.0.121) at <incomplete> on br0
? (192.168.0.141) at <incomplete> on br0
? (35.148.40.1) at 00:22:8e:d1:12:00 [ether] on eth0
? (192.168.0.225) at 00:e2:2f:c3:56:6c [ether] on br0
? (192.168.0.91) at <incomplete> on br0
? (192.168.0.21) at <incomplete> on br0
? (192.168.0.41) at <incomplete> on br0
? (192.168.0.11) at <incomplete> on br0
? (192.168.0.51) at <incomplete> on br0
? (192.168.0.244) at 00:b5:7c:46:8e:57 [ether] on br0
? (192.168.0.81) at <incomplete> on br0
? (192.168.0.71) at <incomplete> on br0
? (192.168.0.223) at 00:96:93:e0:af:a4 [ether] on br0

Of the Successful ARP Responses Only SOME IP Addresses Can Be Pinged & Traced From The Router:

? (192.168.0.251) at 00:38:80:a9:f1:a9 [ether] on br0 (Phone: SUCCESS)
? (192.168.0.217) at 00:d5:bd:f7:dc:9e [ether] on br0 (Desktop: FAILED)
? (35.148.40.1) at 00:22:8e:d1:12:00 [ether] on eth0 (WAN: SUCCESS)
? (192.168.0.225) at 00:e2:2f:c3:56:6c [ether] on br0 (RokuExpress4K: SUCCESS)
? (192.168.0.197) at 00:42:01:6c:62:cc [ether] on br0 (Unknown: SUCCESS)
? (192.168.0.244) at 00:b5:7c:46:8e:57 [ether] on br0 (RokuUltra: SUCCESS)
? (192.168.0.223) at 00:96:93:e0:af:a4 [ether] on br0 (Unknown: FAILED)

[Note: The SUCCESSES are all above the DHCP 192.168.0.193 address minimum and have WLCEVENTD wlceventd_proc_event(529): eth2: Assoc 00:42:01:6C:62:CC, status: Successful (0) entries within the syslog that suggest they are Wi-Fi related devices.]

Desktop on Wi-Fi CAN Ping & Trace Router:

C:\Users\xxx>ping 192.168.0.1

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms

C:\Users\xxx>tracert 192.168.0.1

Tracing route to router [192.168.0.1]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms router [192.168.0.1]

Trace complete.

Any Ideas as to what I may be missing?

Your Assistance is Greatly Appreciated.
 
Last edited:
UPDATE: It appears that all the LAN Ethernet Ports on the Primary Router Work Fine directly connected to an Apple or Windows Computer. It seems the issue is with the AiMesh Nodes originally connected to those same LAN ETH Ports. It must have something to do with the AiMesh implementation.

No Clients listed in the Client List and No AiMesh Nodes listed in the AiMesh Nodes List.

Any thoughts?

Thanks, again.
 
Last edited:
UPDATE: I believe I have found another clue...

Syslog-NG won't start:

Code: 
# /opt/etc/init.d/S01syslog-ng check
 Checking syslog-ng...              dead. 
# /opt/etc/init.d/S01syslog-ng start
 Starting syslog-ng...              failed.

The syslog points to the attached external drive (/tmp/mnt/HitachiHDD):

Code: 
# ls -l /tmp/ | grep -i syslog
lrwxrwxrwx    1 admin    root            21 Jan  6 10:03 syslog.log -> /opt/var/log/messages

# ls -l / | grep -i opt
lrwxrwxrwx    1 admin    root             7 Aug 14  2020 opt -> tmp/opt

# ls -l /tmp/ | grep -i opt
lrwxrwxrwx    1 admin    root            27 Jan  6 10:03 opt -> /tmp/mnt/HitachiHDD/entware
lrwxrwxrwx    1 admin    root            21 Jan  6 10:03 syslog.log -> /opt/var/log/messages

# ls -l /opt/ | grep -i var
drwxr-xr-x    7 admin    root          4096 Jan  2 04:30 var

# ls -l /opt/var/ | grep -i log
drwxr-xr-x    3 admin    root          4096 Jan  2 04:30 log
srwxrwxrwx    1 admin    root             0 Oct 24 16:19 syslog-ng.ctl
-rw-------    1 admin    root         16384 Nov 28 00:00 syslog-ng.persist
-rw-rw-rw-    1 admin    root             5 Oct 24 16:19 syslog-ng.pid

The messages file hasn't been written to since Jan 6:

Code: 
# ls -l /opt/var/log/
-rw-------    1 admin    root         99470 Nov 28 00:00 logrotate.log
-rw-------    1 admin    root        262155 Apr 13  2024 logrotate.log-20240414
-rw-------    1 admin    root        371922 Jan  6 10:03 messages

The attached external drive seems to have adequate Free Space:

Code: 
# df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/root                29.1M     29.1M         0 100% /
devtmpfs                124.7M         0    124.7M   0% /dev
tmpfs                   124.8M      1.9M    122.9M   2% /tmp
/dev/mtdblock4           62.8M     11.3M     51.4M  18% /jffs
/dev/sda1                28.8G     21.0G      6.4G  77% /tmp/mnt/HitachiHDD

There seem to be adequate Free Inodes:

Code: 
# tune2fs -l /dev/sda1
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name:   HitachiHDD
Last mounted on:          /tmp/mnt/HitachiHDD
Filesystem UUID:          b47903cb-b92a-49fa-9062-f0a327fd30bf
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file uninit_bg dir_nlink extra_isize
Filesystem flags:         unsigned_directory_hash 
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1917600
Block count:              7669021
Reserved block count:     383451
Free blocks:              2055985
Free inodes:              10787
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1022
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8160
Inode blocks per group:   510
Flex block group size:    16
Filesystem created:       Sun May 15 01:19:11 2022
Last mount time:          Mon Jan  6 10:03:10 2025
Last write time:          Mon Jan  6 10:03:10 2025
Mount count:              50
Maximum mount count:      -1
Last checked:             Tue Apr  9 02:19:18 2024
Check interval:           0 (<none>)
Lifetime writes:          2341 MB
Reserved blocks uid:      0 (user admin)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      6618767b-9c8b-4654-81de-918bfe1e8026
Journal backup:           inode blocks

I am able to create a sample file in the log directory:

Code: 
# touch /opt/var/log/test

# ls -l /opt/var/log/test
-rw-rw-rw-    1 admin    root             0 Jan  8 03:08 /opt/var/log/test

I'm assuming the next step is to start Syslog-NG with the debug option?

Thanks, again.


Gary
 
Maybe some possible filesystem issues?
Run AMTM, dc - disk check. Enable it and reboot
Then run AMTM and do dcl. (Disk Check Log) to see if it fixed anything.
 
Last edited:
I agree with @JGrana's view.
Since the drive has been in use since 2022, going through however many firmware upgrades, it may even be time to reset, format and start again (or even upgrade the drive).
 
@JGrana and @Ripshod

The router is in a production environment and has seen only a few firmware upgrades.

It appears that klogd works during router startup, but exits shortly thereafter along with all logging:

Code: 
May  4 23:05:05 kernel: klogd started
Jan  8 16:53:05 kernel: klogd: exiting

I was able to preform a clean Check Disk without issue:

Code: 
Jan  8 16:52:42 amtm disk-check: Probing 'ext4' on device /dev/sda1
Jan  8 16:52:42 amtm disk-check: Running disk check v2.9, with command 'e2fsck -p' on /dev/sda1
Jan  8 16:52:53 amtm disk-check: Disk check done on /dev/sda1
Jan  8 16:52:55 usb: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/HitachiHDD.

tune2fs shows the Filesystem state as clean:

Code: 
# tune2fs -l /dev/sda1
tune2fs 1.42.13 (17-May-2015)
Filesystem volume name:   HitachiHDD
Last mounted on:          /tmp/mnt/HitachiHDD
Filesystem UUID:          b47903cb-b92a-49fa-9062-f0a327fd30bf
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file uninit_bg dir_nlink extra_isize
Filesystem flags:         unsigned_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              1917600
Block count:              7669021
Reserved block count:     383451
Free blocks:              2055937
Free inodes:              10787
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1022
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8160
Inode blocks per group:   510
Flex block group size:    16
Filesystem created:       Sun May 15 01:19:11 2022
Last mount time:          Wed Jan  8 16:52:55 2025
Last write time:          Wed Jan  8 16:52:55 2025
Mount count:              51
Maximum mount count:      -1
Last checked:             Tue Apr  9 02:19:18 2024
Check interval:           0 (<none>)
Lifetime writes:          2342 MB
Reserved blocks uid:      0 (user admin)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      6618767b-9c8b-4654-81de-918bfe1e8026
Journal backup:           inode blocks

When attempting to start Syslog-NG, in verbose mode, I found that the /opt/sbin/syslog-ng file was missing:

Code: 
# opkg files syslog-ng | grep -i bin
/opt/sbin/syslog-ng-debun
/opt/bin/pdbtool
/opt/bin/slogverify
/opt/bin/persist-tool
/opt/bin/update-patterndb
/opt/sbin/logread
/opt/bin/slogkey
/opt/sbin/syslog-ng-ctl
/opt/bin/loggen
/opt/bin/dqtool
/opt/sbin/syslog-ng
/opt/bin/slogencrypt

# ls -l /opt/sbin/syslog-ng
ls: /opt/sbin/syslog-ng: No such file or directory

After reinstalling Syslog-NG, the daemon started up without issue. I'll watch the logs and see whether I can find any more clues as to what's going on.

I appreciate you assistance.

Respectfully,


Gary
 
Last edited:
UPDATE: Now that the issues with Syslog-NG have been resolved, the syslog is full of these start_cfgsync messages every 30 seconds:

Code: 
Jan  9 16:23:11 router rc_service: watchdog 259:notify_rc start_cfgsync
Jan  9 16:23:11 router custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Jan  9 16:23:11 router custom_script: Running /jffs/scripts/service-event-end (args: start cfgsync)
Jan  9 16:23:41 router rc_service: watchdog 259:notify_rc start_cfgsync
Jan  9 16:23:41 router custom_script: Running /jffs/scripts/service-event (args: start cfgsync)
Jan  9 16:23:41 router custom_script: Running /jffs/scripts/service-event-end (args: start cfgsync)

Contents of the service-event script:

Code: 
# cat /jffs/scripts/service-event
#!/bin/sh

# Check Whether FreeVPN.me Password Changed
if echo "$1" | grep -i "start" && [ "$2" = "vpnclient1" ]; then
   /bin/sh /root/pushbot/freevpn.me/crawler >/dev/null 2>&1
fi

/jffs/scripts/scribe kill-logger nologo "$1" "$2" & # added by scribe
if echo "$2" | /bin/grep -q "uiScribe"; then { /jffs/scripts/uiScribe service_event "$@" & }; fi # uiScribe

Contents of the service-event-end script:

Code: 
# cat /jffs/scripts/service-event-end
#!/bin/sh

# Check Whether zomg_cfg_sync Executed and If True Then Execute zomg_cfg_server Script
#if echo "$2" | /bin/grep -q "^cfgsync"; then { /bin/sh /jffs/sbin/zomg_cfg_server & }; fi

I believe the reason for the numerous start_cfgsync attempts is due to the router not being able to reach the AiMesh Nodes?

Thanks, again, for your assistance.

Respectfully,


Gary
 
UPDATE: Primary Router Startup Syslog with CfgSync entries filtered out.

Code: 
# grep -v cfgsync /tmp/syslog.log
May  4 23:05:05 kernel: klogd started: BusyBox v1.25.1 (2020-08-14 15:17:43 EDT)
May  4 23:05:05 kernel: Linux version 2.6.36.4brcmarm (merlin@ubuntu-dev) (gcc version 4.5.3 (Buildroot 2012.02) ) #1 SMP PREEMPT Fri Aug 14 15:20:58 EDT 2020
May  4 23:05:05 kernel: CPU: ARMv7 Processor [413fc090] revision 0 (ARMv7), cr=10c53c7f
May  4 23:05:05 kernel: CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
May  4 23:05:05 kernel: Machine: Northstar Prototype
May  4 23:05:05 kernel: Ignoring unrecognised tag 0x00000000
May  4 23:05:05 kernel: Memory policy: ECC disabled, Data cache writealloc
May  4 23:05:05 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 60416
May  4 23:05:05 kernel: Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit earlyprintk debug
May  4 23:05:05 kernel: Memory: 255464k/255464k available, 6680k reserved, 0K highmem
May  4 23:05:05 kernel: * Invalid signature of oopsbuf: FF-E7-D7-FF-FF-FF-EF-FF (len 4160749307)
May  4 23:05:05 kernel: External imprecise Data abort at addr=0x0, fsr=0x1c06 ignored.
May  4 23:05:05 kernel: Mount-cache hash table entries: 512
May  4 23:05:05 kernel: CPU1: Booted secondary processor
May  4 23:05:05 kernel: Found a AMD NAND flash:
May  4 23:05:05 kernel: Total size:  128MB
May  4 23:05:05 kernel: Block size:  128KB
May  4 23:05:05 kernel: Page Size:   2048B
May  4 23:05:05 kernel: OOB Size:    64B
May  4 23:05:05 kernel: Sector size: 512B
May  4 23:05:05 kernel: Spare size:  16B
May  4 23:05:05 kernel: ECC level:   8 (8-bit)
May  4 23:05:05 kernel: Device ID: 0x 1 0xf1 0x 0 0x1d 0x 1 0xf1
May  4 23:05:05 kernel: bio: create slab <bio-0> at 0
May  4 23:05:05 kernel: VFS: Disk quotas dquot_6.5.2
May  4 23:05:05 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
May  4 23:05:05 kernel: pflash: found no supported devices
May  4 23:05:05 kernel: bcmsflash: found no supported devices
May  4 23:05:05 kernel: Boot partition size = 524288(0x80000)
May  4 23:05:05 kernel: lookup_nflash_rootfs_offset: offset = 0x200000
May  4 23:05:05 kernel: nflash: squash filesystem with lzma found at block 28
May  4 23:05:05 kernel: Creating 4 MTD partitions on "nflash":
May  4 23:05:05 kernel: 0x000000000000-0x000000080000 : "boot"
May  4 23:05:05 kernel: 0x000000080000-0x000000200000 : "nvram"
May  4 23:05:05 kernel: 0x000000200000-0x000004000000 : "linux"
May  4 23:05:05 kernel: 0x00000039fb48-0x000004000000 : "rootfs"
May  4 23:05:07 nat: apply redirect rules
May  4 23:05:12 acsd: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs 
May  4 23:05:12 acsd: selected channel spec: 0x100b (11)
May  4 23:05:12 acsd: Adjusted channel spec: 0x100b (11)
May  4 23:05:12 acsd: selected DFS-exit channel spec: 0x100b (11)
May  4 23:05:12 acsd: COEX: downgraded chanspec 0x1909 to 0x100b: channel 6 used by exiting BSSs 
May  4 23:05:12 acsd: selected channel spec: 0x100b (11)
May  4 23:05:12 acsd: Adjusted channel spec: 0x100b (11)
May  4 23:05:12 acsd: selected channel spec: 0x100b (11)
May  4 23:05:12 acsd: acs_set_chspec: 0x100b (11) for reason APCS_INIT
May  4 23:05:12 custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.
May  4 23:05:12 WAN_Connection: ISP's DHCP did not function properly.
May  4 23:05:13 RT-AC66U_B1: start https:8443
May  4 23:05:13 RT-AC66U_B1: start httpd:80
May  4 23:05:13 avahi-daemon[268]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
May  4 23:05:14 disk_monitor: be idle
May  4 23:05:14 avahi-daemon[268]: Alias name "RT-AC66U_B1" successfully established.
May  4 23:05:15 hour_monitor: daemon is starting
May  4 23:05:16 custom_script: Running /jffs/scripts/torrc.postconf (args: /tmp/torrc)
May  4 23:05:16 httpd: Succeed to init SSL certificate...80
May  4 23:05:16 httpd: Succeed to init SSL certificate...8443
May  4 23:05:18 jffs2: valid logs(1)
May  4 23:05:20 lldpd[501]: cannot get ethtool link information with GLINKSETTINGS (requires 4.9+): Operation not permitted
May  4 23:05:20 lldpd[501]: cannot get ethtool link information with GSET (requires 2.6.19+): Operation not permitted
May  4 23:05:22 custom_script: Running /jffs/scripts/services-start
May  4 23:05:22 syslog: module ax88179_178a not found in modules.dep
May  4 23:05:23 custom_script: Running /jffs/scripts/wan-event (args: 0 init)
May  4 23:05:23 custom_script: Running /jffs/scripts/wan-event (args: 0 connecting)
May  4 23:05:23 admin: wan-event: WAN0 is init
May  4 23:05:23 admin: wan-event: WAN0 is connecting
May  4 23:05:23 custom_script: Running /jffs/scripts/wan-event (args: 0 disconnected)
May  4 23:05:23 custom_script: Running /jffs/scripts/wan-event (args: 0 stopped)
May  4 23:05:23 admin: wan-event: WAN0 is stopped
May  4 23:05:23 admin: wan-event: WAN0 is disconnected
May  4 23:05:23 Mastiff: init
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: Failed to enable MSI-X
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: failed to allocate MSI entry
May  4 23:05:23 kernel: usb usb1: No SuperSpeed endpoint companion for config 1  interface 0 altsetting 0 ep 129: using minimum values
May  4 23:05:23 kernel: SCSI subsystem initialized
May  4 23:05:23 kernel: csw_retry 100
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: WARN: short transfer on control ep
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 1
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: disable burst on ep 2
May  4 23:05:23 kernel: xhci_hcd 0000:00:0c.0: WARN no SS endpoint bMaxBurst
May  4 23:05:24 custom_script: Running /jffs/scripts/wan-event (args: 0 connected)
May  4 23:05:24 admin: wan-event: WAN0 is connected
May  4 23:05:24 admin: wan-event: WAN0 is connected
May  4 23:05:24 nat: apply nat rules (/tmp/nat_rules_eth0_eth0)
May  4 23:05:24 custom_script: Running /jffs/scripts/nat-start
May  4 23:05:24 kernel: scsi 0:0:0:0: Direct-Access     JMicron  Generic          0209 PQ: 0 ANSI: 6
May  4 23:05:24 kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
May  4 23:05:24 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
May  4 23:05:25 kernel: sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
May  4 23:05:25 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
May  4 23:05:25 kernel: sd 0:0:0:0: [sda] Write Protect is off
May  4 23:05:25 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
May  4 23:05:25 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
May  4 23:05:25 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
May  4 23:05:25 kernel: xhci_hcd 0000:00:0c.0: WARN: Stalled endpoint
May  4 23:05:25 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
May  4 23:05:25 kernel: sd 0:0:0:0: [sda] Attached SCSI disk
May  4 23:05:27 kernel: nf_conntrack_rtsp v0.6.21 loading
May  4 23:05:27 kernel: nf_nat_rtsp v0.6.21 loading
May  4 23:05:27 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
May  4 23:05:28 custom_script: Running /jffs/scripts/pre-mount (args: /dev/sda1 ext4)
May  4 23:05:28 wan: finish adding multi routes
May  4 23:05:30 rc_service: udhcpc 673:notify_rc stop_ntpd
May  4 23:05:30 rc_service: udhcpc 673:notify_rc start_ntpd
May  4 23:05:30 rc_service: waitting "stop_ntpd" via udhcpc ...
May  4 23:05:30 custom_script: Running /jffs/scripts/service-event (args: stop ntpd)
May  4 23:05:31 custom_script: Running /jffs/scripts/service-event-end (args: stop ntpd)
May  4 23:05:32 custom_script: Running /jffs/scripts/service-event (args: start ntpd)
May  4 23:05:33 ntpd: Started ntpd
May  4 23:05:33 custom_script: Running /jffs/scripts/service-event-end (args: start ntpd)
May  4 23:05:33 WAN_Connection: WAN was restored.
May  4 23:05:33 miniupnpd[1230]: HTTP listening on port 57606
May  4 23:05:33 miniupnpd[1230]: Listening for NAT-PMP/PCP traffic on port 5351
May  4 23:05:35 admin: Running /jffs/scripts/lighttpd.postconf
Jan 10 14:35:35 ntpd: Initial clock set
Jan 10 14:35:35 rc_service: ntpd_synced 1313:notify_rc restart_diskmon
Jan 10 14:35:35 custom_script: Running /jffs/scripts/service-event (args: restart diskmon)
Jan 10 14:35:37 start_ddns: Error ddns server name: 
Jan 10 14:35:37 disk_monitor: Finish
Jan 10 14:35:38 amtm disk-check: Waited 7s for NTP to sync date
Jan 10 14:35:38 custom_script: Running /jffs/scripts/service-event-end (args: restart diskmon)
Jan 10 14:35:40 disk_monitor: be idle
Jan 10 14:35:40 amtm disk-check: Probing 'ext4' on device /dev/sda1
Jan 10 14:35:40 amtm disk-check: Running disk check v2.9, with command 'e2fsck -p' on /dev/sda1
Jan 10 14:35:59 amtm disk-check: Disk check done on /dev/sda1
Jan 10 14:35:59 usb: USB ext4 fs at /dev/sda1 mounted on /tmp/mnt/HitachiHDD.
Jan 10 14:36:01 custom_script: Running /jffs/scripts/post-mount (args: /tmp/mnt/HitachiHDD)
Jan 10 14:36:02 Entware: Starting Entware services on /tmp/mnt/HitachiHDD
Jan 10 14:36:02 admin: Started syslog-ng from /jffs/scripts/post-mount.
Jan 10 14:36:02 kernel: SHN Release Version: 2.0.1 890c91d
Jan 10 14:36:02 kernel: UDB Core Version: 0.2.18
Jan 10 14:36:02 kernel: sizeof forward pkt param = 192
Jan 10 21:36:02 rpcbind[1953]: cannot get uid of 'root': Success
Jan 10 14:36:02 BWDPI: fun bitmap = 3
Jan 10 14:37:26 miniupnpd[1230]: shutting down MiniUPnPd
Jan 10 14:37:27 kernel: svc: failed to register lockdv1 RPC service (errno 97).
Jan 10 14:39:39 kernel: gro disabled
Jan 10 14:39:40 kernel: nfsd: last server has exited, flushing export cache
 
UPDATE: I believe I may have stumbled upon the cause of the issue. The related issues all began, when I attempted to add a DHCP Client Reservation to the Primary Router's LAN > DHCP Server. I already had several DHCP Client Reservations configured and after adding the last one is when all the AiMessh Nodes stopped working (which have DHCP Client Reservations). I immediately removed the last DHCP Client Reservation, but it did not resolve the issue. All the working Wired & Wireless Clients do not have DHCP Client Reservations.

In researching this issue, I found a post stating that the nvram configuration variables are limited to 255 characters one of which is dhcp_staticlist. I've also found a couple of oversized nvram variables nc_setting_conf and cfg_relist.

I've slimmed down the nvram variable dhcp_staticlist by removing DHCP Client Reservations, but I'm not sure how to slim down the nc_setting_conf and cfg_relist variables, through the Web GUI.

Suggestions?

Thanks, again.


Gary
 
YazDHCP?
 
dave14305 said:
384.19
Click to expand...

Yep...

www.snbforums.com

[ANNOUNCEMENT] Asuswrt-Merlin 386_x devices are no longer supported

I think it is more of a pragmatic view - these devices are multiple generations back, and with Wifi6/7 now current, having one of these legacy devices in an AIMesh may impact overall performance... @Tech9 - nothing would stop them from being Media Gateways, or as dedicated AP's... But as...
www.snbforums.com www.snbforums.com

Garry has a lot of updates ahead, nothing to worry about end of support. :)
 
Tech9 said:
Yep...

www.snbforums.com

[ANNOUNCEMENT] Asuswrt-Merlin 386_x devices are no longer supported

I think it is more of a pragmatic view - these devices are multiple generations back, and with Wifi6/7 now current, having one of these legacy devices in an AIMesh may impact overall performance... @Tech9 - nothing would stop them from being Media Gateways, or as dedicated AP's... But as...
www.snbforums.com www.snbforums.com

Garry has a lot of updates ahead, nothing to worry about end of support. :)
Click to expand...
If it isn't broke... Oh, Wait! It is broke! :p
 
garycnew said:
In researching this issue, I found a post stating that the nvram configuration variables are limited to 255 characters one of which is dhcp_staticlist. I've also found a couple of oversized nvram variables nc_setting_conf and cfg_relist.
Click to expand...
The 255 character limit was extended in later firmware (even for your ancient version), so it shouldn't be a problem.

For 384.19:
dhcp_staticlist = 2500
nc_setting_conf (NC was never implemented so should be academic) = 1024
cfg_relist = 4096
 
ColinTaylor said:
The 255 character limit was extended in later firmware (even for your ancient version), so it shouldn't be a problem.

For 384.19:
dhcp_staticlist = 2500
nc_setting_conf (NC was never implemented so should be academic) = 1024
cfg_relist = 4096
Click to expand...
@ColinTaylor

The following was the original values of the cfg_relist, which had null and duplicate values:

Code: 
cfg_relist=
<X4:10:3E:82:C2:93>X4:10:3E:82:C2:94,X6:08:1F:41:C2:93>X4:10:3E:82:C2:97,X6:08:1F:41:C2:93>1735815219
<X4:10:3E:9D:AE:61>X4:10:3E:9D:AE:62,X6:88:1F:4E:AE:61>X4:10:3E:9D:AE:65,X6:88:1F:4E:AE:61>1735815189
<X0:56:27:7A:3C:73>X0:56:27:7A:3C:74,X2:2B:13:BD:3C:73>X0:56:27:7A:3C:77,X2:2B:13:BD:3C:73>1735815187
<X0:56:27:D2:D4:48>X0:56:27:D2:D4:49,X2:2B:13:E9:D4:48>X0:56:27:D2:D4:4C,X2:2B:13:E9:D4:48>1735815216
<>>>1626483259
<X0:56:27:C8:56:10>X0:56:27:C8:56:11,X2:2B:13:E4:56:10>X0:56:27:C8:56:14,X2:2B:13:E4:56:10>1735815221
<X0:56:27:D5:D7:A6>X0:56:27:D5:D7:A7,X2:AB:13:EA:D7:A6>X0:56:27:D5:D7:AA,X2:AB:13:EA:D7:A6>1735815202
<X4:91:82:32:61:EC>X4:91:82:32:61:ED,X6:48:C1:19:61:EC>X4:91:82:32:61:F0,X6:48:C1:19:61:EC>1735815229
<X0:56:27:66:5D:A5>X0:56:27:66:5D:A6,X2:2B:13:B3:5D:A5>X0:56:27:66:5D:A9,X2:2B:13:B3:5D:A5>1735815218
<X4:91:82:33:04:0C>X4:91:82:33:04:0D,X6:C8:C1:19:04:0C>X4:91:82:33:04:10,X6:C8:C1:19:04:0C>1735815221
<X4:10:3E:18:3A:C2>X4:10:3E:18:3A:C3,X6:08:1F:0C:3A:C2>X4:10:3E:18:3A:C6,X6:08:1F:0C:3A:C2>1735815217
<X4:10:3E:03:39:51>X4:10:3E:03:39:52>X4:10:3E:03:39:55>1734425031
<X4:10:3E:03:39:51>X4:10:3E:03:39:52>X4:10:3E:03:39:55>1734425031

After manually updating the cfg_relist values, pairing it down to 9 devices, and rebooting the router... It still does not resolve the issue.

I guess that rules out that theory.

I appreciate the info.

Respectfully,


Gary
 
Last edited:
You must log in or register to reply here.

Similar threads

garycnew
No Clients listed in the Network Map > Client List
Replies
3
Views
213
garycnew
garycnew
R
Help with RT-ac88u network switch issues - causing reboot
Replies
0
Views
349
rkalinka
R
SeeJayEmm
AC68 intermittently VLAN tagging
Replies
8
Views
2K
drinkingbird
drinkingbird
D
[ASUS AX86U Merlin] Blink Sync Module does not connect (connects to iphone hotspot)
Replies
0
Views
1K
dasusm
D
Nas.CloudBusinessPortal
Strange happenings
Replies
1
Views
349
ColinTaylor
C
Similar threads
Thread starter Title Forum Replies Date
zeeblefritz Asus RT-AC66U Merlin Stuck applying settings when manually assigning IP Asuswrt-Merlin 19
M Help needed with Asus RT-AC66U router Asuswrt-Merlin 26
A Asus 86U with 386.14_2 NO export certificate. Any workaround ? Asuswrt-Merlin 2
copperhead Issue with Inter-VLAN Communication on ASUS RT-AX88U Pro Asuswrt-Merlin 3
W ASUS RT-AX88U Pro Asus Merlin Asuswrt-Merlin 2
Harry Azcrac ASUS Merlin on RT-AC86U OpenVPN Server not blocking IP when a client connects Asuswrt-Merlin 2
B Tutorial Automatically Reboot Asus Router on Network Failures Asuswrt-Merlin 15
C Remote home access, using Wireguard Asus AX86U and GLiNet Beryl AX Asuswrt-Merlin 11
ojigi Asus RT-AX68U "hangs" about once per day Asuswrt-Merlin 1
J Curious behaviour after opening ports with iptables - RTAX86U - Asus Wrt Merlin Asuswrt-Merlin 6

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: 464 (members: 18, guests: 446)
Back
Top