Menu
What's new
By:
Filters Better Search

RT-AC88U Problem in wan

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

C

Cleyton

New Around Here
Hello Everyone !

I’m problem in router RT-AC88U, wan port disconnected constant, The problem is not in the provider, because I've already done tests on the outside and the behavior did not happen the same.

Model: RT-AC88U
 

Attachments

  • IMG_0222.jpeg
    IMG_0222.jpeg
    142.3 KB · Views: 49
ColinTaylor said:
Replace the ethernet cable between the modem and your router.
Click to expand...
I changed the cable for a cat 6, but I still get the same message, it seems to me to be some problem with FW or the wan port of the router itself, interesting that before this error did not occur.
 
What is Dual WAN used for in your setup?
 
Does this WAN connection go down in single WAN configuration? Dual WAN is quite buggy in Asuswrt.
 
Tech9 said:
Does this WAN connection go down in single WAN configuration? Dual WAN is quite buggy in Asuswrt.
Click to expand...
I haven't tried using it yet, but using the second link on lan 4 this error did not occur, the worst part is that the connection keeps dropping.
Below is an excerpt from the error log that occurs

Code: 
Oct 29 21:33:49 kernel: dcd/18438: potentially unexpected fatal signal 6.
Oct 29 21:33:49 kernel: Pid: 18438, comm:                  dcd
Oct 29 21:33:49 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Oct 29 21:33:49 kernel: PC is at 0x2abe4890
Oct 29 21:33:49 kernel: LR is at 0x2abbcee4
Oct 29 21:33:49 kernel: pc : [<2abe4890>]    lr : [<2abbcee4>]    psr: 60000010
Oct 29 21:33:49 kernel: sp : 7eee3cf0  ip : 2abc6de8  fp : 7eee3d94
Oct 29 21:33:49 kernel: r10: 7eee3d98  r9 : 0000dafc  r8 : 0000a620
Oct 29 21:33:49 kernel: r7 : 000000a2  r6 : 00000008  r5 : 7eee3d38  r4 : 7eee3d38
Oct 29 21:33:49 kernel: r3 : 00000000  r2 : 00000258  r1 : 7eee3d38  r0 : fffffdfc
Oct 29 21:33:49 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Oct 29 21:33:49 kernel: Control: 10c53c7d  Table: 5251c04a  DAC: 00000015
Oct 29 21:33:49 kernel: Pid: 18443, comm:                  dcd
Oct 29 21:33:49 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Oct 29 21:33:49 kernel: PC is at 0x2abe4890
Oct 29 21:33:49 kernel: LR is at 0x2abbcee4
Oct 29 21:33:49 kernel: pc : [<2abe4890>]    lr : [<2abbcee4>]    psr: 60000010
Oct 29 21:33:49 kernel: sp : 7e3ffdf8  ip : 2abc6de8  fp : 7e3ffe6c
Oct 29 21:33:49 kernel: r10: 2abcb020  r9 : 2abcb3dc  r8 : 00000000
Oct 29 21:33:49 kernel: r7 : 000000a2  r6 : 7eee3d14  r5 : 7e3ffe40  r4 : 7e3ffe40
Oct 29 21:33:49 kernel: r3 : 00000000  r2 : 00000230  r1 : 7e3ffe40  r0 : fffffdfc
Oct 29 21:33:49 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Oct 29 21:33:49 kernel: Control: 10c53c7d  Table: 5251c04a  DAC: 00000015
Oct 29 21:34:24 WAN(0) Connection: No response from ISP.
Oct 29 21:34:24 DualWAN: skip single wan wan_led_control - WANRED off
Oct 29 21:34:25 WAN(0) Connection: WAN was restored.
 
This dcd crashing is perhaps unrelated to your issue. It's TrendMicto Data Collection Daemon crashing. Asus promises a fix, but your router is End-of-Life and no further fixes are expected for it. For your Dual WAN try different port, cable, single WAN configuration and see what works. Many issues reported in Dual WAN fail over/back with multiple solutions from separate router to custom scripts.

One of the cheapest multi-WAN routers is TP-Link ER605, around $60. It works properly with up to 4x WAN connections. Easy to setup UI.
 
Tech9 said:
This dcd crashing is perhaps unrelated to your issue. It's TrendMicto Data Collection Daemon crashing. Asus promises a fix, but your router is End-of-Life and no further fixes are expected for it. For your Dual WAN try different port, cable, single WAN configuration and see what works. Many issues reported in Dual WAN fail over/back with multiple solutions from separate router to custom scripts.

One of the cheapest multi-WAN routers is TP-Link ER605, around $60. It works properly with up to 4x WAN connections. Easy to setup UI.
Click to expand...
This error took me by surprise and knowing that it is at the end of its useful life, but I will follow what you said, look at other equipment that does this type of work, thank you very much.
 
Similar small business class routers with good multi-WAN are Ubiquiti ER-X and MikroTik hEX. Harder to setup though.
 
It will work, but ER605 is readily available in many places and has almost consumer router UI.

UI emulator here:

Opening...

emulator.tp-link.com emulator.tp-link.com

All routers mentioned above have similar hardware capabilities, all entry-level business class devices.

Make sure one of your ISPs or equipment is not causing the disconnections though. None of the above will fix that.
 
Last edited:
Hello Everyone!

I'm having a problem when I turn on the router's dual wan, it's causing the errors below, I've already disabled Trend Micro, but I wasn't successful, and the errors remain, can anyone help me?

Current Merlin version: 386.12_4

With the original FW, it is impossible to navigate, unfortunately.

Model: RT-AC88U



Code: 
Dec  1 10:53:32 kernel: aaews/30760: potentially unexpected fatal signal 11.
Dec  1 10:53:32 kernel: Pid: 30760, comm:                aaews
Dec  1 10:53:32 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Dec  1 10:53:32 kernel: PC is at 0x2b222890
Dec  1 10:53:32 kernel: LR is at 0x2abafee4
Dec  1 10:53:32 kernel: pc : [<2b222890>]    lr : [<2abafee4>]    psr: 60000010
Dec  1 10:53:32 kernel: sp : 7e3ff998  ip : 2abb9de8  fp : ffff6ec4
Dec  1 10:53:32 kernel: r10: 00000000  r9 : 80002005  r8 : 2b27a27c
Dec  1 10:53:32 kernel: r7 : 000000a2  r6 : 001e8481  r5 : 7e3ff9c0  r4 : 00000000
Dec  1 10:53:32 kernel: r3 : 00000001  r2 : 00000230  r1 : 00000000  r0 : fffffdfc
Dec  1 10:53:32 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Dec  1 10:53:32 kernel: Control: 10c53c7d  Table: 5dc7c04a  DAC: 00000015
Dec  1 10:53:32 kernel: aaews/30764: potentially unexpected fatal signal 11.
Dec  1 10:53:32 kernel: Pid: 30764, comm:                aaews
Dec  1 10:53:32 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Dec  1 10:53:32 kernel: PC is at 0x2b223498
Dec  1 10:53:32 kernel: LR is at 0x2abaf96c
Dec  1 10:53:32 kernel: pc : [<2b223498>]    lr : [<2abaf96c>]    psr: 80000010
Dec  1 10:53:32 kernel: sp : 7dbff6d0  ip : 2abb9f50  fp : 00001406
Dec  1 10:53:32 kernel: r10: 00000000  r9 : 00000230  r8 : 2b27a27c
Dec  1 10:53:32 kernel: r7 : 0000009e  r6 : 001e8481  r5 : 7dbff6e0  r4 : 00000000
Dec  1 10:53:32 kernel: r3 : 00000001  r2 : 00000000  r1 : 7dbff6e0  r0 : 00000000
Dec  1 10:53:32 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Dec  1 10:53:32 kernel: Control: 10c53c7d  Table: 5dc7c04a  DAC: 00000015
Dec  1 10:53:32 kernel: Pid: 30763, comm:                aaews
Dec  1 10:53:32 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Dec  1 10:53:32 kernel: PC is at 0x2b223498
Dec  1 10:53:32 kernel: LR is at 0x2abaf96c
Dec  1 10:53:32 kernel: pc : [<2b223498>]    lr : [<2abaf96c>]    psr: 80000010
Dec  1 10:53:32 kernel: sp : 7ddff558  ip : 2abb9f50  fp : 0004ae88
Dec  1 10:53:32 kernel: r10: 00000000  r9 : 00000230  r8 : 2b27a27c
Dec  1 10:53:32 kernel: r7 : 0000009e  r6 : 001e8481  r5 : 7ddff568  r4 : 00000000
Dec  1 10:53:32 kernel: r3 : 00000001  r2 : 00000000  r1 : 7ddff568  r0 : 00000000
Dec  1 10:53:32 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Dec  1 10:53:32 kernel: Control: 10c53c7d  Table: 5dc7c04a  DAC: 00000015
Dec  1 10:59:54 syslog: wlceventd_proc_event(530): eth2: Auth 00:D7:6D:51:D7:7C, status: Successful (0), rssi:0
Dec  1 10:59:54 syslog: wlceventd_proc_event(540): eth2: ReAssoc 00:D7:6D:51:D7:7C, status: Successful (0), rssi:0
Dec  1 14:07:30 syslog: wlceventd_proc_event(530): eth2: Auth 0A:08:06:D1:EC:94, status: Successful (0), rssi:0
Dec  1 14:07:30 syslog: wlceventd_proc_event(559): eth2: Assoc 0A:08:06:D1:EC:94, status: Successful (0), rssi:0
Dec  1 15:25:14 syslog: wlceventd_proc_event(494): eth2: Deauth_ind 0A:08:06:D1:EC:94, status: 0, reason: Disassociated due to inactivity (4), rssi:0
Dec  1 15:25:14 syslog: wlceventd_proc_event(511): eth2: Disassoc 0A:08:06:D1:EC:94, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec  1 15:26:18 syslog: wlceventd_proc_event(530): eth2: Auth 0A:08:06:D1:EC:94, status: Successful (0), rssi:0
Dec  1 15:26:18 syslog: wlceventd_proc_event(559): eth2: Assoc 0A:08:06:D1:EC:94, status: Successful (0), rssi:0
Dec  1 15:33:12 syslog: wlceventd_proc_event(511): eth2: Disassoc 0A:08:06:D1:EC:94, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec  1 16:33:53 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:33:53 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:33:53 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:35:52 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:35:52 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:35:52 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:35:52 miniupnpd[908]: upnpevents_processfds: 0x2f008, remove subscriber uuid:cedfbb18-22bb-47fa-9b47-d3c07166e0e9 after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/qbrtiwnizx
Dec  1 16:35:52 miniupnpd[908]: upnpevents_processfds: 0x30150, remove subscriber uuid:d1467af4-2aa3-47b9-ba06-6fc98362c389 after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/gynzcqhyrs
Dec  1 16:43:00 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:43:00 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:43:00 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 16:43:00 miniupnpd[908]: upnpevents_processfds: 0x2f008, remove subscriber uuid:864fda97-dadb-4b46-9ae5-f264452eaa70 after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/lowfosclvz
Dec  1 16:43:00 miniupnpd[908]: upnpevents_processfds: 0x30150, remove subscriber uuid:1f4a7eed-97eb-43eb-810b-5ae2311c0329 after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/ofkjiusbgm
Dec  1 17:14:53 syslog: wlceventd_proc_event(494): eth2: Deauth_ind 00:D7:6D:51:D7:7C, status: 0, reason: Unspecified reason (1), rssi:0
Dec  1 17:14:53 syslog: wlceventd_proc_event(511): eth2: Disassoc 00:D7:6D:51:D7:7C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Dec  1 17:16:19 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:16:19 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:16:19 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:16:19 miniupnpd[908]: upnpevents_processfds: 0x2f008, remove subscriber uuid:843c58ee-fd83-4c45-aab5-1d02eacf76c4 after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/ekuocmyvqh
Dec  1 17:16:19 miniupnpd[908]: upnpevents_processfds: 0x30150, remove subscriber uuid:d375afb6-f626-4459-81d3-3427d8d1c844 after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/mffcjsprez
Dec  1 17:17:10 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:10 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:18 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:18 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:23 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:23 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:32 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:32 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:35 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:35 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:40 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:40 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:44 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:44 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:47 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:47 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:52 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:17:52 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:18:06 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:18:06 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:18:28 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:18:28 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
Dec  1 17:18:28 miniupnpd[908]: upnpevents_processfds: 0x2f188, remove subscriber uuid:397fd8ef-39c2-4f15-bc16-dbc6e76c405c after an ERROR cb: http://10.0.0.5:2869/upnp/eventing/yoqibsiuiv
Dec  1 17:19:22 miniupnpd[908]: upnp_event_process_notify: connect(10.0.0.5:2869): Connection timed out
 
You must log in or register to reply here.

Similar threads

A
RT-AC88U WAN speed hitting max DL of around 500Mbps from speedtest?
Replies
9
Views
702
aftershox
A
F
Got some routers, need help.
Replies
4
Views
283
F0zeNN
F
K
RT-AC88U wan speed
Replies
11
Views
1K
keydam
K
J
Choose best wired ai mesh nodes for rt-ac88u
Replies
4
Views
725
Daddio
D
A
AIMesh problem with RT-AX88U Pro router and RT-AC88U node
Replies
4
Views
960
glens
G
Similar threads
Thread starter Title Forum Replies Date
A Hyperotpic router replacement - will it solve my problem with connection dropping! Routers 3
A Problem with port forwarding. Routers 0
A Problem with port forwarding. Routers 1
Moan A very strange problem with GT-AX6000 and QNAP QSW-1105-5T switch Routers 34
Scooterit Att Fiber with Synology Router problem Routers 6
O Router that can handle 1000Mbit Full duplex WAN-LAN Routers 36
S ASUS GT-AX110000 + OpenReach FTTP - Bizarre WAN intermittent issue Routers 0
H Any thoughts on ISP supplied TP-Link EX820v 2.5Gb WAN/LAN, AX6000 router? Routers 12
K Router recommendations for 1gbs fibre WAN and PPPOE Routers 5
A XT8 - Losing Internet WAN Connection Routers 0

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!

Members online

Total: 886 (members: 24, guests: 862)
Top