Solved ax88u lost internet today LAN and wifi - do my logs provide a clue?

blacktop_

Occasional Visitor
Hello,

Running ax88u 3.0.0.4.388_20518, after factory reset and followed L&LD first steps of rebooting and waiting. Only things set up are wifi 2.4 and 5 gHz with different SSID and passwords.

(working to recover from this problem: https://www.snbforums.com/threads/a...hen-network-is-192-168-1-x.80758/#post-788574)

Today ~10:00 LAN and wifi ceased to function, then for the next two hours was irratic / slow in its function. My ability to understand these logs is limited.

Searching for the Deauthenticated error did not seem to explain why the LAN was down. There is a high possibilty that it is my ISP as they are doing infrastructure upgrades in the neighbourhood.

If more log data would be helpful, I will post it. A truncated version is below, I am not sure how to best post more.

Thanks for taking a look.

Kind regards,
 

blacktop_

Occasional Visitor
Code:
Sep 14 08:38:42 wlceventd: wlceventd_proc_event(559): eth6: Assoc A2:3A:52:FA:0E:55, status: Successful (0), rssi:-75
Sep 14 10:09:50 wlceventd: wlceventd_proc_event(530): eth6: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 10:09:50 wlceventd: wlceventd_proc_event(559): eth6: Assoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-55
Sep 14 10:09:50 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 1A:B9:A0:B1:35:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:09:50 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 1A:B9:A0:B1:35:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:09:53 wlceventd: wlceventd_proc_event(530): eth7: Auth 1A:B9:A0:B1:35:48, status: Successful (0), rssi:0
Sep 14 10:09:53 wlceventd: wlceventd_proc_event(559): eth7: Assoc 1A:B9:A0:B1:35:48, status: Successful (0), rssi:-76
Sep 14 10:10:23 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 10:10:24 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 10:10:24 wlceventd: wlceventd_proc_event(559): eth7: Assoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-80
Sep 14 10:11:38 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 1A:B9:A0:B1:35:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:11:38 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 1A:B9:A0:B1:35:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:11:38 wlceventd: wlceventd_proc_event(530): eth6: Auth 6E:28:C4:1C:F4:76, status: Successful (0), rssi:0
Sep 14 10:11:38 wlceventd: wlceventd_proc_event(559): eth6: Assoc 6E:28:C4:1C:F4:76, status: Successful (0), rssi:-61
Sep 14 10:12:08 wlceventd: wlceventd_proc_event(511): eth6: Disassoc 6E:28:C4:1C:F4:76, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:12:08 wlceventd: wlceventd_proc_event(511): eth6: Disassoc 6E:28:C4:1C:F4:76, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:12:09 wlceventd: wlceventd_proc_event(530): eth7: Auth 1A:B9:A0:B1:35:48, status: Successful (0), rssi:0
Sep 14 10:12:09 wlceventd: wlceventd_proc_event(559): eth7: Assoc 1A:B9:A0:B1:35:48, status: Successful (0), rssi:-75
Sep 14 10:13:17 wlceventd: wlceventd_proc_event(511): eth6: Disassoc A2:3A:52:FA:0E:55, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:13:17 wlceventd: wlceventd_proc_event(511): eth6: Disassoc A2:3A:52:FA:0E:55, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 10:29:25 wlceventd: wlceventd_proc_event(530): eth6: Auth A2:3A:52:FA:0E:55, status: Successful (0), rssi:0
Sep 14 10:29:25 wlceventd: wlceventd_proc_event(559): eth6: Assoc A2:3A:52:FA:0E:55, status: Successful (0), rssi:-69
Sep 14 10:38:32 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 10:38:34 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 10:38:34 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-78
Sep 14 10:38:49 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 10:41:39 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 10:41:39 wlceventd: wlceventd_proc_event(559): eth7: Assoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-79
Sep 14 10:41:55 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 10:41:57 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 10:41:57 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-79
Sep 14 10:43:43 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 12:14:54 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 12:14:54 wlceventd: wlceventd_proc_event(559): eth7: Assoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-78
Sep 14 12:15:10 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 12:15:10 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 12:15:10 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-78
Sep 14 12:15:26 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 12:15:32 wlceventd: wlceventd_proc_event(530): eth7: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 12:15:32 wlceventd: wlceventd_proc_event(559): eth7: Assoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-78
Sep 14 12:15:44 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind A2:3A:52:FA:0E:55, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-59
Sep 14 12:15:44 wlceventd: wlceventd_proc_event(494): eth6: Deauth_ind A2:3A:52:FA:0E:55, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3), rssi:-59
Sep 14 12:15:45 wlceventd: wlceventd_proc_event(511): eth6: Disassoc A2:3A:52:FA:0E:55, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 12:16:29 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 1A:B9:A0:B1:35:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 12:16:29 wlceventd: wlceventd_proc_event(511): eth7: Disassoc 1A:B9:A0:B1:35:48, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
Sep 14 12:16:29 wlceventd: wlceventd_proc_event(530): eth6: Auth 6E:28:C4:1C:F4:76, status: Successful (0), rssi:0
Sep 14 12:16:29 wlceventd: wlceventd_proc_event(559): eth6: Assoc 6E:28:C4:1C:F4:76, status: Successful (0), rssi:-60
Sep 14 12:16:36 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 18:5E:0F:B5:A5:5E, status: 0, reason: Unspecified reason (1), rssi:0
Sep 14 12:16:37 wlceventd: wlceventd_proc_event(530): eth6: Auth 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:0
Sep 14 12:16:37 wlceventd: wlceventd_proc_event(559): eth6: Assoc 18:5E:0F:B5:A5:5E, status: Successful (0), rssi:-54
Sep 14 12:16:39 wlceventd: wlceventd_proc_event(511): eth6: Disassoc 6E:28:C4:1C:F4:76, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:0
 

ColinTaylor

Part of the Furniture
There's nothing particularly unusual there. A couple of your devices have a very weak connection on 5GHz which could be causing them problems.

If your ISP is having issues then that wouldn't really show up in the log. Some mobile devices don't like it when they can't reach the internet and will constantly disconnect and reconnect to the AP. But you said it affected Ethernet connected devices as well and there's nothing in the log to suggest a router problem (unless you're showing us an incomplete log file).
 
Last edited:

blacktop_

Occasional Visitor
There's nothing particularly unusual there. A couple of your devices have a very weak connection on 5GHz which could be causing them problems.

If your ISP is having issues then that wouldn't really show up in the log. Some mobile devices don't like it when they can't reach the internet and will constantly disconnect and reconnect to the AP. But you said it affected Ethernet connected devices as well and there's nothing in the log to suggest a router problem (unless you're showing us an incomplete log file).
Thanks for your quick reply. The log is complete from Sep 14 10:09:50 to Sep 14 12:16:39, as that was all I could put in the post. The only truncation was before and after these times. If that would be informative I could post them (with some guidance on how to put more than 10,000 characters).

I am totally puzzled. Family reported no LAN devices worked, nor were there any 'bars' on apple devices to indicate wifi was available. I am unable to say if other devices were offline, that said, I will check my NAS log and see if it was offline.
 

ColinTaylor

Part of the Furniture
I'm assuming by "LAN devices" you're talking about Ethernet connected devices. I'm also assuming that you currently only have the single router set up, without any other AiMesh nodes, switches, powerline adapters, etc.

If you need to post bigger log files you can put them on pastebin.com and provide a link to it.
 

blacktop_

Occasional Visitor
I'm assuming by "LAN devices" you're talking about Ethernet connected devices. I'm also assuming that you currently only have the single router set up, without any other AiMesh nodes, switches, powerline adapters, etc.

If you need to post bigger log files you can put them on pastebin.com and provide a link to it.

It is a bit of a messy set up to draw out in text, this is a revised version

ISP router
|
|
ax88u
|
|
|
-LAN cables to most of the things in the house
|
|
-LAN---au68u-AP with 3 directional antenna))) wifi (((au68u-media-bridge with 3 directional antenna---LAN---au68u))) wifi to remote site


Of note, the NAS log does not show that the connectivity was lost via the LAN cable that connects it directly to the ax88u.
 
Last edited:

ColinTaylor

Part of the Furniture
au68u?

Thanks for the additional log file. There's nothing in there that indicates there was any system wide problem.
 
Last edited:

OzarkEdge

Part of the Furniture

blacktop_

Occasional Visitor
I'm confused why you are discussing your network issue in two different subforums/threads and one is marked SOLVED.

OE
Thanks for your reply. This thread is about a new issue.

This problem (https://www.snbforums.com/threads/a...hen-network-is-192-168-1-x.80758/#post-788574), specifically the routing issue of devices on 192.168.0.x when the router is 192.168.1.x, has been resolved as per the other post. Perhaps providing the link introduced unnecessary clutter.



The new problem this post is seeking to understand is that internet via wifi and LAN connected devices on a newly flashed device with factory ASUS firmware is unstable.

Presently, I do not have the ability to interpret the logs to determine if there is a router problem vs ISP problem. With the help of the above, it seems it may be a ISP problem.

I will leave this open for a few day to see if it happens again.

Kind regards.
 

OzarkEdge

Part of the Furniture
The new problem this post is seeking to understand is that internet via wifi and LAN connected devices on a newly flashed device with factory ASUS firmware is unstable.

So, given:

ISP router (router mode?) >> AX88U (router mode; double natted?) >> other LAN/WLAN devices

All 'other LAN/WLAN devices' connected to the AX88U are losing Internet access, but the AX88U log does not indicate that its WAN connection is down.

o did you reset the AX88U firmware to its defaults first before configuring it from scratch for a clean install?

o are the other LAN/WLAN device still able to use the local network when Internet access is down?

o have you rebooted the ISP equipment?

o have you logged into the ISP router to review its log, if any?

o have you disconnected the ISP router WAN connection and wired a PC to the ISP modem, if any, to confirm Internet access?

o have you disconnect the AX88U WAN connection and wired a PC to the ISP router to confirm Internet access?

o have you disconnected all other LAN/WLAN devices and wired a PC to the AX88U to confirm Internet access?

o have you temporarily swapped in a known good Ethernet cable for intervening Ethernet segments/switches to confirm Internet access?

o have you confirmed the integrity of the ISP cable/connections and bonding to Earth Ground at the building demarc?

o have you contacted the ISP to have them remotely review their equipment/logs for trouble?

Given the AX88U log indicates no WAN issue, perhaps the issue is with the ISP but not the connection; or with routing/configuation of the 'other LAN/WLAN devices', like more than one DHCP server in service.

OE
 
Last edited:

blacktop_

Occasional Visitor
So, given:

ISP router (router mode?) >> AX88U (router mode; double natted?) >> other LAN/WLAN devices
- ISP router is in bridge mode. Then I reinstalled all the firmware on the routers and redid the configuration from factory defaults.
All 'other LAN/WLAN devices' connected to the AX88U are losing Internet access, but the AX88U log does not indicate that its WAN connection is down.

o did you reset the AX88U firmware to its defaults first before configuring it from scratch for a clean install?
- yes.
o are the other LAN/WLAN device still able to use the local network when Internet access is down?
- It seems my NAS did not log an error message that the intranet went down.
o have you rebooted the ISP equipment?
- so obvious, I can't believe I omitted this step. Done.
o have you logged into the ISP router to review its log, if any?
- The ISP router only logs who logs on, literally nothing else. I poked around to see if there was more, none.
o have you disconnected the ISP router WAN connection and wired a PC to the ISP modem, if any, to confirm Internet access?
- PC connected to internet.
o have you disconnect the AX88U WAN connection and wired a PC to the ISP router to confirm Internet access?
- PC connected to internet.
o have you disconnected all other LAN/WLAN devices and wired a PC to the AX88U to confirm Internet access?
- Yes, this was my starting point, confirms internet access.
o have you temporarily swapped in a known good Ethernet cable for intervening Ethernet segments/switches to confirm Internet access?
- Yes, switched to cat 6 cables, new and confirmed working.
o have you confirmed the integrity of the ISP cable/connections and bonding to Earth Ground at the building demarc?
- The ISP came out and tested the line, replaced the run from the building to their line outside. Reports is it stable.
o have you contacted the ISP to have them remotely review their equipment/logs for trouble?
- Not at time of writing.
Given the AX88U log indicates no WAN issue, perhaps the issue is with the ISP but not the connection; or with routing/configuation of the 'other LAN/WLAN devices', like more than one DHCP server in service.

OE

This was a great post, thanks for providing the level of detail that I was able to break down the tasks. I will save this list and use it for best practices. I also have a cable tester now, will work through all the lines and confirm they are good.

I will mark this as solved given the infrastructure replacement likely identifies that is was an ISP problem.

Thank you OE and everyone that helped with this problem, and all the other posts here than have helped me navigate this entire internet journey.

Thank you.
 

Hammerthrowerlu

New Around Here
Hello,

Running ax88u 3.0.0.4.388_20518, after factory reset and followed L&LD first steps of rebooting and waiting. Only things set up are wifi 2.4 and 5 gHz with different SSID and passwords.

(working to recover from this problem: https://www.snbforums.com/threads/a...hen-network-is-192-168-1-x.80758/#post-788574)

Today ~10:00 LAN and wifi ceased to function, then for the next two hours was irratic / slow in its function. My ability to understand these logs is limited.

Searching for the Deauthenticated error did not seem to explain why the LAN was down. There is a high possibilty that it is my ISP as they are doing infrastructure upgrades in the neighbourhood.

If more log data would be helpful, I will post it. A truncated version is below, I am not sure how to best post more.

Thanks for taking a look.

Kind regards,
Hi
You have an apple device?
 

blacktop_

Occasional Visitor

Hammerthrowerlu

New Around Here
It is a mix of all sorts of devices - linux, windows, apple.
I say this because me and other people have freezes because Router haba problem with apple devices. In case You have low signal router lost wan conecction and freeze only work If You make a reboot to work again i think You have the same problem probably. I am talking with ASUS in Spain to try solve this problem but os imposible horrible support and make me lost time with a lot of test without results.
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top