cancel
Showing results for 
Search instead for 
Did you mean: 
Jaseb41
Aspiring Expert
24,870 Views
Message 1 of 16

Bt homehub 5 event log ?

Hi had homehub 5 since yesterday all working fine just a bit concerned about all these listings showing in the event log any ideas on why these are showing ?

BLOCKED 4 more packets (because of Packet invalid in connection)
23:39:29, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49602-​>68.232.35.139:443 on ppp3)
23:36:49, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49472-​>23.23.222.135:443 on ppp3)
23:36:29, 24 Oct. BLOCKED 2 more packets (because of Packet invalid in connection)
23:36:26, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49535-​>68.232.35.139:443 on ppp3)
23:35:56, 24 Oct. BLOCKED 1 more packets (because of Packet invalid in connection)
23:35:55, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49496-​>68.232.35.139:443 on ppp3)
23:24:39, 24 Oct. (128613.430000) Admin login successful by 192.168.1.68 on HTTP
23:24:15, 24 Oct. (128589.510000) New GUI session from IP 192.168.1.68
23:17:53, 24 Oct. BLOCKED 1 more packets (because of Packet invalid in connection)
23:17:50, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49246-​>93.184.220.97:443 on ppp3)
23:16:50, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49169-​>95.100.194.217:443 on ppp3)
23:16:13, 24 Oct. (128107.460000) Lease for IP 192.168.1.68 renewed by host Jases-​iPad (MAC e0:b9:ba:bb:1a:14). Lease duration: 1440 min
23:16:13, 24 Oct. (128107.460000) Device connected: Hostname: Jases-​iPad IP: 192.168.1.68 MAC: e0:b9:ba:bb:1a:14 Lease time: 1440 min. Link rate: 130.0 Mbps
23:16:13, 24 Oct. (128107.410000) Lease requested
23:16:11, 24 Oct. ath10: STA e0:b9:ba:bb:1a:14 IEEE 802.11: Client associated
23:08:02, 24 Oct. ath10: STA 00:62:2c:09:e8:95 IEEE 802.11: WiFi registration failed
22:56:13, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49923-​>17.172.232.75:443 on ppp3)
22:44:58, 24 Oct. (126232.720000) Lease for IP 192.168.1.78 expired. MAC: 00:1d:bc:52:40:4c, host name: Wii
22:39:41, 24 Oct. BLOCKED 11 more packets (because of Packet invalid in connection)
22:39:39, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49919-​>213.123.85.97:80 on ppp3)
22:38:41, 24 Oct. (125855.790000) New GUI session from IP 192.168.1.65
22:30:39, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49868-​>87.248.114.191:993 on ppp3)
22:28:05, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49850-​>68.232.35.139:443 on ppp3)
22:27:40, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49848-​>68.232.35.139:443 on ppp3)
22:26:21, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49839-​>68.232.35.139:443 on ppp3)
22:25:28, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49811-​>68.232.35.139:443 on ppp3)
22:22:43, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49825-​>68.232.35.139:443 on ppp3)
22:21:56, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49819-​>95.100.194.217:443 on ppp3)
22:21:51, 24 Oct. BLOCKED 3 more packets (because of Packet invalid in connection)
22:21:49, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49815-​>68.232.35.139:443 on ppp3)
22:21:43, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49792-​>23.21.181.59:443 on ppp3)
22:21:32, 24 Oct. IN: BLOCK [9] Packet invalid in connection (TCP 17.130.16.4:443-​>86.146.156.99:49790 on ppp3)
22:21:16, 24 Oct. IN: BLOCK [9] Packet invalid in connection (TCP 199.16.156.8:443-​>86.146.156.99:49809 on ppp3)
22:20:57, 24 Oct. IN: BLOCK [9] Packet invalid in connection (TCP 213.123.85.18:80-​>86.146.156.99:49782 on ppp3)
22:17:20, 24 Oct. (124574.720000) Lease for IP 192.168.1.65 renewed by host Jases-​iPhone-​5 (MAC bc:92:6b:1a:f2:40). Lease duration: 1440 min
22:17:20, 24 Oct. (124574.720000) Device connected: Hostname: Jases-​iPhone-​5 IP: 192.168.1.65 MAC: bc:92:6b:1a:f2:40 Lease time: 1440 min. Link rate: 130.0 Mbps
22:17:20, 24 Oct. (124574.660000) Lease requested
22:17:20, 24 Oct. ath10: STA bc:92:6b:1a:f2:40 IEEE 802.11: Client associated
22:17:20, 24 Oct. ath10: STA bc:92:6b:1a:f2:40 IEEE 802.11: Client disassociated
22:06:18, 24 Oct. (123912.540000) Lease for IP 192.168.1.65 renewed by host Jases-​iPhone-​5 (MAC bc:92:6b:1a:f2:40). Lease duration: 1440 min
22:06:18, 24 Oct. (123912.540000) Device connected: Hostname: Jases-​iPhone-​5 IP: 192.168.1.65 MAC: bc:92:6b:1a:f2:40 Lease time: 1440 min. Link rate: 130.0 Mbps
22:06:18, 24 Oct. (123912.480000) Lease requested
22:01:31, 24 Oct. ath10: STA bc:92:6b:1a:f2:40 IEEE 802.11: Client associated
22:01:30, 24 Oct. ath10: STA bc:92:6b:1a:f2:40 IEEE 802.11: Client disassociated
21:58:14, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49753-​>188.125.68.69:993 on ppp3)
21:58:08, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49758-​>188.125.68.69:993 on ppp3)
21:57:51, 24 Oct. BLOCKED 1 more packets (because of Packet invalid in connection)
21:57:50, 24 Oct. OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.65:49729-​>87.248.114.191:993 on ppp3)
21:53:53, 24 Oct. (123168.280000) Lease for IP 192.168.1.65 renewed by host Jases-​iPhone-​5 (MAC bc:92:6b:1a:f2:40). Lease duration: 1440 min
21:53:53, 24 Oct. (123168.280000) Device connected: Hostname: Jases-​iPhone-​5 IP: 192.168.1.65 MAC: bc:92:6b:1a:f2:40 Lease time: 1440 min. Link rate: 130.0 Mbps
21:53:53, 24 Oct. (123168.220000) Lease requested
21:53:53, 24 Oct. ath10: STA bc:92:6b:1a:f2:40 IEEE 802.11: Client associated
20:40:18, 24 Oct. (118752.430000) Lease for IP 192.168.1.64 renewed by host Sky-​Plus-​HD-​2TB (MAC 00:19:fb:e8:59:d6). Lease duration: 1440 min
20:40:18, 24 Oct. (118752.430000) Device connected: Hostname: Sky-​Plus-​HD-​2TB IP: 192.168.1.64 MAC: 00:19:fb:e8:59:d6 Lease time: 1440 min. Link rate: 100.0 Mbps
20:40:18, 24 Oct. (118752.380000) Lease requested
20:17:20, 24 Oct. IN: BLOCK [16] Remote administration (TCP 60.214.233.220:6000-​>86.146.156.99:8080 on ppp3)
19:43:28, 24 Oct. IN: BLOCK [16] Remote administration (TCP 218.95.217.105:52890-​>86.146.156.99:8080 on ppp3)
19:23:29, 24 Oct. IN: BLOCK [16] Remote administration (TCP 123.151.42.61:12213-​>86.146.156.99:8080 on ppp3)
19:16:28, 24 Oct. IN: BLOCK [16] Remote administration (TCP 111.73.45.118:54830-​>86.146.156.99:443 on ppp3)
19:16:20, 24 Oct. IN: BLOCK [16] Remote administration (TCP 111.73.45.118:43086-​>86.146.156.99:80 on ppp3)
19:16:17, 24 Oct. BLOCKED 1 more packets (because of Remote administration)
19:16:13, 24 Oct. IN: BLOCK [16] Remote administration (TCP 111.73.45.118:53393-​>86.146.156.99:8080 on ppp3)
19:10:13, 24 Oct. (113347.890000) OpenWiFi IPSec connection is down
19:07:59, 24 Oct. IN: BLOCK [16] Remote administration (TCP 211.137.245.135:24459-​>86.146.156.99:80 on ppp3)
18:55:03, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:55:02, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 10.204.38.50:68-​>255.255.255.255:67 on ath02)
18:47:33, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:47:32, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:46:18, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:46:17, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:41:08, 24 Oct. IN: BLOCK [16] Remote administration (TCP 212.154.213.238:29960-​>86.146.156.99:80 on ppp3)
18:38:03, 24 Oct. IN: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_br1_in/rule/8: UDP 10.204.38.50:3053-​>172.30.139.17:53 on br1)
18:37:59, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:37:58, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:37:37, 24 Oct. BLOCKED 5 more packets (because of Advanced Filter Rule)
18:37:35, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:36:50, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:36:49, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:35:42, 24 Oct. BLOCKED 5 more packets (because of Advanced Filter Rule)
18:35:41, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:34:52, 24 Oct. IN: BLOCK [16] Remote administration (TCP 189.192.19.235:2094-​>86.146.156.99:22 on ppp3)
18:32:16, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:32:15, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:31:58, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:31:57, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:31:57, 24 Oct. BLOCKED 3 more packets (because of Advanced Filter Rule)
18:31:55, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:31:55, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:31:54, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:31:54, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:31:54, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 0.0.0.0:68-​>255.255.255.255:67 on ath02)
18:30:59, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:30:57, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 10.204.38.50:68-​>255.255.255.255:67 on ath02)
18:23:29, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:23:27, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 10.204.38.50:68-​>255.255.255.255:67 on ath02)
18:15:59, 24 Oct. BLOCKED 2 more packets (because of Advanced Filter Rule)
18:15:57, 24 Oct. OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 10.204.38.50:68-​>255.255.255.255:67 on ath02)
18:08:28, 24 Oct. BLOCKED 6 more packets (because of Advanced Filter Rule)

Any help would be great thanks jase !
0 Ratings
15 REPLIES 15
Jaseb41
Aspiring Expert
24,814 Views
Message 2 of 16

Re: Bt homehub 5 event log ?

Reported the above stats last night and there still coming through this morning any ideas anyone ?

 

10:47:42, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 185.24.98.37:80->86.146.156.99:49734 on ppp3)
10:45:07, 25 Oct.BLOCKED 2 more packets (because of Advanced Filter Rule)
10:45:06, 25 Oct.OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 10.204.38.50:68->255.255.255.255:67 on ath02)
10:41:32, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50099->66.220.152.23:443 on ppp3)
10:41:22, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50098->31.13.72.65:443 on ppp3)
10:40:55, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 31.13.72.65:443->86.146.156.99:50097 on ppp3)
10:40:55, 25 Oct.BLOCKED 3 more packets (because of Packet invalid in connection)
10:40:53, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 31.13.72.65:443->86.146.156.99:50097 on ppp3)
10:40:53, 25 Oct.BLOCKED 2 more packets (because of Packet invalid in connection)
10:40:52, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 31.13.72.65:443->86.146.156.99:50097 on ppp3)
10:38:22, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 66.220.152.23:443->86.146.156.99:50091 on ppp3)
10:38:22, 25 Oct.BLOCKED 1 more packets (because of Packet invalid in connection)
10:38:21, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 66.220.152.23:443->86.146.156.99:50091 on ppp3)
10:38:21, 25 Oct.BLOCKED 1 more packets (because of Packet invalid in connection)
10:38:20, 25 Oct.IN: BLOCK [9] Packet invalid in connection (TCP 66.220.152.23:443->86.146.156.99:50091 on ppp3)
10:38:03, 25 Oct.ath10: STA 00:62:2c:09:e8:95 IEEE 802.11: WiFi registration failed
10:37:37, 25 Oct.BLOCKED 2 more packets (because of Advanced Filter Rule)
10:37:36, 25 Oct.OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0: UDP 10.204.38.50:68->255.255.255.255:67 on ath02)
10:35:47, 25 Oct.BLOCKED 1 more packets (because of Packet invalid in connection)
10:35:45, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50087->217.32.28.185:443 on ppp3)
10:35:42, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50082->31.13.72.55:443 on ppp3)
10:35:42, 25 Oct.BLOCKED 1 more packets (because of Packet invalid in connection)
10:35:41, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50086->217.32.28.66:443 on ppp3)
10:35:38, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50088->217.32.28.57:443 on ppp3)
10:35:26, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50089->213.120.177.138:443 on ppp3)
10:35:18, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50085->213.120.177.177:443 on ppp3)
10:35:09, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50081->217.32.28.58:443 on ppp3)
10:34:28, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50078->217.32.28.57:443 on ppp3)
10:34:26, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50074->217.32.28.182:443 on ppp3)
10:34:09, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50076->213.120.177.177:443 on ppp3)
10:34:07, 25 Oct.BLOCKED 1 more packets (because of Packet invalid in connection)
10:34:04, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50077->217.32.28.49:443 on ppp3)
10:34:00, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50061->217.32.28.66:443 on ppp3)
10:33:58, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50075->217.32.28.49:443 on ppp3)
10:33:52, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50071->31.13.72.39:443 on ppp3)
10:33:40, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50070->31.13.72.23:443 on ppp3)
10:33:13, 25 Oct.BLOCKED 1 more packets (because of Packet invalid in connection)
10:33:11, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50054->217.32.28.182:443 on ppp3)
10:33:06, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50062->31.13.72.23:443 on ppp3)
10:32:58, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50059->31.13.72.7:443 on ppp3)
10:32:55, 25 Oct.OUT: BLOCK [65] First packet is Invalid (TCP 192.168.1.71:49596->17.172.116.78:443 on ppp3)
10:32:48, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50058->217.32.28.185:443 on ppp3)
10:32:38, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50060->213.120.177.209:443 on ppp3)
10:32:36, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50055->217.32.28.57:443 on ppp3)
10:32:16, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50053->31.13.72.55:443 on ppp3)
10:32:16, 25 Oct.BLOCKED 15 more packets (because of Packet invalid in connection)
10:32:15, 25 Oct.BLOCKED 6 more packets (because of Packet invalid in connection)
10:32:14, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50004->31.13.72.66:443 on ppp3)
10:32:12, 25 Oct.BLOCKED 2 more packets (because of Packet invalid in connection)
10:32:09, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50033->92.122.123.83:443 on ppp3)
10:32:05, 25 Oct.BLOCKED 2 more packets (because of Packet invalid in connection)
10:32:03, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50009->217.32.28.225:443 on ppp3)
10:32:02, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50008->217.32.28.225:443 on ppp3)
10:31:44, 25 Oct.BLOCKED 3 more packets (because of Packet invalid in connection)
10:31:42, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:50002->217.32.28.166:443 on ppp3)
10:31:40, 25 Oct.OUT: BLOCK [9] Packet invalid in connection (TCP 192.168.1.68:49998->31.13.72.65:443 on ppp3)
10:30:11, 25 Oct.(168546.060000) OpenWiFi IPSec connection is up
10:30:08, 25 Oct.BLOCKED 2 more packets (because of Advanced Filter Rule)
10:30:05, 25 Oct.OUT: BLOCK [44] Advanced Filter Rule (fw/policy/0/chain/fw_ath02_out/rule/0:
0 Ratings
Checked2013
Expert
24,806 Views
Message 3 of 16

Re: Bt homehub 5 event log ?

The "OpenWiFi IPSec connection is up" is when somebody connects to your wifi thru BT Wifi

 

Have you done any p2p/torrents at all?

0 Ratings
Jaseb41
Aspiring Expert
24,739 Views
Message 4 of 16

Re: Bt homehub 5 event log ?

Hi openWifi now disabled been waiting 48 hrs for switch off signal not done any p2p or torrents but the logs are still coming through think will phone bt tomorrow and get them to look into this problem ?
0 Ratings
Distinguished Sage
Distinguished Sage
24,731 Views
Message 5 of 16

Re: Bt homehub 5 event log ?

If you opt out of BTWifi you will not be able to use the free BTWifi hotspots when you are out and about. The opt out can take a week or more to register on your homehub. It has also been pointed out by some other posters that even when you opt out this does not opt out the 5GHz frequency which would appear to software glitch.

0 Ratings
Distinguished Sage
24,728 Views
Message 6 of 16

Re: Bt homehub 5 event log ?

the majority of what you are seeing there is firewall activity just use the log filter and you can see it there if you select the log display you wish to see
Jaseb41
Aspiring Expert
24,724 Views
Message 7 of 16

Re: Bt homehub 5 event log ?

Hi got unlimited internet on my mobile so don't really need it, cancelled openWifi on Tuesday it got disabled yesterday on both 2.4ghz and 5 ghz but still getting loads of events happening in the event log incoming and outgoing connection blocks never had this with my homehub 3b ?
0 Ratings
Jaseb41
Aspiring Expert
24,721 Views
Message 8 of 16

Re: Bt homehub 5 event log ?

Hi John46 as said before had homehub 3b for months and hardly had any of this events but since having homehub 5 since Tuesday they just don't stop ?
0 Ratings
Distinguished Sage
24,711 Views
Message 9 of 16

Re: Bt homehub 5 event log ?

there just the same on the hub 4
Jaseb41
Aspiring Expert
24,708 Views
Message 10 of 16

Re: Bt homehub 5 event log ?

Take it must be more sensitive to blocking inbound outbound connections than homehub 3b then ? So not much can really do about it then ?
0 Ratings