What's new

AX88U Crashed only reboot would fix

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

samuraijmb

Occasional Visitor
Hi,
This has happened a few times but not for a few weeks.

My AX88U is running 388.1 with 5 AiMesh Nodes. It suddenly went down and I could see Wifi was broadcasting but would not connect. When i looked at the router the WAN light was red and only a reboot would solve it.

This is the log before the reboot. Please could someone have a look and give me an idea of what it could be.

Jan 10 21:00:29 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1
Jan 10 21:00:31 kernel: DROP IN=ppp0 OUT= MAC= SRC=54.66.148.87 DST={redacted} LEN=32 TOS=0x00 PREC=0x00 TTL=46 ID=59666 DF PROTO=UDP SPT=32099 DPT=10308 LEN=12 MARK=0x8000000
Jan 10 21:00:34 kernel: DROP IN=ppp0 OUT= MAC= SRC=212.70.149.2 DST={redacted} LEN=40 TOS=0x00 PREC=0x00 TTL=247 ID=39059 PROTO=TCP SPT=47836 DPT=3659 SEQ=519188021 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Jan 10 21:00:42 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=1025
Jan 10 21:00:45 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=2049
Jan 10 21:00:49 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=3073
Jan 10 21:00:54 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=4097
Jan 10 21:00:58 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=5121
Jan 10 21:01:02 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=6145
Jan 10 21:01:23 bsd: bsd: Sending act Frame with transition target eth7 ssid 3c:7c:3f:54:2a:e4
Jan 10 21:01:29 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=7169
Jan 10 21:01:49 bsd: bsd: Sending act Frame with transition target eth7 ssid 3c:7c:3f:54:2a:e4
Jan 10 21:01:51 ovpn-server1[1873]: PLUGIN AUTH-PAM: Error signaling background process to exit: Connection refused (errno=111)
Jan 10 21:01:53 pppd[17990]: Interface eth0 has MTU of 1492 -- should be 1500. You may have serious connection problems.
Jan 10 21:01:57 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link DOWN.
Jan 10 21:02:00 kernel: eth4 (Ext switch port: 3) (Logical Port: 11) (phyId: b) Link UP at 1000 mbps full duplex
Jan 10 21:02:03 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=8193
Jan 10 21:02:28 pppd[17990]: Timeout waiting for PADO packets
Jan 10 21:02:52 pppd[17990]: Unable to complete PPPoE Discovery
Jan 10 21:02:54 pppd[18933]: Interface eth0 has MTU of 1492 -- should be 1500. You may have serious connection problems.
Jan 10 21:02:55 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=9217
Jan 10 21:03:29 pppd[18933]: Timeout waiting for PADO packets
Jan 10 21:03:53 pppd[18933]: Unable to complete PPPoE Discovery
Jan 10 21:03:55 pppd[19936]: Interface eth0 has MTU of 1492 -- should be 1500. You may have serious connection problems.
Jan 10 21:04:01 bsd: bsd: Sending act Frame with transition target eth7 ssid 3c:7c:3f:54:2a:e4
Jan 10 21:04:01 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=10241
Jan 10 21:04:22 bsd: bsd: Sending act Frame with transition target eth7 ssid 3c:7c:3f:54:2a:e4
Jan 10 21:04:30 pppd[19936]: Timeout waiting for PADO packets
Jan 10 21:04:54 pppd[19936]: Unable to complete PPPoE Discovery
Jan 10 21:04:56 pppd[20853]: Interface eth0 has MTU of 1492 -- should be 1500. You may have serious connection problems.
Jan 10 21:05:07 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=11265
Jan 10 21:05:31 pppd[20853]: Timeout waiting for PADO packets
Jan 10 21:05:55 pppd[20853]: Unable to complete PPPoE Discovery
Jan 10 21:05:57 pppd[21600]: Interface eth0 has MTU of 1492 -- should be 1500. You may have serious connection problems.
Jan 10 21:06:15 kernel: ERR: rdpa_cpu_tx_port_enet_lan#213: rdpa_cpu_tx_port_enet_lan failed. rdd_rc=120 tx_rdd_error_count=12289
Jan 10 21:06:32 pppd[21600]: Timeout waiting for PADO packets


Many thanks
 
Had similar issue with my Aimesh main (AX88U). Problem was ISP. While the modem was connected and passed signal, the ISP had an interference problem that degraded the signal. The AX88U is rather sensitive to the quality of the WAN input from modem. I was not getting a signal within spec so not all antennas in modem bonded. (I think I was only getting 4 of 8). Spectrum tested the MoCA input and said it was way out of spec so they had to attenuate and clear node. Once the modem got the full signal without noise, the AX88U red light on the Internet turned green (after booting).
 
Hello @samuraijmb ,

Did you ever resolve this issue? I'm going through the same issues right now.

@The Lorax
As per the ISP issue, I'm assuming you had to put your ISP modem back in order for them to test that or was it someone coming that came to test the fibre itself?
 
Hello @samuraijmb ,

Did you ever resolve this issue? I'm going through the same issues right now.

@The Lorax
As per the ISP issue, I'm assuming you had to put your ISP modem back in order for them to test that or was it someone coming that came to test the fibre itself?
No, unfortunately this still happens me from time to time. I have a Fibre ONT which is connected to my AX88U and normally it works great but every now and again we will lose connection in the house and the WAN light on the AX88U is red and only a reboot solves it. I could well believe it is an issue with ISP but I am sure my ISP would not know how to sort.
 

Similar threads

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