cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
pandarock32
Aspiring Contributor
14,860 Views
Message 1 of 7

BT Home Hub 4 event log

Go to solution

Hi Everyone

I have a home hub 4, and noticed this constantly in the event log:

 

21:52:26, 03 May.BLOCKED 1 more packets (because of Packet invalid in connection)
21:52:25, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 173.194.65.155:80->86.141.91.124:55255 on ppp0)
21:52:21, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.179.51:80->86.141.91.124:55248 on ppp0)
21:52:20, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 80.239.137.104:80->86.141.91.124:55247 on ppp0)
21:48:55, 03 May.(118320.860000) Admin login successful by 192.168.1.130 on HTTP
21:48:43, 03 May.(118309.080000) New GUI session from IP 192.168.1.130
21:48:40, 03 May.OUT: BLOCK [65] First packet is Invalid (TCP 192.168.1.64:55323->157.56.194.23:443 on ppp0)
21:48:38, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.64:55317->184.50.162.217:443 on ppp0)
21:47:42, 03 May.(118248.210000) Lease requested
21:37:45, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 208.46.117.204:80->86.141.91.124:54271 on ppp0)
21:35:57, 03 May.BLOCKED 1 more packets (because of Packet invalid in connection)
21:35:57, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 198.78.221.126:80->86.141.91.124:50220 on ppp0)
21:34:38, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:57563->54.201.29.164:443 on ppp0)
21:34:37, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:53120->54.201.29.164:443 on ppp0)
21:34:34, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:59096->54.201.29.164:443 on ppp0)
21:34:33, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:49493->54.201.29.164:443 on ppp0)
21:34:32, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:59303->54.201.29.164:443 on ppp0)
21:34:30, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:53280->54.201.29.164:443 on ppp0)
21:34:29, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:53647->23.32.8.35:443 on ppp0)
21:34:28, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:52880->23.32.8.35:443 on ppp0)
21:34:25, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:57994->54.201.29.164:443 on ppp0)
21:34:24, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:51493->54.201.29.164:443 on ppp0)
21:34:23, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:64884->54.201.29.164:443 on ppp0)
21:34:21, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:61678->54.201.29.164:443 on ppp0)
21:34:18, 03 May.BLOCKED 1 more packets (because of Packet invalid in connection)
21:34:17, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:53528->54.201.29.164:443 on ppp0)
21:34:15, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:54214->54.201.29.164:443 on ppp0)
21:34:12, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:54451->54.201.29.164:443 on ppp0)
21:34:09, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:51847->23.34.178.106:443 on ppp0)
21:33:20, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:63872->31.13.72.112:443 on ppp0)
21:33:19, 03 May.BLOCKED 19 more packets (because of Packet invalid in connection)
21:33:18, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:62686->198.78.221.126:80 on ppp0)
21:33:01, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 80.239.137.98:80->86.141.91.124:64029 on ppp0)
21:30:47, 03 May.wlan1: STA 84:7a:88:53:f7:02 IEEE 802.11: Client disassociated
21:30:09, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 80.239.137.122:80->86.141.91.124:61591 on ppp0)
21:30:04, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 80.239.137.98:80->86.141.91.124:61586 on ppp0)
21:30:02, 03 May.BLOCKED 1 more packets (because of First packet is Invalid)
21:30:00, 03 May.OUT: BLOCK [65] First packet is Invalid (TCP 192.168.1.87:43375->173.194.65.138:443 on ppp0)
21:29:58, 03 May.BLOCKED 5 more packets (because of First packet is Invalid)
21:29:56, 03 May.OUT: BLOCK [65] First packet is Invalid (TCP 192.168.1.87:55832->173.194.65.138:443 on ppp0)
21:29:55, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 80.239.137.98:80->86.141.91.124:61583 on ppp0)
21:29:51, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 80.239.137.98:80->86.141.91.124:61582 on ppp0)
21:29:50, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:61576->54.215.195.204:443 on ppp0)
21:29:40, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.187.160:443->86.141.91.124:61570 on ppp0)
21:29:39, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.187.160:443->86.141.91.124:61569 on ppp0)
21:29:39, 03 May.BLOCKED 1 more packets (because of Packet invalid in connection)
21:29:39, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.167.40:80->86.141.91.124:61568 on ppp0)
21:29:37, 03 May.BLOCKED 1 more packets (because of Packet invalid in connection)
21:29:36, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.182.165:80->86.141.91.124:61561 on ppp0)
21:29:36, 03 May.BLOCKED 4 more packets (because of Packet invalid in connection)
21:29:35, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:61554->54.200.192.165:443 on ppp0)
21:29:35, 03 May.BLOCKED 5 more packets (because of Packet invalid in connection)
21:29:34, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:64972->54.186.19.164:443 on ppp0)
21:29:28, 03 May.BLOCKED 1 more packets (because of Packet invalid in connection)
21:29:26, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:56103->50.18.217.218:443 on ppp0)
21:29:25, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:51503->50.112.174.81:443 on ppp0)
21:29:24, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.188.19:443->86.141.91.124:51200 on ppp0)
21:29:20, 03 May.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.71:56407->54.201.63.197:443 on ppp0)
21:29:19, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.188.19:443->86.141.91.124:55894 on ppp0)
21:29:17, 03 May.BLOCKED 2 more packets (because of Packet invalid in connection)
21:29:17, 03 May.(117142.930000) Port forwarding rule added via UPnP/TR064. Protocol: UDP, external ports: any->9308, internal ports: 9308, internal client: 192.168.1.71
21:29:16, 03 May.IN: BLOCK [9] Packet invalid in connection (TCP 23.214.188.19:443->86.141.91.124:64466 on ppp0)
21:29:13, 03 May.(117139.090000) Lease for IP 192.168.1.71 renewed by host PS4-b0-05-94-88-0f-d5 (MAC b0:05:94:88:0f:d5). Lease duration: 1440 min
21:29:13, 03 May.(117139.090000) Device connected: Hostname: PS4-b0-05-94-88-0f-d5 IP: 192.168.1.71 MAC: b0:05:94:88:0f:d5 Lease time: 1440 min. Link rate: 144.4 Mbps
21:29:13, 03 May.(117139.010000) Lease requested
21:29:12, 03 May.

wlan0: STA b0:05:94:88:0f:d5 IEEE 802.11: Client associated

 

 

 

Is this OK? I read on a similar thread that it was the firewall but as mine is on 'allow all traffic' does that mean there is a problem? By the way the ip adress that mostly comes up, 192.168.1.71 is my ps4 I was streaming a video at the time

 

0 Ratings
Reply
6 REPLIES 6
Distinguished Sage
14,848 Views
Message 2 of 7

Re: BT Home Hub 4 event log

Go to solution
I would suggest for your safety that the hub firewall is activated it is there for your protection
pandarock32
Aspiring Contributor
14,846 Views
Message 3 of 7

Re: BT Home Hub 4 event log

Go to solution
Ok thanks, I will activate it. Are the log events normal?
0 Ratings
Reply
Distinguished Sage
14,824 Views
Message 4 of 7

Re: BT Home Hub 4 event log

Go to solution
yes they are
pandarock32
Aspiring Contributor
14,805 Views
Message 5 of 7

Re: BT Home Hub 4 event log

Go to solution

UPDATE Uh-oh, I just checked the log one last time as a video I was watching simply failed to load and saw it was suddenly blocking hundreds of packets at a time. I then did a speed test and got a 100% packet loss. I'm not sure this is normal now

0 Ratings
Reply
pandarock32
Aspiring Contributor
14,797 Views
Message 6 of 7

Re: BT Home Hub 4 event log

Go to solution

It's ok, I realised it could be safari that was doing it (I'm on a macbook air) I then tried in chrome both the video and speedtest and it worked fine, on safari my ping was 105 and in chrome 70

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
14,791 Views
Message 7 of 7

Re: BT Home Hub 4 event log

Go to solution

solved the problem - nice and easy change of browser



If you like a post, or want to say thanks for a helpful answer, please click on the Ratings 'Thumbs up' on left hand side.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.