RT-AX88U - randomly WAN going down

[sharmay]

Hi,
Periodically router will loose WAN IP and when I connect to ATT Gateway I can verify internet still working, WAN address is still the same.
Hardware: AT&T Gateway <--> RT-AX88U <--> AC3100 (mesh)
RT-AX88U is in DMZ (IPPassThru)

Addons: Diversion, YazFI to isolate
Firmware: 386.4 ( same issue of previous 2-3 firmware )

Guest 1 IOT & 3 Guest 2.4 and 5 are on
YazFI enabled on all 4 guest

Question / Help :
1. Which port/device is eth7 ?
2. Any known issue with above setup ?
3. Any known hardware issues ? or any known issues related to known GUEST Wireless ?
4. What to info to capture and what logs to monitor to understand this issue ?

In case it shed any light, here is part of syslog:
Jan 6 11:05:25 wlceventd: wlceventd_proc_event(486): eth7: Disassoc B2:1A:39:CF:C5:0D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:05:25 wlceventd: wlceventd_proc_event(486): eth7: Disassoc B2:1A:39:CF:C5:0D, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:05:55 wlceventd: wlceventd_proc_event(505): eth7: Auth 22:50:50:1A7:0F, status: Successful (0)
Jan 6 11:05:55 wlceventd: wlceventd_proc_event(534): eth7: Assoc 22:50:50:1A7:0F, status: Successful (0)
Jan 6 11:05:57 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 22:50:50:1A7:0F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:05:57 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 22:50:50:1A7:0F, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:05:59 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind C2D:B5:F3:5C:45, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:06:00 wlceventd: wlceventd_proc_event(486): eth7: Disassoc C2D:B5:F3:5C:45, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:06:00 wlceventd: wlceventd_proc_event(486): eth7: Disassoc C2D:B5:F3:5C:45, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:06:35 wlceventd: wlceventd_proc_event(505): eth7: Auth 18:48:CA:18:9A:03, status: Successful (0)
Jan 6 11:06:35 wlceventd: wlceventd_proc_event(515): eth7: ReAssoc 18:48:CA:18:9A:03, status: Successful (0)
Jan 6 11:06:39 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 18:48:CA:18:9A:03, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:06:39 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 18:48:CA:18:9A:03, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:06:41 wlceventd: wlceventd_proc_event(505): eth7: Auth 18:48:CA:18:9A:03, status: Successful (0)
Jan 6 11:06:41 wlceventd: wlceventd_proc_event(534): eth7: Assoc 18:48:CA:18:9A:03, status: Successful (0)
Jan 6 11:06:45 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 18:48:CA:18:9A:03, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:06:45 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 18:48:CA:18:9A:03, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:06:56 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind D4:F5:47:91:23:FB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:07:04 wlceventd: wlceventd_proc_event(505): wl1.1: Auth D4:F5:47:91:23:FB, status: Successful (0)
Jan 6 11:07:04 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc D4:F5:47:91:23:FB, status: Successful (0)
Jan 6 11:07:08 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind D4:F5:47:91:23:FB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:07:09 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind D4:F5:47:91:23:FB, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:07:10 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 18:48:CA:18:9A:03, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:07:10 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 18:48:CA:18:9A:03, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Jan 6 11:07:36 wlceventd: wlceventd_proc_event(505): wl1.1: Auth D4:F5:47:91:23:FB, status: Successful (0)
Jan 6 11:07:36 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc D4:F5:47:91:23:FB, status: Successful (0)
Jan 6 11:07:40 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind D4:F5:47:91:23:FB, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:07:40 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind D4:F5:47:91:23:FB, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:07:45 wlceventd: wlceventd_proc_event(505): wl1.1: Auth 38:8B:59:A2:B3:72, status: Successful (0)
Jan 6 11:07:45 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc 38:8B:59:A2:B3:72, status: Successful (0)
Jan 6 11:07:49 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 38:8B:59:A2:B3:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:07:49 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 38:8B:59:A2:B3:72, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:07:50 wlceventd: wlceventd_proc_event(505): wl1.1: Auth 20F:B9:71:1A2, status: Successful (0)
Jan 6 11:07:50 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc 20F:B9:71:1A2, status: Successful (0)
Jan 6 11:07:51 wlceventd: wlceventd_proc_event(469): wl0.1: Deauth_ind 28:6D:97:F8:47:F9, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
...
Jan 6 11:07:54 wlceventd: wlceventd_proc_event(505): wl1.1: Auth E4:F0:42:26:12:8E, status: Successful (0)
Jan 6 11:07:54 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc E4:F0:42:26:12:8E, status: Successful (0)
Jan 6 11:07:54 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 20F:B9:71:1A2, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:07:58 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind E4:F0:42:26:12:8E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:07:58 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind E4:F0:42:26:12:8E, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:07:58 wlceventd: wlceventd_proc_event(505): wl1.1: Auth 54:60:09:AF:E8:72, status: Successful (0)
Jan 6 11:07:58 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc 54:60:09:AF:E8:72, status: Successful (0)
Jan 6 11:08:02 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 54:60:09:AF:E8:72, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:08:03 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 54:60:09:AF:E8:72, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:08:04 wlceventd: wlceventd_proc_event(505): wl1.1: Auth 38:8B:59:A2:B3:72, status: Successful (0)
Jan 6 11:08:04 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc 38:8B:59:A2:B3:72, status: Successful (0)
Jan 6 11:08:04 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 38:8B:59:A2:B3:72, status: 0, reason: Class 3 frame received from nonassociated station (7)
..
Jan 6 11:08:05 wlceventd: wlceventd_proc_event(469): wl0.1: Deauth_ind 64:69:4E:31:C9:76, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:08:07 wlceventd: wlceventd_proc_event(505): wl1.1: Auth 20F:B9:71:1A2, status: Successful (0)
Jan 6 11:08:08 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc 20F:B9:71:1A2, status: Successful (0)
Jan 6 11:08:11 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 20F:B9:71:1A2, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:08:12 wlceventd: wlceventd_proc_event(505): wl1.1: Auth E4:F0:42:26:12:8E, status: Successful (0)
Jan 6 11:08:12 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc E4:F0:42:26:12:8E, status: Successful (0)
Jan 6 11:08:12 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind 20F:B9:71:1A2, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:08:16 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind E4:F0:42:26:12:8E, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Jan 6 11:08:16 wlceventd: wlceventd_proc_event(469): wl1.1: Deauth_ind E4:F0:42:26:12:8E, status: 0, reason: Previous authentication no longer valid (2)
Jan 6 11:08:17 wlceventd: wlceventd_proc_event(505): wl1.1: Auth D4:F5:47:91:23:FB, status: Successful (0)
Jan 6 11:08:17 wlceventd: wlceventd_proc_event(534): wl1.1: Assoc D4:F5:47:91:23:FB, status: Successful (0)

Any help is appreciated.

Thank you
YS

 

[ColinTaylor]

All the information you posted is about WiFi connections. I don't understand why any of that is relevant to a WAN IP problem. What exactly do you mean by "loose WAN IP"?

 

[sharmay]

All the information you posted is about WiFi connections. I don't understand why any of that is relevant to a WAN IP problem. What exactly do you mean by "loose WAN IP"?

That is all I see in syslog besides DROP packet messages.

 

[ColinTaylor]

What exactly do you mean by "loose WAN IP"?

 

[sharmay]

What exactly do you mean by "loose WAN IP"?

ifconfig eth0 shows no IP and WAN light is red.

 

[sharmay]

Any idea about this log message ?
br0: received packet on eth7 with own address as source address

On router WAN,1,2,3 are only port in use, what is eth7 ?

 

[ColinTaylor]

Upload the complete unedited syslog to pastebin.com and post a link to it so we can take a look.

Does the log on the AT&T Gateway show the link to the router going down?

Is the router's WAN interface type set to Automatic IP (i.e. DHCP)? Does the problem coincide with its DHCP lease renewal?

Any idea about this log message ?
br0: received packet on eth7 with own address as source address

That's normal, ignore it.

On router WAN,1,2,3 are only port in use, what is eth7 ?

eth7 is the 5GHz wireless interface.

 

[sharmay]

Upload the complete unedited syslog to pastebin.com and post a link to it so we can take a look.

I will get this when I run into this issue.

Does the log on the AT&T Gateway show the link to the router going down?

I will capture logs next time. On interface ATT Gateway it was showing disconnected.

Is the router's WAN interface type set to Automatic IP (i.e. DHCP)? Does the problem coincide with its DHCP lease renewal?

Yes, automatic. I will check on dhcp lease and monitor it.

That's normal, ignore it.

eth7 is the 5GHz wireless interface.

Thank you.

I use same ssid for 2.4GHz & 5GHz. So total of 3 ssid 1 for wireless Guest 1, Guest 2.