cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
mr-b
Aspiring Contributor
1,616 Views
Message 1 of 4

Intermittent loss of internet solved by restart

Hi

 

My new whole home wifi suffers from intermittent connectivity issues and where a restart of the main disc is necessary. The discs are connected by homeplugs. Firmware is v1.02.03 build03. Clients remain connected but internet access is lost. The disc lights are blue.

The logs dont seem to show anything untoward, but ill paste them in once i get them. The upstream router is a Zyxel Vmg1312 and has its wifi disabled.

 

Any ideas on what the issue could be or how to diagnose these issues?

0 Ratings
Reply
3 REPLIES 3
mr-b
Aspiring Contributor
1,614 Views
Message 2 of 4

Re: Intermittent loss of internet solved by restart

23.02.2018 01:25:19 [4 4 1] IF[2.4G]:STA(9c:35:eb:98:0f:a5) had associated successfully
23.02.2018 01:45:42 [4 4 1] IF[2.4G]:STA(9c:35:eb:98:0f:a5) had been aged-out and disassociated
23.02.2018 02:22:14 [4 4 1] IF[2.4G]:STA(9c:35:eb:98:0f:a5) had associated successfully
23.02.2018 02:27:03 [4 4 0] Free Memory 58828K.
23.02.2018 02:30:44 [4 4 1] IF[2.4G]:STA(9c:35:eb:98:0f:a5) had been aged-out and disassociated
23.02.2018 08:21:08 [4 4 1] IF[5G]:STA(4e:8d:36:eb:72:95) had associated successfully
23.02.2018 08:21:15 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(AC:3C:0B:B0:68:C4) connected.
23.02.2018 08:21:18 [4 4 1] IF[2.4G]:STA(4e:8d:36:eb:72:94) had associated successfully
23.02.2018 08:21:40 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 13:40:50 [2 4 9] Start logging.
23.02.2018 13:41:15 [2 4 1] HTTP-start ...
23.02.2018 13:41:15 [2 4 1] Current firmware version is v1.02.03 build03 and boot flag is 1.
23.02.2018 13:41:25 [2 4 2] OWL-start
23.02.2018 13:41:25 [4 4 0] Free Memory 68852K.
23.02.2018 13:41:32 [2 4 2] OWL-Backhaul Monitor Start.
23.02.2018 13:41:34 [4 4 0] Ethernet Port 0 Link Up.
23.02.2018 13:41:41 [2 4 2] OWL-Lounge become slave in topology
23.02.2018 13:41:41 [2 4 2] OWL-Lounge(48:8D:36:EB:7C:E7) join topology
23.02.2018 13:41:41 [2 4 2] OWL-Backhaul Ethernet being used for uplink mode.
23.02.2018 13:41:48 [2 4 4] DHCPC-Obtain new IP 192.168.1.42 and netmask 255.255.255.0
23.02.2018 13:41:48 [2 4 2] OWL-Backhaul Ethernet being used for uplink mode.
23.02.2018 13:41:49 [2 4 1] HTTP-start ...
23.02.2018 13:41:49 [2 4 1] Current firmware version is v1.02.03 build03 and boot flag is 1.
23.02.2018 13:41:50 [2 4 2] OWL-Backhaul Ethernet being used for downlink mode.
23.02.2018 13:41:51 [2 4 2] OWL-Adjust LED from Dim to Dim.
23.02.2018 13:41:53 [2 4 2] OWL-RE work fine, but no uplink, turn off downlink backhaul Wi-Fi SSID.
23.02.2018 13:41:55 [2 4 2] OWL-Adjust LED from Dim to Dim.
23.02.2018 13:42:06 [2 4 2] OWL-Backhaul WiFi Link Up apclii0.
23.02.2018 13:42:06 [2 4 2] OWL-Backhaul RE 5G exceeded the threshold for other reasons..
23.02.2018 13:42:07 [2 4 2] OWL-start
23.02.2018 13:42:15 [2 4 2] OWL-Backhaul WiFi Link Down apclii0.
23.02.2018 13:42:18 [2 4 2] OWL-RE work fine, but no uplink, turn off downlink backhaul Wi-Fi SSID.
23.02.2018 13:42:18 [2 2 0] 
23.02.2018 13:42:18 [2 2 0] No subnet declaration for br0 (no IPv4 addresses).
23.02.2018 13:42:18 [2 2 0] ** Ignoring requests on br0.  If this is not what
23.02.2018 13:42:18 [2 2 0] you want, please write a subnet declaration
23.02.2018 13:42:18 [2 2 0] in your dhcpd.conf file for the network segment
23.02.2018 13:42:18 [2 2 0] to which interface br0 is attached. **
23.02.2018 13:42:18 [2 2 0] 
23.02.2018 13:42:18 [2 2 0] Not configured to listen on any interfaces!
23.02.2018 13:42:18 [2 4 1] HTTP-start ...
23.02.2018 13:42:18 [2 4 1] Current firmware version is v1.02.03 build03 and boot flag is 1.
23.02.2018 13:42:20 [2 2 0] 
23.02.2018 13:42:20 [2 2 0] No subnet declaration for br0 (no IPv4 addresses).
23.02.2018 13:42:20 [2 2 0] ** Ignoring requests on br0.  If this is not what
23.02.2018 13:42:20 [2 2 0] you want, please write a subnet declaration
23.02.2018 13:42:20 [2 2 0] in your dhcpd.conf file for the network segment
23.02.2018 13:42:20 [2 2 0] to which interface br0 is attached. **
23.02.2018 13:42:20 [2 2 0] 
23.02.2018 13:42:20 [2 2 0] Not configured to listen on any interfaces!
23.02.2018 13:42:24 [4 4 1] IF[2.4G]:STA(ac:3c:0b:b0:68:c4) had associated successfully
23.02.2018 13:42:29 [2 4 2] OWL-Backhaul Ethernet being used for uplink mode.
23.02.2018 13:42:41 [2 4 4] DHCPC-Obtain new IP 192.168.1.43 and netmask 255.255.255.0
23.02.2018 13:42:42 [2 4 1] HTTP-start ...
23.02.2018 13:42:42 [2 4 1] Current firmware version is v1.02.03 build03 and boot flag is 1.
23.02.2018 13:42:50 [2 4 2] OWL-Lounge become slave in topology
23.02.2018 13:42:50 [2 4 2] OWL-Lounge(48:8D:36:EB:7C:E7) join topology
23.02.2018 13:42:56 [2 4 2] OWL-Adjust LED from Dim to Dim.
23.02.2018 13:42:59 [2 4 2] OWL-Adjust LED from Dim to Dim.
23.02.2018 13:43:00 [2 4 2] OWL-Adjust LED from Dim to Dim.
23.02.2018 13:43:01 [2 4 2] OWL-Sync config success
23.02.2018 13:43:04 [2 4 2] OWL-Sync config success
23.02.2018 13:43:05 [2 4 2] OWL-Sync config success
23.02.2018 13:43:13 [2 4 2] OWL-Adjust LED from Dim to Dim.
23.02.2018 13:43:18 [2 4 2] OWL-start
23.02.2018 13:43:22 [2 4 2] OWL-Sync config success
23.02.2018 13:44:01 [4 4 1] IF[2.4G]:STA(ac:3c:0b:b0:68:c4) had associated successfully
23.02.2018 13:46:21 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 13:48:59 [4 4 1] IF[5G]:STA(00:b3:62:89:56:c7) had associated successfully
23.02.2018 13:49:19 [4 2 1] IF[5G]:STA(00:b3:62:89:56:c7) had deauthenticated
23.02.2018 13:49:41 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 13:52:29 [4 4 1] IF[2.4G]:STA(ac:3c:0b:b0:68:c4) had been aged-out and disassociated
23.02.2018 13:53:01 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 13:56:21 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 13:59:42 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 14:03:02 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 14:04:03 [4 4 1] IF[2.4G]:STA(ac:3c:0b:b0:68:c4) had associated successfully
23.02.2018 14:04:08 [4 4 1] IF[5G]:STA(00:b3:62:89:56:c7) had associated successfully
23.02.2018 14:04:15 [2 4 1] HTTP-start ...
23.02.2018 14:04:15 [2 4 1] Current firmware version is v1.02.03 build03 and boot flag is 1.
23.02.2018 14:04:19 [2 4 2] OWL-Lounge(48:8D:36:EB:7C:E7) leave topology
23.02.2018 14:04:19 [2 4 2] OWL-Lounge become master in topology
23.02.2018 14:05:23 [2 4 2] OWL-(Lounge)IF[5G](48:8D:36:EB:7C:E9):STA(00:B3:62:89:56:C7)(RSSI_Low AP_ROAM)(BTM)(48:8D:36:EB:72:95) start.
23.02.2018 14:05:25 [2 4 2] OWL-Kitchen(48:8D:36:EB:72:93) join topology
23.02.2018 14:05:29 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:05:29 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7)(RSSI_Low AP_ROAM)(BTM)(48:8D:36:EB:72:95) finish.
23.02.2018 14:05:33 [2 4 2] Firmware upgrade - FW SYNC compare WHWv1.02.03build03 WHWv1.02.03build03!
23.02.2018 14:05:33 [2 4 2] OWL-Sync config success
23.02.2018 14:06:22 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 14:06:24 [4 2 1] IF[5G]:STA(00:b3:62:89:56:c7) had deauthenticated
23.02.2018 14:06:35 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(AC:3C:0B:B0:68:C4) connected.
23.02.2018 14:06:35 [2 4 2] OWL-(Kitchen)IF[2.4G](48:8D:36:EB:72:94):STA(AC:3C:0B:B0:68:C4) connected.
23.02.2018 14:06:46 [4 4 1] IF[5G]:STA(00:b3:62:89:56:c7) had associated successfully
23.02.2018 14:06:47 [2 4 2] OWL-(Lounge)IF[5G](48:8D:36:EB:7C:E9):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:06:58 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:07:06 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:08:05 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:09:42 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 14:12:48 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:13:02 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 14:13:02 [4 4 1] IF[2.4G]:STA(ac:3c:0b:b0:68:c4) had been aged-out and disassociated
23.02.2018 14:13:37 [4 4 1] IF[5G]:STA(ac:3c:0b:b0:68:c4) had associated successfully
23.02.2018 14:13:37 [2 4 2] OWL-(Lounge)IF[5G](48:8D:36:EB:7C:E9):STA(AC:3C:0B:B0:68:C4) connected.
23.02.2018 14:13:38 [4 4 1] IF[5G]:STA(00:b3:62:89:56:c7) had associated successfully
23.02.2018 14:13:54 [2 4 2] OWL-Kitchen(48:8D:36:EB:72:93) leave topology
23.02.2018 14:14:56 [2 4 2] OWL-Kitchen(48:8D:36:EB:72:93) join topology
23.02.2018 14:15:07 [2 4 2] Firmware upgrade - FW SYNC compare WHWv1.02.03build03 WHWv1.02.03build03!
23.02.2018 14:15:07 [2 4 2] OWL-Sync config success
23.02.2018 14:15:09 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:15:13 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(AC:3C:0B:B0:68:C4) connected.
23.02.2018 14:15:46 [4 4 1] IF[5G]:STA(00:b3:62:89:56:c7) had associated successfully
23.02.2018 14:15:47 [2 4 2] OWL-(Lounge)IF[5G](48:8D:36:EB:7C:E9):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:15:54 [4 4 1] IF[5G]:STA(4e:8d:36:eb:72:95) had associated successfully
23.02.2018 14:16:05 [4 4 1] IF[2.4G]:STA(4e:8d:36:eb:72:94) had associated successfully
23.02.2018 14:16:22 [2 2 6] Time Server connected but Server responded with Error(14).
23.02.2018 14:17:34 [2 4 2] OWL-Kitchen(48:8D:36:EB:72:93) leave topology
23.02.2018 14:18:18 [2 4 6] NTP-Time Server successfully connected and time synchronisation achieved.
23.02.2018 14:18:25 [2 4 2] OWL-Kitchen(48:8D:36:EB:72:93) join topology
23.02.2018 14:18:26 [2 4 2] Firmware upgrade - FW SYNC compare WHWv1.02.03build03 WHWv1.02.03build03!
23.02.2018 14:18:26 [2 4 2] OWL-Sync config success
23.02.2018 14:20:09 [4 4 1] IF[5G]:STA(00:b3:62:89:56:c7) had associated successfully
23.02.2018 14:20:09 [2 4 2] OWL-(Lounge)IF[5G](48:8D:36:EB:7C:E9):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:20:43 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 14:26:09 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(B4:AE:2B:64:5A:96) connected.
23.02.2018 14:27:37 [4 2 1] IF[5G]:STA(00:b3:62:89:56:c7) had deauthenticated
23.02.2018 14:28:05 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(20:C9:D0:D0:10:8F) connected.
23.02.2018 14:58:31 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(9C:35:EB:98:0F:A5) connected.
23.02.2018 15:14:25 [2 4 2] OWL-(Kitchen)IF[2.4G](48:8D:36:EB:72:94):STA(9C:35:EB:98:0F:A5) connected.
23.02.2018 15:15:55 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(B4:AE:2B:64:5A:96) connected.
23.02.2018 15:15:56 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(20:C9:D0:D0:10:8F) connected.
23.02.2018 15:15:56 [2 4 2] OWL-(Kitchen)IF[5G](48:8D:36:EB:72:95):STA(00:B3:62:89:56:C7) connected.
23.02.2018 15:16:07 [2 4 2] OWL-(Kitchen)IF[2.4G](48:8D:36:EB:72:94):STA(9C:35:EB:98:0F:A5) connected.
23.02.2018 15:17:25 [4 4 1] IF[2.4G]:STA(9c:35:eb:98:0f:a5) had associated successfully
0 Ratings
Reply
ciscosurplus
Beginner
1,556 Views
Message 3 of 4

Re: Intermittent loss of internet solved by restart

I have been getting the same issue mainly under heavy load. Intrestinly the App said no FW update available and was running the same FW version as you. 

 

I went in to the main disc via the webpage for it, and when I clicked checked for update it had one available. 

 

I updated to v1.02.04 build10 this morning, and before update the network would lock up every 1-2 hours. I even set the channels manually as per advise on here and it didnt help. It been running for 5 hours now without locking up (so far). 

 

The firmware upgrade for now seems to have fixed it (for now) 

 

 

0 Ratings
Reply
mr-b
Aspiring Contributor
1,541 Views
Message 4 of 4

Re: Intermittent loss of internet solved by restart

I checked too but it didn't give me any option.
Will try again later. I only see the issue after a week or so, so I'd guess at a memory leak that a restart clears.

Not sure how manually setting the channels would make any difference though as there are no neighbouring WiFi APs nearby. Or does that fix another issue?
0 Ratings
Reply