cancel
Showing results for 
Search instead for 
Did you mean: 

Internet really poor again and dropping out

prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Internet really poor again and dropping out

My internet is really poor again today and keeps dropping out.  Last time Plusnet.  Last time I went through this i plugged the hub into the test socket and it has been there ever since.  So I have the box hanging off the wall and still bad connection. Can anyone help?

 

12 REPLIES 12
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

Time and date Message
16:23:15, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64449-​>[192.229.220.133]:443 on ppp3)
16:22:38, 14 May. (2794028.100000) Admin login successful by 192.168.1.70 on HTTP
16:21:47, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:21:45, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64417-​>[104.244.46.199]:443 on ppp3)
16:21:29, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64448-​>[192.229.220.133]:443 on ppp3)
16:21:23, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64444-​>[192.229.220.133]:443 on ppp3)
16:21:11, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64446-​>[192.229.220.133]:443 on ppp3)
16:21:08, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64443-​>[192.229.220.133]:443 on ppp3)
16:21:05, 14 May. BLOCKED 49 more packets (because of Packet invalid in connection)
16:21:05, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.72]:63777-​>[54.192.2.104]:443 on ppp3)
16:21:02, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:59, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.72]:63763-​>[52.88.15.114]:443 on ppp3)
16:20:59, 14 May. BLOCKED 5 more packets (because of Packet invalid in connection)
16:20:59, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.72]:63761-​>[34.214.11.81]:443 on ppp3)
16:20:55, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:55, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63773 on ppp3)
16:20:53, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.143]:443-​>[51.9.189.170]:63775 on ppp3)
16:20:49, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [52.88.15.114]:443-​>[51.9.189.170]:63763 on ppp3)
16:20:49, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:49, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [52.88.15.114]:443-​>[51.9.189.170]:63763 on ppp3)
16:20:49, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:47, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64441-​>[104.244.46.231]:443 on ppp3)
16:20:47, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:43, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63769 on ppp3)
16:20:43, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.143]:443-​>[51.9.189.170]:63771 on ppp3)
16:20:40, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:37, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63773 on ppp3)
16:20:37, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.143]:443-​>[51.9.189.170]:63775 on ppp3)
16:20:34, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.252]:443-​>[51.9.189.170]:63768 on ppp3)
16:20:31, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:31, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:31, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63773 on ppp3)
16:20:28, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:28, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63769 on ppp3)
16:20:28, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:26, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.252]:443-​>[51.9.189.170]:63776 on ppp3)
16:20:25, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:25, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:23, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:23, 14 May. BLOCKED 3 more packets (because of Packet invalid in connection)
16:20:19, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:17, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:17, 14 May. BLOCKED 3 more packets (because of Packet invalid in connection)
16:20:16, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:13, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63765 on ppp3)
16:20:13, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:13, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.124]:443-​>[51.9.189.170]:60532 on ppp3)
16:20:12, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [159.253.128.183]:443-​>[51.9.189.170]:60557 on ppp3)
16:20:12, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:12, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.21]:443-​>[51.9.189.170]:60507 on ppp3)
16:20:12, 14 May. BLOCKED 3 more packets (because of Packet invalid in connection)
16:20:12, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.138]:443-​>[51.9.189.170]:63770 on ppp3)
16:20:12, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:09, 14 May. (2793879.490000) New GUI session from IP 192.168.1.70
16:20:08, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.124]:443-​>[51.9.189.170]:60532 on ppp3)
16:20:08, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:08, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.138]:443-​>[51.9.189.170]:63770 on ppp3)
16:20:08, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:06, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.124]:443-​>[51.9.189.170]:60532 on ppp3)
16:20:06, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.252]:443-​>[51.9.189.170]:63768 on ppp3)
16:20:06, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:20:05, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [151.101.18.49]:443-​>[51.9.189.170]:60486 on ppp3)
16:20:05, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:04, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [204.79.197.200]:443-​>[51.9.189.170]:60503 on ppp3)
16:20:04, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:20:03, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [151.101.18.49]:443-​>[51.9.189.170]:60486 on ppp3)
16:20:01, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.104]:443-​>[51.9.189.170]:63765 on ppp3)
16:20:00, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:19:59, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.138]:443-​>[51.9.189.170]:63766 on ppp3)
16:19:58, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.162]:443-​>[51.9.189.170]:60341 on ppp3)
16:19:57, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.138]:443-​>[51.9.189.170]:63766 on ppp3)
16:19:54, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64422-​>[192.229.233.50]:443 on ppp3)
16:19:53, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.162]:443-​>[51.9.189.170]:60341 on ppp3)
16:19:47, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [34.214.11.81]:443-​>[51.9.189.170]:63761 on ppp3)
16:19:47, 14 May. BLOCKED 4 more packets (because of Packet invalid in connection)
16:19:47, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [34.214.11.81]:443-​>[51.9.189.170]:63761 on ppp3)
16:19:47, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:19:46, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [34.214.11.81]:443-​>[51.9.189.170]:63761 on ppp3)
16:19:40, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
16:19:30, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
16:19:18, 14 May. BLOCKED 5 more packets (because of Packet invalid in connection)
16:19:17, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.65]:64437-​>[17.250.13.5]:443 on ppp3)
16:19:17, 14 May. OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.65]:64437-​>[17.250.13.5]:443 on ppp3)
16:19:16, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64434-​>[104.244.46.39]:443 on ppp3)
16:19:11, 14 May. IN: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:19:11, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:19:10, 14 May. IN: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:19:01, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:19:00, 14 May. IN: BLOCK [16] Remote administration (TCP [187.214.7.181]:59482-​>[51.9.189.170]:8080 on ppp3)
16:18:59, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:18:46, 14 May. IN: BLOCK [16] Remote administration (TCP [187.192.131.150]:64306-​>[51.9.189.170]:8080 on ppp3)
16:18:43, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64433-​>[104.244.46.39]:443 on ppp3)
16:18:43, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64430-​>[104.244.46.39]:443 on ppp3)
16:18:30, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:60285-​>[52.50.113.158]:443 on ppp3)
16:18:10, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64411-​>[104.244.46.39]:443 on ppp3)
16:17:58, 14 May. IN: BLOCK [16] Remote administration (TCP [187.175.45.148]:54372-​>[51.9.189.170]:8080 on ppp3)
16:17:57, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:17:56, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64412-​>[104.244.46.39]:443 on ppp3)
16:17:46, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.239.36.126]:443-​>[51.9.189.170]:64418 on ppp3)
16:16:19, 14 May. OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.79]:37090-​>[52.94.229.76]:443 on ppp3)
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

16:19:11, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:19:10, 14 May. IN: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:19:01, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:19:00, 14 May. IN: BLOCK [16] Remote administration (TCP [187.214.7.181]:59482-​>[51.9.189.170]:8080 on ppp3)
16:18:59, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [17.250.13.5]:443-​>[51.9.189.170]:64437 on ppp3)
16:18:46, 14 May. IN: BLOCK [16] Remote administration (TCP [187.192.131.150]:64306-​>[51.9.189.170]:8080 on ppp3)
16:18:43, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64433-​>[104.244.46.39]:443 on ppp3)
16:18:43, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64430-​>[104.244.46.39]:443 on ppp3)
16:18:30, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:60285-​>[52.50.113.158]:443 on ppp3)
16:18:10, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64411-​>[104.244.46.39]:443 on ppp3)
16:17:58, 14 May. IN: BLOCK [16] Remote administration (TCP [187.175.45.148]:54372-​>[51.9.189.170]:8080 on ppp3)
16:17:57, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:17:56, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64412-​>[104.244.46.39]:443 on ppp3)
16:17:46, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.239.36.126]:443-​>[51.9.189.170]:64418 on ppp3)
16:16:19, 14 May. OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.79]:37090-​>[52.94.229.76]:443 on ppp3)
16:16:05, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [17.248.144.50]:443-​>[51.9.189.170]:60183 on ppp3)
16:15:47, 14 May. BLOCKED 3 more packets (because of Packet invalid in connection)
16:15:47, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [54.69.196.30]:443-​>[51.9.189.170]:63757 on ppp3)
16:15:16, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [54.192.2.147]:443-​>[51.9.189.170]:60209 on ppp3)
16:12:47, 14 May. BLOCKED 3 more packets (because of Packet invalid in connection)
16:12:46, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [52.88.15.114]:443-​>[51.9.189.170]:63753 on ppp3)
16:12:41, 14 May. IN: BLOCK [16] Remote administration (TCP [189.163.105.117]:42594-​>[51.9.189.170]:8080 on ppp3)
16:12:18, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [54.230.0.148]:443-​>[51.9.189.170]:63750 on ppp3)
16:11:19, 14 May. OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.79]:35079-​>[52.94.232.206]:443 on ppp3)
16:11:15, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
16:11:05, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
16:09:47, 14 May. BLOCKED 3 more packets (because of Packet invalid in connection)
16:09:46, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [54.187.55.149]:443-​>[51.9.189.170]:63746 on ppp3)
16:09:22, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [74.125.100.135]:443-​>[51.9.189.170]:53013 on ppp3)
16:09:02, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:09:00, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.67]:52913-​>[216.58.201.42]:443 on ppp3)
16:08:45, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [184.28.56.45]:443-​>[51.9.189.170]:60027 on ppp3)
16:08:14, 14 May. IN: BLOCK [16] Remote administration (TCP [178.94.18.238]:24912-​>[51.9.189.170]:8080 on ppp3)
16:06:19, 14 May. OUT: BLOCK [65] First packet is Invalid (Packet not in tcp window: TCP [192.168.1.79]:60715-​>[52.46.156.47]:443 on ppp3)
16:04:37, 14 May. IN: BLOCK [16] Remote administration (TCP [179.111.3.168]:49693-​>[51.9.189.170]:8080 on ppp3)
16:04:23, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 88.221.135.222-​>51.9.189.170 on ppp3)
16:04:19, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 2.16.170.54-​>51.9.189.170 on ppp3)
16:04:13, 14 May. BLOCKED 1 more packets (because of Remote administration)
16:04:12, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 80.239.216.76-​>51.9.189.170 on ppp3)
16:04:11, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 23.3.15.50-​>51.9.189.170 on ppp3)
16:04:06, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 213.123.252.78-​>51.9.189.170 on ppp3)
16:04:01, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 109.144.2.183-​>51.9.189.170 on ppp3)
16:03:57, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 92.122.153.70-​>51.9.189.170 on ppp3)
16:03:42, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 213.123.255.53-​>51.9.189.170 on ppp3)
16:03:22, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 88.221.135.222-​>51.9.189.170 on ppp3)
16:03:20, 14 May. (2792870.150000) Lease for IP 192.168.1.70 renewed by host Lisa (MAC c0:38:96:4f:2c:43). Lease duration: 1440 min
16:03:20, 14 May. (2792870.150000) Device connected: Hostname: Lisa IP: 192.168.1.70 MAC: c0:38:96:4f:2c:43 Lease time: 1440 min. Link rate: 71.3 Mbps
16:03:20, 14 May. (2792869.960000) Lease requested
16:03:19, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 2.16.170.54-​>51.9.189.170 on ppp3)
16:03:19, 14 May. ath00: STA c0:38:96:4f:2c:43 IEEE 802.11: Client associated
16:03:15, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
16:03:13, 14 May. BLOCKED 1 more packets (because of Remote administration)
16:03:12, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 80.239.216.76-​>51.9.189.170 on ppp3)
16:03:11, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 23.3.15.50-​>51.9.189.170 on ppp3)
16:03:06, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 213.123.252.78-​>51.9.189.170 on ppp3)
16:03:05, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
16:03:00, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 109.144.2.183-​>51.9.189.170 on ppp3)
16:02:57, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 92.122.153.70-​>51.9.189.170 on ppp3)
16:02:48, 14 May. BLOCKED 16 more packets (because of Packet invalid in connection)
16:02:47, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.72]:63716-​>[54.192.2.138]:443 on ppp3)
16:02:43, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.213.78]:443-​>[51.9.189.170]:52846 on ppp3)
16:02:42, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 213.123.255.53-​>51.9.189.170 on ppp3)
16:02:22, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 88.221.135.222-​>51.9.189.170 on ppp3)
16:02:22, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [17.250.13.5]:443-​>[51.9.189.170]:64376 on ppp3)
16:02:19, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 2.16.170.54-​>51.9.189.170 on ppp3)
16:02:19, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:02:17, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [172.217.23.10]:443-​>[51.9.189.170]:52832 on ppp3)
16:02:13, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 80.239.216.76-​>51.9.189.170 on ppp3)
16:02:12, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 23.55.59.174-​>51.9.189.170 on ppp3)
16:02:11, 14 May. IN: BLOCK [16] Remote administration (ICMP type 8 code 0 23.3.15.50-​>51.9.189.170 on ppp3)
16:01:52, 14 May. IN: BLOCK [16] Remote administration (TCP [109.248.9.9]:57311-​>[51.9.189.170]:22 on ppp3)
16:01:50, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.198.97]:443-​>[51.9.189.170]:52823 on ppp3)
16:01:48, 14 May. IN: BLOCK [16] Remote administration (TCP [109.248.9.9]:57311-​>[51.9.189.170]:22 on ppp3)
16:01:47, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
16:01:47, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.210.52]:443-​>[51.9.189.170]:64380 on ppp3)
16:01:45, 14 May. IN: BLOCK [16] Remote administration (TCP [109.248.9.9]:57311-​>[51.9.189.170]:22 on ppp3)
16:00:49, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp packet flags: TCP [192.168.1.65]:64371-​>[52.85.68.21]:443 on ppp3)
16:00:47, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
16:00:47, 14 May. IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [52.42.67.204]:443-​>[51.9.189.170]:63730 on ppp3)
15:59:16, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp packet flags: TCP [192.168.1.65]:64371-​>[52.85.68.21]:443 on ppp3)
15:58:44, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [52.85.68.21]:443-​>[51.9.189.170]:64371 on ppp3)
15:58:42, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [172.217.23.34]:443-​>[51.9.189.170]:52750 on ppp3)
15:58:28, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [52.85.68.21]:443-​>[51.9.189.170]:64371 on ppp3)
15:58:21, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp packet flags: TCP [192.168.1.65]:64371-​>[52.85.68.21]:443 on ppp3)
15:58:20, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [52.85.68.21]:443-​>[51.9.189.170]:64371 on ppp3)
15:58:17, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp packet flags: TCP [192.168.1.65]:64371-​>[52.85.68.21]:443 on ppp3)
15:58:16, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [52.85.68.21]:443-​>[51.9.189.170]:64371 on ppp3)
15:58:15, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp packet flags: TCP [192.168.1.65]:64371-​>[52.85.68.21]:443 on ppp3)
15:58:15, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
15:58:13, 14 May. IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [52.85.68.21]:443-​>[51.9.189.170]:64371 on ppp3)
15:58:13, 14 May. BLOCKED 2 more packets (because of Packet invalid in connection)
15:58:12, 14 May. OUT: BLOCK [9] Packet invalid in connection (Invalid tcp packet flags: TCP [192.168.1.65]:64371-​>[52.85.68.21]:443 on ppp3)
15:57:27, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:57:17, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:56:45, 14 May. BLOCKED 1 more packets (because of Packet invalid in connection)
15:56:45, 14 May. OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.65]:64362-​>[151.101.17.140]:443 on ppp3)
15:51:26, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:51:16, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:49:42, 14 May. (2792052.600000) Lease for IP 192.168.1.79 renewed by host amazon-​6931b0cf0 (MAC 38:f7:3d:c4:e9:85). Lease duration: 1440 min
15:49:42, 14 May. (2792052.600000) Device connected: Hostname: amazon-​6931b0cf0 IP: 192.168.1.79 MAC: 38:f7:3d:c4:e9:85 Lease time: 1440 min. Link rate: 11.0 Mbps
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

15:49:42, 14 May. (2792052.470000) Lease requested
15:45:27, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:45:17, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:39:42, 14 May. (2791452.650000) Lease for IP 192.168.1.67 renewed by host iPad (MAC fc:fc:48:3c:03:30). Lease duration: 1440 min
15:39:42, 14 May. (2791452.650000) Device connected: Hostname: iPad IP: 192.168.1.67 MAC: fc:fc:48:3c:03:30 Lease time: 1440 min. Link rate: 104.0 Mbps
15:39:42, 14 May. (2791452.590000) Lease requested
15:39:42, 14 May. (2791452.240000) Lease for IP 192.168.1.67 renewed by host iPad (MAC fc:fc:48:3c:03:30). Lease duration: 1440 min
15:39:42, 14 May. (2791452.240000) Device connected: Hostname: iPad IP: 192.168.1.67 MAC: fc:fc:48:3c:03:30 Lease time: 1440 min. Link rate: 11.0 Mbps
15:39:42, 14 May. (2791452.170000) Lease requested
15:39:41, 14 May. ath00: STA fc:fc:48:3c:03:30 IEEE 802.11: Client associated
15:39:41, 14 May. ath00: STA fc:fc:48:3c:03:30 IEEE 802.11: Client disassociated
15:38:29, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:38:19, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:38:06, 14 May. ath10: STA 6c:94:f8:af:fc:f8 IEEE 802.11: WiFi registration failed
15:38:02, 14 May. (2791352.450000) Device disconnected: Hostname: iPad IP: 192.168.1.67 MAC: fc:fc:48:3c:03:30
15:38:00, 14 May. ath00: STA fc:fc:48:3c:03:30 IEEE 802.11: Client disassociated
15:37:34, 14 May. (2791324.260000) Host Lisas-​iPad-​2 (MAC 6c:94:f8:af:fc:f8) using IP 192.168.1.72 detected on interface ath00, port -​1
15:37:33, 14 May. ath00: STA 6c:94:f8:af:fc:f8 IEEE 802.11: Client associated
15:37:33, 14 May. ath00: STA 6c:94:f8:af:fc:f8 IEEE 802.11: Client disassociated
15:34:24, 14 May. (2791134.260000) Host Lisas-​iPad-​2 (MAC 6c:94:f8:af:fc:f8) using IP 192.168.1.72 detected on interface ath10, port -​1
15:34:16, 14 May. ath10: STA 6c:94:f8:af:fc:f8 IEEE 802.11: Client associated
15:31:14, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:31:04, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:18:35, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:18:25, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:13:15, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:13:05, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:10:01, 14 May. (2789671.730000) Lease for IP 192.168.1.75 renewed by host Unknown-​22-​a3-​f6-​b2-​ac-​b2 (MAC 22:a3:f6:b2:ac:b2). Lease duration: 1440 min
15:10:01, 14 May. (2789671.730000) Device connected: Hostname: Unknown-​22-​a3-​f6-​b2-​ac-​b2 IP: 192.168.1.75 MAC: 22:a3:f6:b2:ac:b2 Lease time: 1440 min. Link rate: 144.3 Mbps
15:10:01, 14 May. (2789671.650000) Lease requested
15:07:22, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:07:12, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
15:07:07, 14 May. (2789497.340000) Device disconnected: Hostname: Lisa IP: 192.168.1.70 MAC: c0:38:96:4f:2c:43
15:07:03, 14 May. ath00: STA c0:38:96:4f:2c:43 IEEE 802.11: Client disassociated
15:01:22, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
15:01:12, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:59:06, 14 May. (2789016.870000) Lease for IP 192.168.1.72 renewed by host Lisas-​iPad-​2 (MAC 6c:94:f8:af:fc:f8). Lease duration: 1440 min
14:59:06, 14 May. (2789016.870000) Device connected: Hostname: Lisas-​iPad-​2 IP: 192.168.1.72 MAC: 6c:94:f8:af:fc:f8 Lease time: 1440 min. Link rate: 78.0 Mbps
14:59:06, 14 May. (2789016.790000) Lease requested
14:59:06, 14 May. ath00: STA 6c:94:f8:af:fc:f8 IEEE 802.11: Client associated
14:53:21, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
14:53:11, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:48:40, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: Client associated
14:48:12, 14 May. (2788362.240000) Device disconnected: Hostname: XboxOne IP: 192.168.1.68 MAC: 30:59:b7:e3:46:c3
14:48:07, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: Client disassociated
14:48:07, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: WiFi registration failed
14:47:53, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
14:47:43, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:42:26, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
14:42:16, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:37:07, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
14:36:57, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:27:17, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
14:27:07, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:25:47, 14 May. (2787017.210000) Device disconnected: Hostname: COM-​MID1 IP: 192.168.1.82 MAC: 48:a9:d2:75:8c:ea
14:25:42, 14 May. ath00: STA 48:a9:d2:75:8c:ea IEEE 802.11: Client disassociated
14:25:22, 14 May. (2786992.210000) Lease for IP 192.168.1.73 renewed by host JamesPC (MAC 74:29:af:07:11:7f). Lease duration: 1440 min
14:25:22, 14 May. (2786992.210000) Device connected: Hostname: JamesPC IP: 192.168.1.73 MAC: 74:29:af:07:11:7f Lease time: 1440 min. Link rate: 54.7 Mbps
14:25:22, 14 May. (2786992.110000) Lease requested
14:25:22, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client associated
14:25:22, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client disassociated
14:25:06, 14 May. (2786976.600000) Lease for IP 192.168.1.82 renewed by host COM-​MID1 (MAC 48:a9:d2:75:8c:ea). Lease duration: 1440 min
14:25:06, 14 May. (2786976.600000) Device connected: Hostname: COM-​MID1 IP: 192.168.1.82 MAC: 48:a9:d2:75:8c:ea Lease time: 1440 min. Link rate: 11.0 Mbps
14:25:06, 14 May. (2786976.500000) Lease requested
14:25:05, 14 May. ath00: STA 48:a9:d2:75:8c:ea IEEE 802.11: Client associated
14:25:05, 14 May. ath00: STA 48:a9:d2:75:8c:ea IEEE 802.11: Client disassociated
14:24:56, 14 May. ath00: STA 58:82:a8:13:60:47 IEEE 802.11: Client associated
14:24:56, 14 May. ath00: STA 58:82:a8:13:60:47 IEEE 802.11: Client disassociated
14:24:56, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: Client associated
14:24:56, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: Client disassociated
14:24:52, 14 May. (2786962.820000) Lease for IP 192.168.1.73 renewed by host JamesPC (MAC 74:29:af:07:11:7f). Lease duration: 1440 min
14:24:52, 14 May. (2786962.820000) Device connected: Hostname: JamesPC IP: 192.168.1.73 MAC: 74:29:af:07:11:7f Lease time: 1440 min. Link rate: 56.2 Mbps
14:24:52, 14 May. (2786962.730000) Lease requested
14:24:52, 14 May. ath00: STA 22:a3:f6:b2:ac:b2 IEEE 802.11: Client associated
14:24:52, 14 May. ath00: STA 22:a3:f6:b2:ac:b2 IEEE 802.11: Client disassociated
14:24:52, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client associated
14:24:52, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client disassociated
14:24:43, 14 May. ath00: STA 58:82:a8:13:60:47 IEEE 802.11: Client associated
14:24:43, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: Client associated
14:24:43, 14 May. ath00: STA 30:59:b7:e3:46:c3 IEEE 802.11: Client disassociated
14:24:40, 14 May. (2786949.930000) Lease for IP 192.168.1.73 renewed by host JamesPC (MAC 74:29:af:07:11:7f). Lease duration: 1440 min
14:24:40, 14 May. (2786949.930000) Device connected: Hostname: JamesPC IP: 192.168.1.73 MAC: 74:29:af:07:11:7f Lease time: 1440 min. Link rate: 67.7 Mbps
14:24:40, 14 May. ath00: STA 22:a3:f6:b2:ac:b2 IEEE 802.11: Client associated
14:24:40, 14 May. ath00: STA 22:a3:f6:b2:ac:b2 IEEE 802.11: Client disassociated
14:24:39, 14 May. (2786949.820000) Lease requested
14:24:39, 14 May. (2786949.370000) Device disconnected: Hostname: XboxOne IP: 192.168.1.81 MAC: 58:82:a8:13:60:47
14:24:39, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client associated
14:24:39, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client disassociated
14:24:39, 14 May. ath00: STA 58:82:a8:13:60:47 IEEE 802.11: Client disassociated
14:24:18, 14 May. (2786928.880000) Lease for IP 192.168.1.73 renewed by host JamesPC (MAC 74:29:af:07:11:7f). Lease duration: 1440 min
14:24:18, 14 May. (2786928.880000) Device connected: Hostname: JamesPC IP: 192.168.1.73 MAC: 74:29:af:07:11:7f Lease time: 1440 min. Link rate: 52.0 Mbps
14:24:18, 14 May. (2786928.800000) Lease requested
14:24:18, 14 May. ath00: STA 74:29:af:07:11:7f IEEE 802.11: Client associated
14:23:39, 14 May. (2786889.570000) Lease for IP 192.168.1.82 renewed by host COM-​MID1 (MAC 48:a9:d2:75:8c:ea). Lease duration: 1440 min
14:23:39, 14 May. (2786889.570000) Device connected: Hostname: COM-​MID1 IP: 192.168.1.82 MAC: 48:a9:d2:75:8c:ea Lease time: 1440 min. Link rate: 84.1 Mbps
14:23:39, 14 May. (2786889.420000) Lease requested
14:23:39, 14 May. ath00: STA 48:a9:d2:75:8c:ea IEEE 802.11: Client associated
14:21:16, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client disassociated
14:21:06, 14 May. ath10: STA 88:75:98:64:4c:85 IEEE 802.11: Client associated
14:19:31, 14 May. (2786641.710000) Lease for IP 192.168.1.70 renewed by host Lisa (MAC c0:38:96:4f:2c:43). Lease duration: 1440 min
EmilyD
Plusnet Help Team
Plusnet Help Team
Posts: 2,032
Thanks: 357
Fixes: 117
Registered: ‎26-03-2018

Re: Internet really poor again and dropping out

Hi @prettyinpink,

 

I'm sorry to hear that you're experiencing drops in your connection. Thank you for confirming that you're currently connected to the test socket.

 

I've tested your line today, however the test hasn't picked up the cause of this issue. For reference, today's test result is as follows:

GEA Test Detail
Circuit ID   Service ID BBEU274XXXXX
 
 
Test Outcome Pass
Test Outcome Code GTC_FTTC_SERVICE_0000
Description GEA service test completed and no fault found .
Main Fault Location OK
Sync Status In Sync
Downstream Speed 38.2 Mbps
Upstream Speed 7.4 Mbps
Appointment Required N
Fault Report Advised N
NTE Power Status PowerOn
Voice Line Test Result Pass
Bridge Tap Not Detected
Radio Frequency Ingress Not Detected
Repetitive Electrical Impulse Noise Not Detected
Cross Talk Not Detected
Estimated Line Length In Metres 910.1
Upstream Rate Assessment Very Good
Downstream Rate Assessment Reasonable
Interference Pattern Regular Interference Observed Daily
Service Impact No Impact Observed
Interference Duration Longest Occurrence From 04:45 to 01:30
Interference Location Customer Premise
Interference Observed In Days 14
Home Wiring Problem Not Detected
Downstream Policing Discard Rate 0.0
Customer Traffic Level Upstream and Downstream Traffic Detected
Technology VDSL
Profile Name 0.128M-80M Downstream, Interleaving Low - 0.128M-20M Upstream, Error Protection Off
Time Stamp 2018-05-01T17:15:00
Parameters MIN MAX AVG
Down Stream Line Rate 38.1 Mbps 38.1 Mbps 38.1 Mbps
Up Stream Line Rate 7.3 Mbps 7.3 Mbps 7.3 Mbps
Up Time 900.0 Sec 900.0 Sec 900.0 Sec
Retrains 0.0 0.0 0.0
Current and Last 15 Minute Bin Performance
Parameters Last Traffic Count(Upto 15 mins) Current Traffic Count(Upto 15 mins)
Start Time Stamp 2018-05-14T16:46:05.642+01:00 2018-05-14T17:01:05.642+01:00
Ingress Code Violation 0 0
Egress Code Violation 0 0
Errored Seconds 0 0
Severely Errored Seconds 0 0
Unavailable Seconds 0 0
Our radius hasn't picked up any drops in connection within the last 30 days:
  
Does the light on the front of your router change when your connection drops? If so, please can you advise what changes you see to the light when the connection drops?
 

 

 

If this post resolved your issue please click the 'This fixed my problem' button
 Emily D
 Plusnet Help Team
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

The router is in the bedroom and I m downstairs so I have noticed if the lights change. Sorry!

MatthewWheeler
Plusnet Help Team
Plusnet Help Team
Posts: 8,896
Thanks: 1,506
Fixes: 480
Registered: ‎01-01-2012

Re: Internet really poor again and dropping out

Can you give us more information about when the connection drops?

Do you get a particular error and in addition are you connecting over wireless or a wired connection?

If this post resolved your issue please click the 'This fixed my problem' button
 Matthew Wheeler
 Plusnet Help Team
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

It happens randomly all the time.  Web pages just freeze on loading or run really slowly.  With my phone I am having to turn wifi off and use my data.  We connect over wifi.  I am concerned that I have the box hanging off the wall where the line comes in and on my log it shows tcp attack reset. Today it has been a little better.  Just getting very frustrated.  It works for a few days and then slows right down

 

MatthewWheeler
Plusnet Help Team
Plusnet Help Team
Posts: 8,896
Thanks: 1,506
Fixes: 480
Registered: ‎01-01-2012

Re: Internet really poor again and dropping out

I've read through the logs and there's nothing jumping out that would concern me.

The majority of them refer to your wireless devices disconnecting then reconnecting so it may be a issue with the signal.

We'd recommend going through the steps here to boost this

If this post resolved your issue please click the 'This fixed my problem' button
 Matthew Wheeler
 Plusnet Help Team
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

Ok I will take a look at the help section.  In the meantime is it down to me to replace the socket that appears to be faulty? I do not want to use the test socket permanately. 

 

adamwalker
Plusnet Help Team
Plusnet Help Team
Posts: 16,871
Thanks: 882
Fixes: 221
Registered: ‎27-04-2007

Re: Internet really poor again and dropping out

Hi there, 

 

Officially we'd need to arrange that to be done via an engineer visit. 

If this post resolved your issue please click the 'This fixed my problem' button
 Adam Walker
 Plusnet Help Team
prettyinpink
Dabbler
Posts: 21
Registered: ‎19-02-2018

Re: Internet really poor again and dropping out

Hi how can I get that arranged? Will i be liable for the cost?

 

Townman
Superuser
Superuser
Posts: 22,922
Thanks: 9,538
Fixes: 158
Registered: ‎22-08-2007

Re: Internet really poor again and dropping out

Why do you think the socket is faulty? Using the test socket eliminates the possibility that internal gives rise to problems.

I note that the test results refer to internal interference on customers premises ... are those claims from BTw testing reliable?

There is a difference between sluggish responses and disconnections. The evidence provided by PlusNET does not indicate a connection failure between the router and the exchange, but that does not rule out issues with WiFi due to your local environment.

Which router do you use?
What phones / pc are you using?
This somewhat feels like a WiFi connectivity issue - do you live in an area of dense housing?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.