Losing connection

sullys666 · ‎07-04-2016

My wife and son have been experiencing loss of wi-fi on their phones and also on my son's pc (which connects via wifi as cabling would be messy and expensive.

I have looked on the Event Log and this is what i see. Not able to make any real sense of it. Hopefully someone on the team can. I've not experienced any noticable loss of connection myself

Event Log

This page summarises all the recent events that have been recorded on your Plusnet Hub.

You can filter the events to show items related to a specific category.

Recorded events

Time and date	Message
19:47:02, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:47:01, 25 May.	(5031895.420000) Device disconnected: Hostname: XboxOne IP: 192.168.1.70 MAC: 30:59:b7:8c:70:59
19:47:01, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:47:01, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:47:00, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:47:00, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:46:55, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [157.240.221.16]:443->[80.229.225.85]:60723 on ppp3)
19:46:50, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:46:49, 25 May.	(5031883.080000) Device disconnected: Hostname: XboxOne IP: 192.168.1.70 MAC: 30:59:b7:8c:70:59
19:46:49, 25 May.	BLOCKED 2 more packets (because of Packet invalid in connection)
19:46:49, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:46:48, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:46:48, 25 May.	IN: ACCEPT [57] Connection closed (Port Forwarding: UDP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [118.210.3.234]:52745 ppp3 NAPT)
19:46:48, 25 May.	IN: ACCEPT [57] Connection closed (Port Forwarding: TCP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [65.130.61.154]:36837 SYN_RECV/SYN_SENT ppp3 NAPT)
19:46:43, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [157.240.221.16]:443->[80.229.225.85]:60722 on ppp3)
19:46:43, 25 May.	IN: ACCEPT [54] Connection opened (Port Forwarding: TCP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [65.130.61.154]:36837 CLOSED/SYN_SENT ppp3 NAPT)
19:46:43, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:46:41, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [157.240.221.16]:443->[80.229.225.85]:60722 on ppp3)
19:46:39, 25 May.	IN: ACCEPT [57] Connection closed (Port Forwarding: TCP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [99.244.180.36]:21903 TIME_WAIT/CLOSED ppp3 NAPT)
19:46:39, 25 May.	IN: ACCEPT [54] Connection opened (Port Forwarding: TCP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [99.244.180.36]:21903 CLOSED/SYN_SENT ppp3 NAPT)
19:46:37, 25 May.	(5031870.850000) Lease for IP 192.168.1.74 renewed by host DANIELSPC (MAC d4:3b:04:fd:cd:84). Lease duration: 1440 min
19:46:37, 25 May.	(5031870.850000) Device connected: Hostname: DANIELSPC IP: 192.168.1.74 MAC: d4:3b:04:fd:cd:84 Lease time: 1440 min. Link rate: 54.1 Mbps
19:46:37, 25 May.	(5031870.760000) Lease requested
19:46:37, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:46:37, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:46:30, 25 May.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.76]:49222->[34.251.180.54]:443 on ppp3)
19:46:30, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:46:30, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:46:17, 25 May.	(5031851.120000) Lease for IP 192.168.1.74 renewed by host DANIELSPC (MAC d4:3b:04:fd:cd:84). Lease duration: 1440 min
19:46:17, 25 May.	(5031851.120000) Device connected: Hostname: DANIELSPC IP: 192.168.1.74 MAC: d4:3b:04:fd:cd:84 Lease time: 1440 min. Link rate: 55.0 Mbps
19:46:17, 25 May.	(5031851.020000) Lease requested
19:46:17, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:46:17, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:46:11, 25 May.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [45.173.28.32]:47514 ppp3 NAPT)
19:46:11, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:46:11, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:45:45, 25 May.	(5031819.330000) Lease for IP 192.168.1.74 renewed by host DANIELSPC (MAC d4:3b:04:fd:cd:84). Lease duration: 1440 min
19:45:45, 25 May.	(5031819.330000) Device connected: Hostname: DANIELSPC IP: 192.168.1.74 MAC: d4:3b:04:fd:cd:84 Lease time: 1440 min. Link rate: 53.5 Mbps
19:45:45, 25 May.	(5031819.230000) Lease requested
19:45:45, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:45:45, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:45:41, 25 May.	BLOCKED 3 more packets (because of Packet invalid in connection)
19:45:41, 25 May.	IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [104.120.212.26]:443->[80.229.225.85]:62499 on ppp3)
19:45:41, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:45:39, 25 May.	IN: ACCEPT [57] Connection closed (Port Forwarding: TCP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [99.244.180.36]:21467 TIME_WAIT/CLOSED ppp3 NAPT)
19:45:39, 25 May.	IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [23.62.3.42]:443->[80.229.225.85]:62511 on ppp3)
19:45:38, 25 May.	IN: ACCEPT [54] Connection opened (Port Forwarding: TCP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [99.244.180.36]:21467 CLOSED/SYN_SENT ppp3 NAPT)
19:45:38, 25 May.	IN: ACCEPT [54] Connection opened (Port Forwarding: UDP [192.168.1.64]:57359 <--> [80.229.225.85]:57359 - - - [71.83.74.135]:60120 ppp3 NAPT)
19:45:36, 25 May.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.69]:62549->[104.120.213.27]:443 on ppp3)
19:45:31, 25 May.	BLOCKED 4 more packets (because of Packet invalid in connection)
19:45:31, 25 May.	IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [23.62.3.42]:443->[80.229.225.85]:62464 on ppp3)
19:45:26, 25 May.	IN: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [17.188.164.156]:443->[80.229.225.85]:62572 on ppp3)
19:45:25, 25 May.	(5031799.350000) Lease for IP 192.168.1.74 renewed by host DANIELSPC (MAC d4:3b:04:fd:cd:84). Lease duration: 1440 min
19:45:25, 25 May.	(5031799.350000) Device connected: Hostname: DANIELSPC IP: 192.168.1.74 MAC: d4:3b:04:fd:cd:84 Lease time: 1440 min. Link rate: 52.8 Mbps
19:45:25, 25 May.	(5031799.260000) Lease requested
19:45:25, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:45:25, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:45:23, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:45:23, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:45:23, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:45:22, 25 May.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.69]:62460->[104.120.213.27]:443 on ppp3)
19:45:21, 25 May.	OUT: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [192.168.1.70]:52398->[40.90.10.180]:443 on ppp3)
19:45:21, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [74.125.100.73]:443->[80.229.225.85]:52496 on ppp3)
19:45:15, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [104.120.212.26]:443->[80.229.225.85]:62499 on ppp3)
19:45:15, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:45:15, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:45:13, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:45:13, 25 May.	OUT: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:52398->[40.90.10.180]:443 on ppp3)
19:45:07, 25 May.	(5031780.820000) Lease for IP 192.168.1.74 renewed by host DANIELSPC (MAC d4:3b:04:fd:cd:84). Lease duration: 1440 min
19:45:07, 25 May.	(5031780.820000) Device connected: Hostname: DANIELSPC IP: 192.168.1.74 MAC: d4:3b:04:fd:cd:84 Lease time: 1440 min. Link rate: 53.5 Mbps
19:45:07, 25 May.	(5031780.730000) Lease requested
19:45:07, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:45:07, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:45:06, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [104.120.212.26]:443->[80.229.225.85]:62499 on ppp3)
19:45:03, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:45:02, 25 May.	OUT: BLOCK [65] First packet is Invalid (Invalid tcp flags for current tcp state: TCP [192.168.1.70]:52398->[40.90.10.180]:443 on ppp3)
19:45:02, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [104.120.212.26]:443->[80.229.225.85]:62499 on ppp3)
19:45:02, 25 May.	BLOCKED 2 more packets (because of Packet invalid in connection)
19:45:01, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [216.58.204.34]:443->[80.229.225.85]:62547 on ppp3)
19:45:01, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:45:00, 25 May.	(5031774.000000) Admin login successful by 192.168.1.64 on HTTP
19:45:00, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags SYN inside connection: TCP [104.120.212.26]:443->[80.229.225.85]:62483 on ppp3)
19:45:00, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:45:00, 25 May.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.69]:62479->[17.248.144.211]:443 on ppp3)
19:45:00, 25 May.	BLOCKED 12 more packets (because of Packet invalid in connection)
19:45:00, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client associated
19:45:00, 25 May.	ath00: STA 30:59:b7:8c:70:59 IEEE 802.11: Client disassociated
19:44:58, 25 May.	BLOCKED 2 more packets (because of Packet invalid in connection)
19:44:58, 25 May.	IN: BLOCK [9] Packet invalid in connection (Invalid tcp flags for current tcp state: TCP [104.120.212.26]:443->[80.229.225.85]:62488 on ppp3)
19:44:53, 25 May.	IN: BLOCK [9] Packet invalid in connection (Packet not in tcp window: TCP [104.120.212.26]:443->[80.229.225.85]:62483 on ppp3)
19:44:53, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:44:52, 25 May.	(5031766.550000) Lease for IP 192.168.1.74 renewed by host DANIELSPC (MAC d4:3b:04:fd:cd:84). Lease duration: 1440 min
19:44:52, 25 May.	(5031766.550000) Device connected: Hostname: DANIELSPC IP: 192.168.1.74 MAC: d4:3b:04:fd:cd:84 Lease time: 1440 min. Link rate: 55.0 Mbps
19:44:52, 25 May.	(5031766.410000) Lease requested
19:44:52, 25 May.	BLOCKED 3 more packets (because of Packet invalid in connection)
19:44:52, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client associated
19:44:52, 25 May.	ath00: STA d4:3b:04:fd:cd:84 IEEE 802.11: Client disassociated
19:44:51, 25 May.	OUT: BLOCK [9] Packet invalid in connection (tcp reset attack is suspected: TCP [192.168.1.69]:62447->[17.253.35.208]:443 on ppp3)
19:44:51, 25 May.	BLOCKED 1 more packets (because of Packet invalid in connection)
19:44:50, 25 May.	BLOCKED 6 more packets (because of Packet invalid in connection)

sullys666 · ‎07-04-2016

Anyone?? It is the 263 firmware, but neither are using the 5ghz and all devices have been given static IP's

May have to bite the bullet and try and buy a less flaky modem/router

Gandalf · ‎21-04-2017

Thanks for getting in touch @sullys666 and apologies for the delayed response.

Can you drop me a PM with your account username so I can look into this for you?

From 31st October 2022, I no longer have a regular presence here as I’ve moved on to a new role.

Anoush Mortazavi
Plusnet

sullys666 · ‎07-04-2016

PM sent

Gandalf · ‎21-04-2017

Thanks for the private message @sullys666 Because this appears to be a wireless issue, can you try going through the wireless troubleshooting steps explained Here. If you continue to experience problems I'd then recommend moving your wireless devices onto the wireless network ending in 5GHz.

If you have issues while on the 5GHz wireless frequency, it may be worth posting in this thread Here as we might be able to make changes to your router's firmware version.

From 31st October 2022, I no longer have a regular presence here as I’ve moved on to a new role.

Anoush Mortazavi
Plusnet

Mav · ‎06-04-2007

Moderator's note(s):

Thread moved from Fibre Broadband to My Router.

Forum Moderator and Customer
Courage is resistance to fear, mastery of fear, not absence of fear - Mark Twain
He who feared he would not succeed sat still

sullys666 · ‎07-04-2016

Checking in settings and 5gHz is separated from the 2.4 and has been since I joined. The 5gHz doesn't show as an available network on my phone or my wife's and it's showing in settings as broadcasting. Any suggestions as to why this is?

Also 5gHz isn't showing on wifi analyser 😞

sullys666 · ‎07-04-2016

TV and Sky Box, which had been connected lost connection this afternoon. 5gHz no longer appears to be showing at all. I am going to reboot the Hub once my son finishes the download on his XBox One in an attempt to try and get it back.

sullys666 · ‎07-04-2016

Noticed when I went into settings that the Smart function had been re enabled, which is probably why 5gHz wasn't showing. I have split them again and am in the process of reconnecting anything that needs it. No idea how it reverted to the Smart connection as I had split it and just connected stuff close to the router to it (TV and Sky+ Box).

Will keep an eye on things and report back if things are still not right.