cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Aspiring Contributor
646 Views
Message 1 of 13

Keeping the router on

Short question - Have been told by Customer Support that my broadband speed will increase after a cleared line fault if I keep the router on (Home Hub 2). I currently have it set to power down at night under its power saving settings. Is this OK or does it need to be on all the time?

 

Long version - very low broadband speed.

Line fault 10/10/11, broadband down to 1.5M, no telephone. Fault rectified 22/10/11, broadband down to 1.3K, telephone working. No exchange outages. Ran a line check which was unable to complete and BT engineer turned up today. Replaced faulty master socket and line OK.

 

Speed still 1.3K so contacted online customer support who told me that the speed should increase after the line fault cleared if I keep the router switched on. Fingers crossed.

 

In case it makes more sense to anyone else, here comes the science bit!

 

BT Speed Test data 

Download speed 88Kbps

Acceptable range of speed 50-250Kbps

DSL connection rate 7232Kbps (Downstream) 448Kbs (Upstream)

IP Profile for line 135Kbps

 

BT Home Hub 2 Event Log

12:41:03   5 Nov
LOGIN User admin logged in on [HTTP] (from 192.168.1.67)
12:40:51   5 Nov
LOGIN User Basic logged in on [HTTP] (from 192.168.1.67)
12:34:57   5 Nov
CONFIGURATION saved by TR69
12:34:22   5 Nov
[CWMP] Connection Request NOT ALLOWED.
12:33:47   5 Nov
CONFIGURATION saved by TR69
12:33:17   5 Nov
[CWMP] Connection Request NOT ALLOWED.
12:02:33   5 Nov
IDS proto parser : udp null port (1 of 1) : 218.76.138.156 86.129.68.111 1500 UDP 0->0
12:00:58   5 Nov
CONFIGURATION saved by TR69
12:00:24   5 Nov
SNTP Synchronised to server: 213.123.26.170
12:00:24   5 Nov
SNTP Systemtime update: time setting 00:04:00 > new time setting: 12:00:24
00:03:58   1 Jan
FIREWALL event (1 of 9): deleted rules
00:03:57   1 Jan
PPP link up (Internet) [86.129.68.111]
00:03:57   1 Jan
PPP CHAP Chap receive success : authentication ok
00:03:57   1 Jan
PPP CHAP Receive challenge (rhost = ERX23.Manchester4)
00:03:53   1 Jan
FIREWALL event (1 of 15): modified rules
00:03:53   1 Jan
FIREWALL event (1 of 38): created rules
00:03:53   1 Jan
xDSL linestate up (ITU-T G.992.1; downstream: 7232 kbit/s, upstream: 448 kbit/s; output Power Down: 19.8 dBm, Up: 12.0 dBm; line Attenuation Down: 25.0 dB, Up: 14.0 dB; snr Margin Down: 22.0 dB, Up: 14.9 dB)
00:02:11   1 Jan
PPP link down (Internet) [86.129.71.143]
00:01:29   1 Jan
usbmgr: USB device isn't matched the configuration
00:01:29   1 Jan
usbmgr: try /etc/usbmgr/class/module
00:01:29   1 Jan
usbmgr: try /etc/usbmgr/class/09/module
00:01:29   1 Jan
usbmgr: try /etc/usbmgr/class/09/00/module
00:01:29   1 Jan
usbmgr: try /etc/usbmgr/class/09/00/00/module
00:01:29   1 Jan
usbmgr: class:0x9 subclass:0x0 protocol:0x0
00:01:29   1 Jan
usbmgr: buffer line: remove T
00:01:29   1 Jan
usbmgr: USB device isn't matched the configuration
00:01:28   1 Jan
usbmgr: try /etc/usbmgr/class/module
00:01:28   1 Jan
usbmgr: try /etc/usbmgr/class/09/module
00:01:28   1 Jan
usbmgr: try /etc/usbmgr/class/09/00/module
00:01:28   1 Jan
usbmgr: try /etc/usbmgr/class/09/00/00/module
00:01:28   1 Jan
usbmgr: class:0x9 subclass:0x0 protocol:0x0
00:01:28   1 Jan
usbmgr: buffer line: remove T
00:01:26   1 Jan
xDSL linestate down
00:01:02   1 Jan
PPP link up (Internet) [86.129.71.143]
00:01:02   1 Jan
PPP CHAP Chap receive success : authentication ok
00:01:01   1 Jan
PPP CHAP Receive challenge (rhost = ERX23.Manchester4)
00:00:57   1 Jan
xDSL linestate up (ITU-T G.992.1; downstream: 7200 kbit/s, upstream: 448 kbit/s; output Power Down: 19.8 dBm, Up: 12.0 dBm; line Attenuation Down: 25.0 dB, Up: 14.0 dB; snr Margin Down: 22.0 dB, Up: 14.9 dB)
00:00:53   1 Jan
DHCS server up
00:00:52   1 Jan
FIREWALL event (1 of 1): deleted rules
00:00:46   1 Jan
FIREWALL level changed to Standard.
00:00:41   1 Jan
FIREWALL event (1 of 1): modified rules
00:00:41   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 Cold restart


Software version 8.1.H.U (Type A) | Access
Click to activate accessibility mode
| Time and date  12:42:34  05/11/2011

 

Cheers,

Sean.


0 Ratings
12 REPLIES 12
Highlighted
Distinguished Sage
640 Views
Message 2 of 13

Re: Keeping the router on

Hi yes it is important to leave your hub turned on all the time however its power saving only turns off the wireless feature only so you are still connected to the internet and powered up just leave everything as it is and do not restart the hub manually and your ip profile will rise automatically
0 Ratings
Highlighted
Aspiring Contributor
639 Views
Message 3 of 13

Re: Keeping the router on

Cheers,
Fingers crossed...
0 Ratings
Highlighted
Distinguished Sage
634 Views
Message 4 of 13

Re: Keeping the router on

if after 5 days when you run the bt speedtest your ip profile (curently135k) has not risen then you need to contact the forum mods here and they can get it reset for you this is a link to them http://bt.custhelp.com/app/contact_email/c/4951
they normally reply by email or phone directly to you within 72 hours
better than using the help line
They are a UK based specialist team who have a good record at getting problems solved
Highlighted
Aspiring Contributor
622 Views
Message 5 of 13

Re: Keeping the router on

Many thanks John, appreciate that.
0 Ratings
Highlighted
Distinguished Sage
620 Views
Message 6 of 13

Re: Keeping the router on

No problems glad to help
0 Ratings
Highlighted
Aspiring Contributor
563 Views
Message 7 of 13

Re: Keeping the router on

Speed now up to almost 900K but line capable of 8M. Mods contacted for assistance, resetting IP profile etc.

 

Fingers crossed.

 

speedtest01.jpg

 

speedtest02.jpg

 

speedtest03.jpg

 

 

 

 

 

 

 

0 Ratings
Highlighted
Distinguished Sage
Distinguished Sage
560 Views
Message 8 of 13

Re: Keeping the router on

does your router show a connection time of greater than 5days or has there been disconnections during that period which has stopped the automatic process from increasing your profile?

 

profiles can get stuck but that normally is on 135 or 2000.



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’.
0 Ratings
Highlighted
Aspiring Contributor
544 Views
Message 9 of 13

Re: Keeping the router on

Connection time two days.

 

15:13:00  12 NovSNTP Synchronised to server: 213.123.20.170
14:34:01  12 NovFIREWALL replay check (1 of 1): Protocol: ICMP Src ip: 192.168.1.68 Dst ip: 217.32.171.21 Type: Destination Unreachable Code: Port Unreacheable
14:13:00  12 NovSNTP Synchronised again to server: 213.123.26.170
13:14:21  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:14:18  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:13:00  12 NovSNTP Synchronised to server: 213.123.26.170
13:10:42  12 NovUPnP action 'DeletePortMapping' from ip=192.168.1.69 (Success)
13:10:28  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:09:56  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:09:52  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:09:50  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:09:14  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:06:05  12 NovUPnP action 'DeletePortMapping' from ip=192.168.1.69 (Success)
13:05:32  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:05:15  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:05:05  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:05:00  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:04:57  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:04:55  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:04:18  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:03:46  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:03:01  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:02:58  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:02:55  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:02:16  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:01:33  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:01:30  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:01:27  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:00:45  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:00:36  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:00:31  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:00:28  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
13:00:26  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
12:59:46  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
12:59:02  12 NovUPnP action 'AddPortMapping' from ip=192.168.1.69 (Success)
12:22:42  12 NovCONFIGURATION saved by TR69
12:22:11  12 Nov[CWMP] Connection Request NOT ALLOWED.
12:21:59  12 NovCONFIGURATION saved by TR69
12:21:28  12 Nov[CWMP] Connection Request NOT ALLOWED.
12:12:59  12 NovSNTP Synchronised again to server: 213.123.20.170
11:36:23  12 NovCONFIGURATION saved by TR69
11:35:49  12 NovLOGIN User Basic logged in on [HTTP] (from 192.168.1.68)
11:35:35  12 Nov[CWMP] Connection Request NOT ALLOWED.
11:12:59  12 NovSNTP Synchronised to server: 213.123.20.170
10:12:59  12 NovSNTP Synchronised to server: 213.123.26.170
09:12:59  12 NovSNTP Synchronised again to server: 213.123.20.170
08:12:59  12 NovSNTP Synchronised to server: 213.123.20.170
07:12:59  12 NovSNTP Synchronised to server: 213.123.26.170
06:12:59  12 NovSNTP Synchronised again to server: 213.123.20.170
05:12:59  12 NovSNTP Synchronised to server: 213.123.20.170
04:12:58  12 NovSNTP Synchronised again to server: 213.123.26.170
03:12:58  12 NovSNTP Synchronised again to server: 213.123.26.170
02:12:58  12 NovSNTP Synchronised again to server: 213.123.26.170
01:12:58  12 NovSNTP Synchronised again to server: 213.123.26.170
00:12:58  12 NovSNTP Synchronised to server: 213.123.26.170
23:12:58  11 NovSNTP Synchronised to server: 213.123.20.170
23:05:18  11 NovFIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 88.52.147.151 Dst ip: 86.152.248.133 Type: Destination Unreachable Code: Host Unreacheable
23:04:15  11 NovFIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 195.32.95.179 Dst ip: 86.152.248.133 Type: Destination Unreachable Code: Host Unreacheable
22:12:58  11 NovSNTP Synchronised again to server: 213.123.26.170
21:12:58  11 NovSNTP Synchronised again to server: 213.123.26.170
20:12:57  11 NovSNTP Synchronised again to server: 213.123.26.170
19:12:57  11 NovSNTP Synchronised again to server: 213.123.26.170
18:12:57  11 NovSNTP Synchronised to server: 213.123.26.170
17:12:57  11 NovSNTP Synchronised to server: 213.123.20.170
17:08:34  11 NovCONFIGURATION saved by TR69
16:12:57  11 NovSNTP Synchronised again to server: 213.123.26.170
15:12:56  11 NovSNTP Synchronised to server: 213.123.26.170
14:12:56  11 NovSNTP Synchronised again to server: 213.123.20.170
13:12:56  11 NovSNTP Synchronised again to server: 213.123.20.170
12:12:56  11 NovSNTP Synchronised to server: 213.123.20.170
11:12:56  11 NovSNTP Synchronised again to server: 213.123.26.170
10:12:56  11 NovSNTP Synchronised again to server: 213.123.26.170
09:12:56  11 NovSNTP Synchronised to server: 213.123.26.170
08:12:56  11 NovSNTP Synchronised again to server: 213.123.20.170
07:12:55  11 NovSNTP Synchronised to server: 213.123.20.170
06:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
05:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
04:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
03:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
02:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
01:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
00:12:55  11 NovSNTP Synchronised again to server: 213.123.26.170
23:12:54  10 NovSNTP Synchronised again to server: 213.123.26.170
22:12:54  10 NovSNTP Synchronised again to server: 213.123.26.170
21:58:32  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
21:57:52  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
21:57:06  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
21:56:22  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
21:56:20  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
21:55:46  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
21:12:54  10 NovSNTP Synchronised to server: 213.123.26.170
20:46:48  10 NovUPnP action 'DeletePortMapping' from ip=192.168.1.78 (Success)
20:46:15  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
20:46:06  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
20:46:01  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
20:45:58  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
20:45:56  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
20:45:14  10 NovUPnP action 'AddPortMapping' from ip=192.168.1.78 (Success)
 
0 Ratings
Highlighted
Distinguished Sage
Distinguished Sage
541 Views
Message 10 of 13

Re: Keeping the router on

as only 2 days that explains why the automatic process has not increased your profile.  need a 24/7 connection for 3/5 days for automatic process to work.  just stay connected



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’.
0 Ratings