Time Synch fail & WAN connection loss

Product Discussion Pepwave AP & Surf
1

Almost like clockwork, each night I lose my internet connection. After looking through my logs, I see a time synchronization failed message around the same time I lose my connections. Here is a sample.

Preformatted text Device Event Log Apr 28 10:20:16 Admin: MooLAeFdi (192.168.29.11) login successful Apr 27 23:54:08 System: Time synchronization successful Dec 31 19:02:06 System: Wi-Fi AP Normal Mode Dec 31 19:01:41 WAN: WAN connected (**********) Dec 31 19:01:13 Web blocking: Activated Dec 31 19:01:01 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex) Dec 31 19:00:57 System: Started up (7.1.2 build 1387) Apr 27 23:07:37 System: Time synchronization successful Apr 27 22:50:11 Admin: MooLAeFdi (192.168.29.11) logout Apr 27 22:41:17 System: Changes applied Apr 27 22:39:20 System: Changes applied Apr 27 22:38:10 Admin: MooLAeFdi (192.168.29.11) login successful Apr 27 22:15:06 System: Time synchronization fail Apr 26 22:40:38 Admin: admin (192.168.29.11) logout Apr 26 22:40:08 System: Changes applied Apr 26 22:36:41 System: Changes applied Apr 26 22:35:20 System: Changes applied Apr 26 22:33:19 Admin: admin (192.168.29.11) login successful Apr 26 22:33:09 Admin: MooLAeFdi (192.168.29.11) login failed Apr 26 22:32:39 Admin: MooLAeFdi (192.168.29.11) login failed Apr 26 22:32:24 Admin: MooLaeFdi (192.168.29.11) login failed Apr 26 22:31:09 System: Time synchronization successful Dec 31 19:02:03 System: Wi-Fi AP Normal Mode Dec 31 19:01:34 WAN: WAN connected (98.166.81.112) Dec 31 19:01:09 Web blocking: Activated Dec 31 19:00:57 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex) Dec 31 19:00:52 System: Started up (7.1.2 build 1387) Apr 26 22:27:14 System: Changes applied Apr 26 20:43:22 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex) Apr 26 20:35:04 Port: Port 2 status changed (link down) Apr 26 20:32:49 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex) Apr 26 20:22:09 Port: Port 2 status changed (link down) Apr 26 19:26:49 System: Time synchronization fail Apr 26 18:22:04 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=108.178.16.154 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=54321 PROTO=TCP SPT=56785 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 18:14:45 Admin: MooLAeFdi (192.168.29.11) logout Apr 26 18:13:40 Admin: MooLAeFdi (192.168.29.11) login successful Apr 26 16:45:03 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=216.243.31.2 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=54321 PROTO=TCP SPT=52728 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 15:27:32 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=185.173.35.21 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=35517 PROTO=TCP SPT=65154 DPT=443 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 14:07:21 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=185.53.88.157 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=41627 PROTO=TCP SPT=56356 DPT=443 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 13:31:34 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=185.5.64.120 DST=192.168.29.200 LEN=48 TOS=0x00 PREC=0x00 TTL=252 ID=1717 PROTO=TCP SPT=64697 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 09:11:45 Admin: MooLAeFdi (192.168.29.11) logout Apr 26 09:09:39 WAN: WAN changes applied Apr 26 08:58:19 Admin: MooLAeFdi (192.168.29.11) login successful Apr 26 08:53:55 System: Time synchronization successful Dec 31 19:02:04 System: Wi-Fi AP Normal Mode Dec 31 19:01:37 WAN: WAN connected (********) Dec 31 19:01:10 Web blocking: Activated Dec 31 19:00:57 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex) Dec 31 19:00:53 System: Started up (7.1.2 build 1387) Apr 26 07:40:38 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex) Apr 26 07:32:39 Port: Port 2 status changed (link down) Apr 26 07:15:23 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=185.234.217.42 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=27720 PROTO=TCP SPT=58018 DPT=443 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 05:13:10 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=45.79.106.170 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=54321 PROTO=TCP SPT=41329 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 03:30:54 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=125.64.94.210 DST=192.168.29.200 LEN=60 TOS=0x00 PREC=0x00 TTL=252 ID=61559 DF PROTO=TCP SPT=51968 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 03:28:14 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=125.64.94.210 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=54321 PROTO=TCP SPT=46428 DPT=443 WINDOW=65535 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 00:28:16 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=104.152.52.25 DST=192.168.29.200 LEN=44 TOS=0x00 PREC=0x00 TTL=252 ID=41331 PROTO=TCP SPT=51707 DPT=443 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0xa Apr 26 00:14:13 Allowed CONN=WAN1 MAC=00:1a:dd:43:40:81:84:8a:8d:32:cc:19:08:00 SRC=108.178.16.154 DST=192.168.29.200 LEN=60 TOS=0x00 PREC=0x00 TTL=252 ID=24243 DF PROTO=TCP SPT=58804 DPT=443 WINDOW=29200 RES=0x00 SYN URGP=0 MARK=0xa

What can I do to fix this?

1 Like
2

Hi,
in the Log I found the following lines

So, it seems to sync the Time.
Is it a DSL-Line? In Germany for example the ISP will reset your connection every night.

Regards
Dennis

3
Apr 29 08:21:19 System: Time synchronization successful
Dec 31 19:02:04 System: Wi-Fi AP Normal Mode
Dec 31 19:01:36 WAN: WAN connected (98.166.81.112)
Dec 31 19:01:09 Web blocking: Activated
This logs below be a better representation of my problem. I have cable internet, and each time I lose my connection, I have to reset the power on my router to get my internet connection back. I don’t know of any nightly resets from my cable company. Thaanks

|Dec 31 19:00:57|Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex)|
|Dec 31 19:00:53|System: Started up (7.1.2 build 1387)|
|Apr 29 07:48:38|System: Time synchronization successful|
|Apr 28 22:25:01|System: Time synchronization fail|
|Apr 28 21:55:01|System: Time synchronization successful|
|Apr 28 21:29:17|System: Time synchronization fail|

4

It happened again tonight, and twice. Around 10 PM or so, the router dropped its WAN connection so I reset the router. Then at about 1130 or 1145 it dropped the connection again. I have noticed that when it does this I can’t login to the router, and I have to unplug it to reset it. Here is a log showing time sync failures. Even if it succeeds a time or two, it will still fail around 10 PM and drop my internet connection. My cable TV stays working, and I have the default time server on the router. Maybe its not the time synch problem but I’m not sure what else to look for or how to enable additional logging. I’m really stuck on this so any help is greatly appreciated. Here are logs.

Apr 30 00:12:34 Admin: MooLAeFdi (192.168.29.11) login successful
Apr 30 00:11:14 System: Time synchronization successful
Dec 31 19:02:01 System: Wi-Fi AP Normal Mode
Dec 31 19:01:35 WAN: WAN connected (98.166.81.112)
Dec 31 19:01:10 Web blocking: Activated
Dec 31 19:00:57 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex)
Dec 31 19:00:53 System: Started up (7.1.2 build 1387)
Apr 29 23:17:22 System: Time synchronization fail
Apr 29 22:16:50 System: Time synchronization successful
Dec 31 19:02:13 System: Wi-Fi AP Normal Mode
Dec 31 19:01:46 WAN: WAN connected (***********)
Dec 31 19:01:19 Web blocking: Activated
Dec 31 19:01:07 Port: Port 2 status changed (link up, speed 100 Mbps Full Duplex)
Dec 31 19:01:02 System: Started up (7.1.2 build 1387)
5

@jachin99

How long the device being deployed in the network ? The problem just happen recently ? If the issue happen recently, may i know the any recent changes for the network ?

Possible please open support ticket for support team to check:
https://ticket.peplink.com/ticket/new/public

Not easy to investigate the issue by looking at the partial logs that cut out as shown in the previous logs.

1 Like
6

Thanks. I created a ticket.