BT
At home
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Reply
Topic Options
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0
Accepted Solution

BT Home Hub nightmare

[ Edited ]
Options

‎19-02-2011 19h50 - edited ‎19-02-2011 20h30

Over the last week, I have spoken to over 5 BT representatives and on my 3rd BT Home Hub 2.0 Type A  (previously ok on BT Home 1.0 and 1.5), previously sales and customer services said they would send out a 'newer Home Hub that would ease my wireless signal issues' aka the issue inability to load webpages etc on either Windows 7 laptop or Ubuntu laptop (both different hardware, operating systems etc) after 11 hours switched on, unless hub is restarted then fine again.

 

In my stupidity I thought this would be the BT Home Hub 3.0 as advertised on the website, but since been told this is online only for new sales/willing to send one out for £47 (contracts renewed under a month ago !!)/awaiting stock/unable to see on the product catalogue, nothing is on the system notes for these conversations rather strangely.

 

Sadly unable to wait in today (sat) due to family commitments so spoke to them on monday i believe (all blurred) so cancelled eng visit for today , they even phoned back to confirm the visit was cancelled, just as we were going out BT engineer arrives to perform work with another BT Home Hub 2.0 under his arm , engineer advised, get automated message saying fault fixed ?? fast forward to 3.30pm advising engineer has fixed the 'issue' - 'which would be amazing if he could just be turning up knocking on the door then walking back to his van', relayed this to BT who said sorry again and would call us back tomorrow.

 

Issues are now every 5 hours, BT Technical support cant suggest anything but booking all day engineer visit to check the line, ethernet connection is ine, gone through repeated technical support workflows changing the channels, resetting to factory defaults, restarting the router aka http://bt.custhelp.com/app/answers/detail/c/346,502,505/a_id/13598


 

Even replaced the micro filters on every telephone socket i can find.

 

Any ideas, has anyone else had wireless issues.

 

 

 Download speedachieved during the test was - 1706 Kbps
 For your connection, the acceptable range of speeds is 400-2000 Kbps.
 Additional Information:
 Your DSL Connection Rate :2528 Kbps(DOWN-STREAM), 448 Kbps(UP-STREAM)
 IP Profile for your line is - 2000 Kbps

Message 1 of 34 (49,434 Views)
 
Reply
Please use plain text.
 
alones
Contributor
alones
Posts: 41
Registered: ‎17-01-2011

Re: BT Home Hub nightmare

Options

on ‎19-02-2011 20h47

Yes, it is a problem with the software updates for the hub.

 

Have you looked at your event log on your hub manager? Post what you get here

Message 2 of 34 (49,386 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

Options

on ‎19-02-2011 20h57

Hub Firmware Information
Current firmware Version 8.1.H.J (Type A)
Last updated 15/02/11

20:54:17 19 Feb LOGIN User admin logged in on [HTTP] (from 192.168.1.66)
20:53:55 19 Feb LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)
20:50:57 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 121.185.220.237 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:44:16 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:42:25 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:41:18 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:41:12 19 Feb SNTP Synchronised to server: 213.123.20.170
20:37:03 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 2.90.141.102 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:33:30 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 110.138.215.118 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:28:29 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 79.109.176.229 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Port Unreacheable
20:24:03 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 121.163.157.227 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:21:03 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 94.156.108.47 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:19:23 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 195.91.213.129 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Communication Administratively Prohibited
20:16:26 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 209.145.107.74 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:07:33 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 24.125.170.133 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:05:31 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 121.214.225.185 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
20:01:14 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 24.132.40.230 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:51:45 19 Feb VOIP: [2.0A] [100] [] 404 Not Found - SIP message sent
19:51:45 19 Feb VOIP: [2.0A] [100] [-] OPTIONS - SIP message received
19:41:12 19 Feb SNTP Synchronised to server: 213.123.26.170
19:35:30 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 2.51.251.125 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:28:33 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 122.107.9.237 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:20:55 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 82.101.205.153 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:14:11 19 Feb ALG Protocol: UDP Open port: 7648 Helper: CU/SeeMe => ok
19:11:41 19 Feb FIREWALL icmp check (1 of 3): Protocol: ICMP Src ip: 68.61.142.65 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:08:36 19 Feb FIREWALL icmp check (1 of 4): Protocol: ICMP Src ip: 123.214.251.14 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:05:33 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 123.214.251.14 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:03:27 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 123.214.251.14 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
19:01:29 19 Feb FIREWALL icmp check (1 of 19): Protocol: ICMP Src ip: 186.45.117.192 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
18:57:09 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 192.168.1.66 Dst ip: 81.94.87.72 Type: Destination Unreachable Code: Port Unreacheable
18:56:28 19 Feb ALG Protocol: UDP Open port: 7648 Helper: CU/SeeMe => ok
18:54:57 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 88.104.43.254 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
18:54:30 19 Feb UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)
18:54:29 19 Feb UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)
18:41:12 19 Feb SNTP Synchronised to server: 213.123.20.170
18:41:12 19 Feb SNTP Systemtime update: time setting 00:03:58 > new time setting: 18:41:12
00:02:04 1 Jan CONFIGURATION saved by TR69
00:01:32 1 Jan usbmgr: USB device isn't matched the configuration
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/module
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/09/module
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/09/00/module
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/09/00/00/module
00:01:32 1 Jan usbmgr: class:0x9 subclass:0x0 protocol:0x0
00:01:32 1 Jan usbmgr: buffer line: remove T
00:01:32 1 Jan usbmgr: USB device isn't matched the configuration
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/module
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/09/module
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/09/00/module
00:01:32 1 Jan usbmgr: try /etc/usbmgr/class/09/00/00/module
00:01:32 1 Jan usbmgr: class:0x9 subclass:0x0 protocol:0x0
00:01:32 1 Jan usbmgr: buffer line: remove T
00:00:59 1 Jan PPP link up (Internet) [81.155.44.58]
00:00:59 1 Jan PPP CHAP Chap receive success : authentication ok
00:00:58 1 Jan PPP CHAP Receive challenge (rhost = ESR8.Kingston4)
00:00:56 1 Jan xDSL linestate up (ITU-T G.992.1; downstream: 2528 kbit/s, upstream: 448 kbit/s; output Power Down: 17.5 dBm, Up: 12.5 dBm; line Attenuation Down: 62.0 dB, Up: 31.5 dB; snr Margin Down: 16.0 dB, Up: 6.3 dB)
00:00:54 1 Jan DHCS server up
00:00:48 1 Jan FIREWALL level changed to Standard.
00:00:42 1 Jan WIRELESS automatic channel selection done (channel = 10)
00:00:39 1 Jan FIREWALL event (1 of 1): deleted rules
00:00:39 1 Jan FIREWALL event (1 of 1): modified rules
00:00:39 1 Jan FIREWALL event (1 of 1): created rules
00:00:28 1 Jan WIRELESS interface turned on.
00:00:27 1 Jan usbmgr: start 0.4.8
00:00:19 1 Jan KERNEL Warm restart
18:23:53 19 Feb SNTP Synchronised again to server: 213.123.26.170
18:06:44 19 Feb VOIP: [2.0A] [100] [] 404 Not Found - SIP message sent
18:06:44 19 Feb VOIP: [2.0A] [100] [-] OPTIONS - SIP message received
17:34:51 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 88.8.188.33 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
17:30:59 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 24.222.218.181 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
17:26:12 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
17:23:53 19 Feb SNTP Synchronised to server: 213.123.26.170
17:17:40 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 24.18.80.251 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
17:15:49 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 78.45.4.17 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
16:56:59 19 Feb FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
16:53:43 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
16:44:54 19 Feb FIREWALL icmp check (1 of 3): Protocol: ICMP Src ip: 93.103.82.27 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
16:42:02 19 Feb FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 67.167.33.221 Dst ip: 86.137.107.185 Type: Destination Unreachable Code: Host Unreacheable
16:41:27 19 Feb UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)
16:41:25 19 Feb UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)
16:23:52 19 Feb SNTP Synchronised again to server: 213.123.20.170
15:23:52 19 Feb SNTP Synchronised to server: 213.123.20.170
14:23:52 19 Feb SNTP Synchronised again to server: 213.123.26.170
13:23:52 19 Feb SNTP Synchronised to server: 213.123.26.170
12:23:52 19 Feb SNTP Synchronised to server: 213.123.20.170
11:23:52 19 Feb SNTP Synchronised again to server: 213.123.26.170
10:23:52 19 Feb SNTP Synchronised again to server: 213.123.26.170
09:23:52 19 Feb SNTP Synchronised to server: 213.123.26.170
09:23:52 19 Feb SNTP Systemtime update: time setting 00:03:59 > new time setting: 09:23:52
00:02:05 1 Jan CONFIGURATION saved by TR69
00:01:33 1 Jan usbmgr: USB device isn't matched the configuration
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/module
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/09/module
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/09/00/module
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/09/00/00/module
00:01:33 1 Jan usbmgr: class:0x9 subclass:0x0 protocol:0x0
00:01:33 1 Jan usbmgr: buffer line: remove T
00:01:33 1 Jan usbmgr: USB device isn't matched the configuration
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/module
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/09/module
00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/09/00/module

00:01:33 1 Jan usbmgr: try /etc/usbmgr/class/09/00/00/module
00:01:33 1 Jan usbmgr: class:0x9 subclass:0x0 protocol:0x0
00:01:33 1 Jan usbmgr: buffer line: remove T
00:01:00 1 Jan PPP link up (Internet) [86.137.107.185]
00:01:00 1 Jan PPP CHAP Chap receive success : authentication ok
00:00:59 1 Jan PPP CHAP Receive challenge (rhost = ESR8.Kingston4)
00:00:56 1 Jan xDSL linestate up (ITU-T G.992.1; downstream: 2496 kbit/s, upstream: 448 kbit/s; output Power Down: 17.8 dBm, Up: 12.5 dBm; line Attenuation Down: 62.0 dB, Up: 31.5 dB; snr Margin Down: 16.0 dB, Up: 6.3 dB)
00:00:55 1 Jan DHCS server up
00:00:49 1 Jan FIREWALL level changed to Standard.
00:00:43 1 Jan WIRELESS automatic channel selection done (channel = 7)
00:00:40 1 Jan FIREWALL event (1 of 1): deleted rules
00:00:40 1 Jan FIREWALL event (1 of 1): modified rules
00:00:40 1 Jan FIREWALL event (1 of 1): created rules
00:00:29 1 Jan WIRELESS interface turned on.
00:00:28 1 Jan usbmgr: start 0.4.8
00:00:19 1 Jan KERNEL Warm restart
Message 3 of 34 (49,377 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

Options

on ‎19-02-2011 20h58

ADSL line status
Connection information
Line state Connected
Connection time 0 days, 2:19:57
Downstream 2,528 Kbps
Upstream 448 Kbps

ADSL settings
VPI/VCI 0/38
Type PPPoA
Modulation ITU-T G.992.1
Latency type Interleaved
Noise margin (Down/Up) 6.0 dB / 16.0 dB
Line attenuation (Down/Up) 62.0 dB / 31.5 dB
Output power (Down/Up) 17.5 dBm / 12.5 dBm
Message 4 of 34 (49,375 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

Options

on ‎19-02-2011 21h00

Disabled Firewall and saved settings
Message 5 of 34 (49,374 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

[ Edited ]
Options

‎19-02-2011 23h28 - edited ‎19-02-2011 23h58

23:54:59  19 Feb     LOGIN User admin logged in on [HTTP] (from 192.168.1.66)
23:54:50  19 Feb     LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)
23:53:42  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 91.82.64.149 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:49:17  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 24.8.45.90 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:42:36  19 Feb     FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 76.31.192.132 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:41:12  19 Feb     SNTP Synchronised to server: 213.123.26.170
23:41:06  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 95.220.114.48 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:35:32  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 123.230.195.8 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:29:26  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 221.159.211.186 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:26:56  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 112.186.95.87 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:25:32  19 Feb     LOGIN User admin logged in on [HTTP] (from 192.168.1.66)
23:25:20  19 Feb     LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)
23:25:02  19 Feb     FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 174.52.3.91 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:23:21  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 90.154.230.119 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:22:33  19 Feb     FIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 84.40.122.238 Dst ip: 81.155.44.58 Type: Redirect Code: Redirect Datagram for the Host
23:21:49  19 Feb     FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 93.166.164.176 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Port Unreacheable
23:20:16  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 92.249.108.10 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:17:59  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 67.187.177.56 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:10:56  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 112.186.95.87 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
23:06:16  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 74.5.128.18 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:50:57  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 77.41.30.72 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:49:03  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 76.103.104.179 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:41:12  19 Feb     SNTP Synchronised to server: 213.123.20.170
22:39:39  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 112.186.95.87 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:34:35  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 110.12.182.35 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:25:45  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 124.199.167.231 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:22:02  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 84.41.40.49 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:08:21  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 87.6.164.2 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
22:03:11  19 Feb     FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 58.121.224.28 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:50:19  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 195.91.170.50 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Port Unreacheable
21:49:16  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 195.91.170.50 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Port Unreacheable
21:41:12  19 Feb     SNTP Synchronised to server: 213.123.26.170
21:38:19  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 112.186.95.87 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:29:51  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 60.236.25.160 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:22:03  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 93.72.155.33 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:19:38  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 90.218.252.139 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:13:43  19 Feb     VOIP: [2.0A] [100] [] 404 Not Found - SIP message sent
21:13:43  19 Feb     VOIP: [2.0A] [100] [-] OPTIONS - SIP message received
21:09:39  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 121.163.157.227 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:05:42  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 93.72.155.33 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:03:53  19 Feb     FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 118.36.6.129 Dst ip: 81.155.44.58 Type: Destination Unreachable Code: Host Unreacheable
21:00:23  19 Feb     FIREWALL level changed to Disabled.

Message 6 of 34 (49,344 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

[ Edited ]
Options

‎21-02-2011 6h35 - edited ‎21-02-2011 12h48

any ideas  as to why my HH is trying to dial home so much ?

 

 

 
inetnum:      81.154.0.0 - 81.157.255.255
netname:      BT-CENTRAL-PLUS
descr:        IP pools
country:      GB
admin-c:      BTCP1-RIPE
tech-c:       BTCP1-RIPE
status:       ASSIGNED PA
mnt-by:       BTNET-MNT
mnt-lower:    BTNET-MNT
mnt-routes:   BTNET-MNT
source:       RIPE # Filtered

role:           BT CENTRAL PLUS - OPERATIONAL SUPPORT
address:        BT
address:        Wholesale
address:        UK
admin-c:        PC487-RIPE
tech-c:         SR401-RIPE
nic-hdl:        BTCP1-RIPE
mnt-by:         BTNET-MNT
source:         RIPE # Filtered

route:        81.128.0.0/11
descr:        BT Public Internet Service
origin:       AS2856
mnt-by:       BTNET-MNT
source:       RIPE # Filtered
http://whois.domaintools.com/81.155.44.58
Message 7 of 34 (49,285 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

Options

on ‎24-02-2011 14h52

The connections to the laptops have improved it would appear (no changes in hardware or software), however the wife's BT Mobile newly renewed bout a month ago is now dropping out.

 

To be honest i've lost count of the number of HH's ive gone through to date, 1.0, 1.5, 2.0's.

I might make a HH mountain and invite my neighbours to hit them with sledgehammers, at the speed they would travel would be faster than my broadband.

 

come payday I suspect I'll buy a non-BT wireless router that receives regular updates that dont call home every 10 minutes, apologies for being petty I just find this whole business so darn irritating.

Message 8 of 34 (49,168 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

Options

on ‎01-03-2011 21h49

Had to restart the HH twice this morning in the space of 2 hours due to lack of bandwidth, waiting on confirmation of engineer visit for monday 7th March 2011 (0800-1300)

wish me luck :smileyvery-happy:

Message 9 of 34 (49,044 Views)
 
Reply
Please use plain text.
 
Loxx
Contributor
Loxx
Posts: 31
Registered: ‎28-01-2010
0

Re: BT Home Hub nightmare

Options

on ‎07-03-2011 11h35

had a bt engineer that came out and changed the wireless channel, advising my neighbour was stealing all the bandwidth with his netgear router.

So thanks BT you will 1st prize in helpfulness, I wish i had never renewed contracts for both telephone, broadband and mobile, does customer loyality mean nothing to you ????

Message 10 of 34 (48,926 Views)
 
Reply
Please use plain text.