cancel
Showing results for 
Search instead for 
Did you mean: 

Broadband connection keeps dropping out?

user2455
Newbie
Posts: 3
Registered: ‎24-03-2021

Broadband connection keeps dropping out?

How do I diagnose what is going on with the broadband it is affecting bother the wired computers and the wi-fi.   I have tried the usual ... restarting the router and devices but it seems to re-occur?

1. Product name:Plusnet Hub
2. Serial number:+081441+NQ93101891
3. Firmware version:Software version 4.7.5.1.83.8.263 Last updated Unknown
4. Board version:Plusnet Hub One
5. DSL uptime:0 days, 02:50:19
6. Data rate:2667 / 13079
7. Maximum data rate:2670 / 16404
8. Noise margin:6.2 / 9.4
9. Line attenuation:39.0 / 29.4
10. Signal attenuation:38.6 / 23.7

 

23. Modulation:G.993.2 Annex B
24. Software variant:AA
25. Boot loader:1.0.0

 

16:11:46, 24 Mar.BLOCKED 3 more packets (because of Packet invalid in connection)
16:11:45, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [86.189.120.146]:443-​>[80.189.45.133]:52895 on ppp3)
16:11:30, 24 Mar.BLOCKED 2 more packets (because of Packet invalid in connection)
16:11:29, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [86.189.120.146]:443-​>[80.189.45.133]:52900 on ppp3)
16:11:29, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [86.189.120.146]:443-​>[80.189.45.133]:52895 on ppp3)
16:11:21, 24 Mar.BLOCKED 3 more packets (because of Packet invalid in connection)
16:11:21, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [86.189.120.146]:443-​>[80.189.45.133]:52895 on ppp3)
16:11:17, 24 Mar.BLOCKED 3 more packets (because of Packet invalid in connection)
16:11:17, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [86.189.120.146]:443-​>[80.189.45.133]:52895 on ppp3)
16:11:15, 24 Mar.BLOCKED 3 more packets (because of Packet invalid in connection)
16:11:15, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [86.189.120.146]:443-​>[80.189.45.133]:52895 on ppp3)
16:11:11, 24 Mar.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254-​>224.0.0.22 on ptm0.101)
16:11:05, 24 Mar.IN: BLOCK [12] Spoofing protection (IGMP 80.189.45.133-​>224.0.0.22 on ppp3)
16:11:00, 24 Mar.BLOCKED 6 more packets (because of Packet invalid in connection)
16:10:59, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.0.77.32]:443-​>[80.189.45.133]:52871 on ppp3)
16:09:13, 24 Mar.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254-​>224.0.0.22 on ptm0.101)
16:09:01, 24 Mar.IN: BLOCK [12] Spoofing protection (IGMP 80.189.45.133-​>224.0.0.22 on ppp3)
16:08:56, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52813 on ppp3)
16:08:46, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [13.107.254.128]:443-​>[80.189.45.133]:52832 on ppp3)
16:08:46, 24 Mar.BLOCKED 3 more packets (because of Packet invalid in connection)
16:08:45, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [13.107.254.128]:443-​>[80.189.45.133]:52831 on ppp3)
16:08:45, 24 Mar.BLOCKED 1 more packets (because of Packet invalid in connection)
16:08:45, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [13.107.254.128]:443-​>[80.189.45.133]:52828 on ppp3)
16:08:40, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52813 on ppp3)
16:08:34, 24 Mar.OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.78]:52784-​>[216.58.212.206]:443 on ppp3)
16:08:33, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.204.14]:443-​>[80.189.45.133]:52814 on ppp3)
16:08:32, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.206.109]:443-​>[80.189.45.133]:52825 on ppp3)
16:08:32, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.206.109]:443-​>[80.189.45.133]:52824 on ppp3)
16:08:26, 24 Mar.BLOCKED 1 more packets (because of Packet invalid in connection)
16:08:25, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.204.14]:443-​>[80.189.45.133]:52814 on ppp3)
16:08:24, 24 Mar.BLOCKED 2 more packets (because of Packet invalid in connection)
16:08:23, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52812 on ppp3)
16:08:21, 24 Mar.BLOCKED 1 more packets (because of Packet invalid in connection)
16:08:20, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52812 on ppp3)
16:08:14, 24 Mar.BLOCKED 1 more packets (because of Packet invalid in connection)
16:08:13, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.198.163]:443-​>[80.189.45.133]:52807 on ppp3)
16:08:12, 24 Mar.BLOCKED 1 more packets (because of Packet invalid in connection)
16:08:11, 24 Mar.IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [86.189.120.211]:443-​>[80.189.45.133]:63650 on ppp3)
16:07:55, 24 Mar.BLOCKED 8 more packets (because of Packet invalid in connection)
16:07:54, 24 Mar.OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.78]:52775-​>[37.157.5.142]:443 on ppp3)
16:07:38, 24 Mar.OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.100]:63647-​>[2.16.14.41]:443 on ppp3)
16:07:22, 24 Mar.OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.100]:53260-​>[3.213.65.77]:443 on ppp3)
16:07:05, 24 Mar.IN: BLOCK [12] Spoofing protection (IGMP 192.168.1.254-​>224.0.0.22 on ptm0.101)
16:06:57, 24 Mar.IN: BLOCK [12] Spoofing protection (IGMP 80.189.45.133-​>224.0.0.22 on ppp3)
16:06:23, 24 Mar.( 9382.080000) Admin login successful by 192.168.1.78 on HTTP
16:06:11, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [178.250.0.163]:443-​>[80.189.45.133]:52655 on ppp3)
16:05:53, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52700 on ppp3)
16:05:37, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [178.250.0.163]:443-​>[80.189.45.133]:52655 on ppp3)
16:05:37, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52700 on ppp3)
16:05:23, 24 Mar.BLOCKED 1 more packets (because of Packet invalid in connection)
16:05:22, 24 Mar.BLOCKED 2 more packets (because of Packet invalid in connection)
16:05:21, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.210.34]:443-​>[80.189.45.133]:52697 on ppp3)
16:05:20, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [23.207.186.145]:443-​>[80.189.45.133]:52698 on ppp3)
16:05:17, 24 Mar.IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [104.244.36.20]:443-​>[80.189.45.133]:52694 on ppp3)

 

 

1 REPLY 1
Dan_the_Van
Pro
Posts: 499
Thanks: 51
Fixes: 6
Registered: ‎25-06-2007

Re: Broadband connection keeps dropping out?

I believe this to be a accidental double post, please ignore. See - 

https://community.plus.net/t5/Fibre-Broadband/Broadband-keeps-dropping-out-and-packet-invalid-in-con...

Dan