cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
maat121m
Aspiring Contributor
1,640 Views
Message 1 of 9

HH5 Disconnections

Hello, have had consistent disconnections all throughout the day for about 2-3 weeks now. It will happen every so often but usually around the same time every day, and to fix I disconnect from my router and re-connect. This occurs to every device in the house hold. Also, my event log looks a little crazy..so if anyone could provide some insight or help it would be appreciated.

Thanks.

 

5:31:03, 30 Apr.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.65:47996 <-->86.145.166.40:47996 [201.24.234.27:50122] CLOSED/TIME_WAIT ppp3 NAPT)
15:31:01, 30 Apr.IN: ACCEPT [54] Connection opened (Port Forwarding: UDP 192.168.1.65:47996 <-->86.145.166.40:47996 [98.215.37.60:11621] ppp3 NAPT)
15:31:01, 30 Apr.IN: ACCEPT [54] Connection opened (Port Forwarding: UDP 192.168.1.70:47683 <-->86.145.166.40:47683 [98.215.37.60:11621] ppp3 NAPT)
15:30:47, 30 Apr.IN: ACCEPT [54] Connection opened (Port Forwarding: UDP 192.168.1.65:47996 <-->86.145.166.40:47996 [201.24.234.27:28786] ppp3 NAPT)
15:30:47, 30 Apr.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP 192.168.1.65:47996 <-->86.145.166.40:47996 [201.24.234.27:50122] CLOSED/SYN_SENT ppp3 NAPT)
15:30:41, 30 Apr.(443424.080000) Port forwarding rule added via UPnP/TR064. Protocol: TCP, external ports: any->47996, internal ports: 47996, internal client: 192.168.1.65
15:30:39, 30 Apr.IN: ACCEPT [57] Connection closed (Port Forwarding: UDP 192.168.1.65:47996 <-->86.145.166.40:47996 [194.230.159.251:22177] ppp3 NAPT)
15:30:39, 30 Apr.IN: ACCEPT [57] Connection closed (Port Forwarding: UDP 192.168.1.65:47996 <-->86.145.166.40:47996 [213.195.48.40:54357] ppp3 NAPT)
15:30:39, 30 Apr.IN: ACCEPT [57] Connection closed (Port Forwarding: UDP 192.168.1.65:47996 <-->86.145.166.40:47996 [168.187.148.137:61623] ppp3 NAPT)
15:30:36, 30 Apr.(443419.310000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any->47996, internal ports: 47996, internal client: 192.168.1.65
15:30:33, 30 Apr.(443415.740000) Port forwarding rule deleted via UPnP/TR064. Protocol: TCP, external ports: any->47996, internal ports: 47996, internal client: 192.168.1.65
15:30:29, 30 Apr.(443411.840000) Port forwarding rule deleted via UPnP/TR064. Protocol: UDP, external ports: any->47996, internal ports: 47996, internal client: 192.168.1.65
15:30:17, 30 Apr.IN: ACCEPT [57] Connection closed (Port Forwarding: TCP 192.168.1.65:47996 <-->86.145.166.40:47996 [83.10.138.171:63330] TIME_WAIT/CLOSED ppp3 NAPT)
15:30:16, 30 Apr.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP 192.168.1.65:47996 <-->86.145.166.40:47996 [83.10.138.171:63330] CLOSED/SYN_SENT ppp3 NAPT)
15:30:15, 30 Apr.(443398.230000) Lease for IP 192.168.1.65 renewed by host Matt-PC (MAC 00:b0:8c:00:04:23). Lease duration: 30240 min
15:30:15, 30 Apr.(443398.230000) Device connected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23 Lease time: 30240 min. Link rate: 58.5 Mbps
15:30:15, 30 Apr.(443398.160000) Lease requested
15:30:15, 30 Apr.ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client associated
15:30:10, 30 Apr.(443392.540000) Device disconnected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23
15:30:10, 30 Apr.ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client disassociated
15:30:07, 30 Apr.BLOCKED 2 more packets (because of Packet invalid in connection)
15:30:06, 30 Apr.BLOCKED 3 more packets (because of Packet invalid in connection)
15:30:05, 30 Apr.BLOCKED 1 more packets (because of Packet invalid in connection)
15:30:04, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 173.194.34.67:443->86.145.166.40:55722 on ppp3)
15:29:56, 30 Apr.BLOCKED 2 more packets (because of Packet invalid in connection)
15:29:55, 30 Apr.BLOCKED 1 more packets (because of Packet invalid in connection)
15:29:54, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 173.194.34.67:443->86.145.166.40:55722 on ppp3)
15:29:53, 30 Apr.(443376.190000) Lease for IP 192.168.1.65 renewed by host Matt-PC (MAC 00:b0:8c:00:04:23). Lease duration: 30240 min
15:29:53, 30 Apr.(443376.190000) Device connected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23 Lease time: 30240 min. Link rate: 58.5 Mbps
15:29:53, 30 Apr.(443376.120000) Lease requested
15:29:50, 30 Apr.BLOCKED 1 more packets (because of Packet invalid in connection)
15:29:49, 30 Apr.BLOCKED 2 more packets (because of Packet invalid in connection)
15:29:48, 30 Apr.BLOCKED 4 more packets (because of Packet invalid in connection)
15:29:48, 30 Apr.(443371.190000) Lease for IP 192.168.1.65 renewed by host Matt-PC (MAC 00:b0:8c:00:04:23). Lease duration: 30240 min
15:29:48, 30 Apr.(443371.190000) Device connected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23 Lease time: 30240 min. Link rate: 58.5 Mbps
15:29:48, 30 Apr.(443371.120000) Lease requested
15:29:48, 30 Apr.ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client associated
15:29:47, 30 Apr.BLOCKED 5 more packets (because of Packet invalid in connection)
15:29:46, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 31.13.72.65:443->86.145.166.40:55729 on ppp3)
15:29:46, 30 Apr.BLOCKED 2 more packets (because of Packet invalid in connection)
15:29:45, 30 Apr.BLOCKED 4 more packets (because of Packet invalid in connection)
15:29:45, 30 Apr.(443368.370000) Device disconnected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23
15:29:45, 30 Apr.ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client disassociated
15:29:44, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 31.13.72.65:443->86.145.166.40:55729 on ppp3)
15:29:42, 30 Apr.BLOCKED 1 more packets (because of Packet invalid in connection)
15:29:41, 30 Apr.BLOCKED 4 more packets (because of Packet invalid in connection)
15:29:40, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 31.13.72.65:443->86.145.166.40:55729 on ppp3)
15:29:40, 30 Apr.BLOCKED 6 more packets (because of Packet invalid in connection)
15:29:39, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 31.55.166.211:443->86.145.166.40:55712 on ppp3)
15:29:39, 30 Apr.BLOCKED 6 more packets (because of Packet invalid in connection)
15:29:38, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 31.55.166.211:443->86.145.166.40:55710 on ppp3)
15:29:38, 30 Apr.BLOCKED 7 more packets (because of Packet invalid in connection)
15:29:37, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 31.55.166.211:443->86.145.166.40:55725 on ppp3)
15:29:36, 30 Apr.IN: BLOCK [9] Packet invalid in connection (TCP 173.252.107.18:443->86.145.166.40:55724 on ppp3)
0 Ratings
Reply
8 REPLIES 8
Barry57
Expert
1,603 Views
Message 2 of 9

Re: HH5 Disconnections

Hi 

 

Your not alone with the HH5 disconnections 😞

 

As for a fix -

 

https://community.bt.com/t5/BT-Infinity-Speed-Connection/planning-to-get-myself-an-unlocked-openreac...

 

The Above thread worked for me -

 

More experienced posters pointed me towards that thread and its been great since!

 

Thanks

maat121m
Aspiring Contributor
1,565 Views
Message 3 of 9

Re: HH5 Disconnections

Since my event log has not stated that the router restarts, just that lots of packets are blocked and then it re-requests the lease again, would there be any way of figuring out how/why my router is disconnecting?

 

Thanks.

 

*Most recent disconnections.

 

14:03:30, 01 May.(10538.400000) Lease for IP 192.168.1.65 renewed by host Matt-PC (MAC 00:b0:8c:00:04:23). Lease duration: 30240 min
14:03:30, 01 May.(10538.390000) Device connected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23 Lease time: 30240 min. Link rate: 58.5 Mbps
14:03:30, 01 May.(10538.330000) Lease requested
14:03:30, 01 May.ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client associated
14:03:28, 01 May.BLOCKED 1 more packets (because of Packet invalid in connection)
14:03:28, 01 May.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP 192.168.1.65:47996 <-->109.152.67.204:47996 [2.123.248.213:46306] CLOSED/SYN_SENT ppp3 NAPT)
14:03:27, 01 May.IN: ACCEPT [54] Connection opened (Port Forwarding: TCP 192.168.1.65:47996 <-->109.152.67.204:47996 [2.123.248.213:37585] CLOSED/SYN_SENT ppp3 NAPT)
14:03:27, 01 May.(10535.150000) Device disconnected: Hostname: Matt-PC IP: 192.168.1.65 MAC: 00:b0:8c:00:04:23
14:03:26, 01 May.IN: BLOCK [9] Packet invalid in connection (TCP 46.19.168.101:443->109.152.67.204:52759 on ppp3)
14:03:25, 01 May.ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client disassociated
14:03:24, 01 May.BLOCKED 1 more packets (because of Packet invalid in connection)
14:03:23, 01 May.IN: BLOCK [9] Packet invalid in connection (TCP 46.19.168.101:443->109.152.67.204:52761 on ppp3)

 

 

0 Ratings
Reply
Semmy
Contributor
1,531 Views
Message 4 of 9

Re: HH5 Disconnections

Hi mate,

 

Have just gone through this issue.

 

On inspectionof the event log the wireless is disconnecting due to the wireless module disconnecting within the hub as evidenced by this line "ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client disassociated".

 

Went through the usual rigmarole with the chap in India via the online chat... (handy for the ability to save evidence of conversations).

 

Final synopsis after being told to try the blindingly obvious (have you tried resetting etc...), the router is faulty.

 

New router sent and no repeat of the issue.

0 Ratings
Reply
Semmy
Contributor
1,529 Views
Message 5 of 9

Re: HH5 Disconnections

I also do have a HG612 on the way 😉
0 Ratings
Reply
Leg2ion
Aspiring Expert
1,475 Views
Message 6 of 9

Re: HH5 Disconnections


@Semmy wrote:

 

On inspectionof the event log the wireless is disconnecting due to the wireless module disconnecting within the hub as evidenced by this line "ath00: STA 00:b0:8c:00:04:23 IEEE 802.11: Client disassociated".

 


Is that correct? I thought the number after the STA was the MAC address of the wireless device connected to the router.

 

I have multiple devices connected wirelessly to my router, so if the wireless module in the hub was disconnecting, surely I would see an entry for every device, not just my smartphone?

0 Ratings
Reply
Barry57
Expert
1,444 Views
Message 7 of 9

Re: HH5 Disconnections

There are great those HG612 3B's

 

Always useful this thread for updates and findings 🙂

 

https://community.bt.com/t5/BT-Infinity-Speed-Connection/planning-to-get-myself-an-unlocked-openreac...

0 Ratings
Reply
Semmy
Contributor
1,430 Views
Message 8 of 9

Re: HH5 Disconnections

Sorry, I was a little unclear.

 

To put it more precisely the hub is disconnecting the device not a case of the device loosing the connection.

0 Ratings
Reply
Leg2ion
Aspiring Expert
1,405 Views
Message 9 of 9

Re: HH5 Disconnections

Ah, OK. Seems odd though that in my case it is being selective?

0 Ratings
Reply