BT Broadband

[Jonboy]

Will mention the Iplate again here as a cheap method of helping to speed up ADSL connections. It has worked for both myself and several others on here for less than a tenner and five minutes fitting

 

Jon

[Mickey]

I must first confess that because an automatic exchange was installed in a nearby town some 26 years ago, that this small Lincolnshire village I live in has broadband at 7.6 mbps.

 

However my impoverished Daughter uses a Vodaphone dongle - bought by Dad of course - for her minimal Internet usage. The 'credit' has just dropped below £10 after five months usage - it started at £15 - and it prompts the question as to whether mobile networks should be taking advantage of this market opportunity.

 

No-one seriously expects fibre-optic cables giving 20+ mbps in our lifetime and many would presumably settle for the reliable 2.6/3.0 mbps that a pay-as-you-go dongle brings.

 

Other than viewing 'iplayer'and swopping big files, does anyone know of any major drawbacks with mobile networks ?

 

Bob

 

I have an Orange Dongle and it works perfectly well for the usual surfing stuff, when it will connect......Orange is the only mobile system that works at all out in the Wilds Of Woodhead so I cant comment on the other ones....

 

Im happy with the £14.99 per month rolling contract Orange have and also I believe that if you go a bit over the top watching You Tube or what ever then the maximum monthly charge is £40...

[RFS]

Will mention the Iplate again here as a cheap method of helping to speed up ADSL connections. It has worked for both myself and several others on here for less than a tenner and five minutes fitting

 

Jon

 

You need to first bypass the internal house wiring by plugging the broadband directly into the master socket first. If that makes no difference, then the internal extension wiring is not the issue and the Iplate will be of no use. Likewise if you have no internal extension wiring then the Iplate won't work.

 

Also look at your phone socket: if it says "Openreach" rather than "BT" then this later socket has the functions of the Iplate already built into its circuitry. Likewise if your face plate is an ADSL filtered one - ie you have two sockets, one for ADSL and one for the phone - it already has the Iplate function.

 

I bought an Iplate before I knew all this and it's now gathering dust in the loft somewhere.

 

As you're a BT customer they should send you one for free.

[Dagworth]

Progress update again

Today we have a reasonable connection, but my DSL rate has dropped from 2mb+ to 928k. can anyone who knows more about these things tell me why that might be? I'm going to add a speed test screen cap each day for the next few days to keep track of what happens.

[RFS]

If you connect during the day you'll likely get a faster sync speed than overnight. This is because medium-wave radio frequencies overlap those used by broadband and these become stronger at night due to atmospheric conditions, causing more line interference. I suspect you connected at 2016 during the day but this wasn't sustainable overnight.

 

Do you have any extension wiring in your house at all?

 

Can you get at the stats from your router? For example, line attenuation (in db, which will tell you how far you are from the Exchange) and noise margin (again in db, which says how strong the broadband signal is above the general noise on the line). As the noise increases after dark it can cause the broadband signal to become difficult to hold for the router. What happens then is BT will automatically increase the noise margin in 3 db steps to compensate. The default is 6 db, but if your line can't hold that after dark then it gets increased to 9 db, or 12 db. Although this can then stabilize the line, it's at the cost of a lower sync speed.

 

My line has a noise margin set at 9 db, which gives a sync speed of 4096 which it can hold pretty well all the time. I did once get BT to reset it to 6 db: it gave me 5 mb during the day but lost sync overnight and reverted to 4 mb.

 

Also some routers are better able to hold a noisy line than others. It would be worth your joining the broadband forum at http://www.thinkbroadband.com/ and posting your problem there as there are a lot of knowledgable people who may be able to help.

[Dagworth]

Both of the screen caps I've posted were at similar times of day. Over night last night I got a sync rate of 2300+

 

Hopefully this cap from the router info should give some more useful information

We are just over 4km from the exchange according to the BT engineers loop test data yesterday

[RFS]

Many routers, and I think the BT Home Hub is one of them, will report a maximum line attenuation of 63.5 db. What this means is that it could be higher than that: either you are on a very long line (more than 4 km) or you have a poor quality one with many aluminium joints which will increase line noise.

 

If the BT Engineer said your line was capable of 2 mbit then I'd get back to them and ask why it's only less than 1 Mbit.

[Lady_Ava_Hay]

The phone and broadband market is actually quite fragmented. I used to work for a cable company (now Virgin, previously Nynex, then Cable and Wireless, then.....). this was before general use of ADSL and the market was hot for second lines for dial up.

 

I had to sign up for BT when I moved to a new flat 3 years ago. I always feel that they rip new connections off at £128+ for wiring up pre installed new build because Virgin Media (ex Telewest, ex....) haven't done any new installs in this area for six years so BT get their monopoly back.

 

I could shoot out the windows of my exchange with an airgun (and did threaten to during the install process) but there is no guarantee that the server is in there anyway.

 

I have never tested my line speed but am pretty sure that it was in the 500's Kbs/sec most of the time. Recently, there has been an upgrade on my server (Utilities Warehouse) and the speeds are noticeably higher since although the loss of E Mail for three days was not pleasing and only after I contacted my server was I told about the upgrade at all.

 

I had no real trouble with BT but I have noticed, as an aside, that since I have left them the incidence of nuisance calls from foreign climes about my mortgage ( I pay rent) has stopped. I am fairly convinced that the outsourcing of data to foreign climes is not very well controlled. BT is one of the last to do this. If you look on your contract, they have to tell you that data processing is carried out outside the EU. If everybody saw that and voted with their feet, it would stop very quickly. BT might be a monopoly in new connections but these days, phone service providers are two a penny. I get the distinct impression that all ISP's are a bit rubbish in the service area and that BT's advantage in providing the line as well means very little since they have had to allow other ISPs to add digital overlay servers in key exchanges.

[Danemouth]

Keep an eye out for BT Infinity becoming available in your area - that's fibre to the cabinet.

 

I was part of the trial so I've had 20 mb for 12 months. A colleague living in a village up the road has just got it - jumped from 400 kb to 19 mb

 

Regards,

 

Dave

[Dagworth]

grrrrrrrrrrrrrrrrrrrrrrrrrrrrr!

 

back to 106kbps

[Dagworth]

Noise on the line?

[RFS]

Noise on the line?

Your downsteam noise margin is a massive 22 db. Sounds like some noise issue caused it to drop to 135 kbps and that issue has gone away. Try forcing a re-sync - unplug the BT Home Hub from the telephone line, wait for the broadband light to go out, and plug back in again.

[Tony_S]

Your downsteam noise margin is a massive 22 db. Sounds like some noise issue caused it to drop to 160 kbps and that issue haas gone away. Try forcing a re-sync - unplug the BT Home Hub from the telephone line, wait for the broadband light to go out, and plug back in again.

 

 

 

I hope Andi manages to get his broadband speed sorted but your suggestion of forcing a re-sync worked for me. The line was only running at about half my normal speed and nothing seemed to get it to reconnect at it's previous rate. I followed your instruction of removing the ADSL lead until the light went out, re connected ran speed test and all is much better now.

 

Many thanks

 

Tony

 

 

[Dagworth]

Forcing a re-sync has cleared the noise margin down to 9.1dB and allowed the DSL rate to rise to 1920 kbps. Thanks for that tip, it looks like that is the cause of the problem. Hopefully BT will now be able to find out why the noise margin rises to such a high level.

Now I have the problem though of the IP profile for the line. This is still sat at 135kbps today and that won't update for 24 hours. grrrrrrr!

 

Andi

[Dagworth]

todays results AFTER the re-sync. I wish I'd looked at the data for the hub before forcing it to re-sync.

[mezzoman253]

Keep an eye out for BT Infinity becoming available in your area - that's fibre to the cabinet.

 

I was part of the trial so I've had 20 mb for 12 months. A colleague living in a village up the road has just got it - jumped from 400 kb to 19 mb

 

Regards,

 

Dave

 

Hi, Fibre would have been available in 1980's, but Mrs. Thatcher and Co decided to only allow certain privatised companies to put it in, blocking BT. Of course the other technology hadn't arrived that would give us the speeds we have now, but the network and local lines would have been fibre.

 

Rob

[Tony_S]

Our local exchange went to ADSL2 a month ago. Before that we reliably got 6.6Mbps but it has been a bit erratic (and usually half the previous speed!) since, though to be fair BT did say it could be so for a while. It was very slow for a few days but after trying the re-sync as suggested by RFS these are the results now,

 

 

 

Tony

[RFS]

Forcing a re-sync has cleared the noise margin down to 9.1dB and allowed the DSL rate to rise to 1920 kbps. Thanks for that tip, it looks like that is the cause of the problem. Hopefully BT will now be able to find out why the noise margin rises to such a high level.

Now I have the problem though of the IP profile for the line. This is still sat at 135kbps today and that won't update for 24 hours. grrrrrrr!

 

Andi

 

Looks to me as though you line is set to sync with a noise margin of 9 db - ie it will sync at the highest speed pssible whilst preserving that margin. The default is 6 db but it would appear your line needs a bit more margin than that - more or less normal for longer lines. Although I sync at 4096 my margin is currently 12 db.

 

I suspect you had some interference which caused loss of sync: when the hub tried to reconnect, the best it could do was 136 whilst preserving the 9 db margin, due to the noise on the line at the time. When the interference went away, the margin increased to 22 db simply due to the low sync speed. Hence forcing a re-sync got you a better speed.

 

You could try looking at the log on the home hub to see when this happened. When I was having a lot of issues I considered putting the hub on to a time switch so that it powered off at midnight and back on at 7am, but in the end the line stablized.

 

Perish the thought, but it's not some model railway equipment causing the interference?

[Dagworth]

Looks to me as though you line is set to sync with a noise margin of 9 db - ie it will sync at the highest speed pssible whilst preserving that margin. The default is 6 db but it would appear your line needs a bit more margin than that - more or less normal for longer lines. Although I sync at 4096 my margin is currently 12 db.

 

I suspect you had some interference which caused loss of sync: when the hub tried to reconnect, the best it could do was 136 whilst preserving the 9 db margin, due to the noise on the line at the time. When the interference went away, the margin increased to 22 db simply due to the low sync speed. Hence forcing a re-sync got you a better speed.

 

You could try looking at the log on the home hub to see when this happened. When I was having a lot of issues I considered putting the hub on to a time switch so that it powered off at midnight and back on at 7am, but in the end the line stablized.

 

Perish the thought, but it's not some model railway equipment causing the interference?

 

Being as I have not switched anything model railway related on for a few days I don't think its the trains causing the problem...

I can see the log from the router but I don't know what in particular I'm looking for or at what time my speed changed, as that happened while the PC was off and I was asleep.

 

I have such items as

11:44:12 22 Jun [CWMP] Connection Request NOT ALLOWED.

and

00:26:00 22 Jun SNTP Roundtrip exceeds limits

00:25:57 22 Jun SNTP Invalid response from server (IP address)

in the log

 

I'm not sure how wise it would be to copy the full log here, do the server IP addresses etc. identify my PC?

Andi

[RFS]

When you browse the log you can select what class of messages you want to see, one of which is connections. At least I believe that's the name as I recently replaced my home hub with a Netgear DG834GT router off Ebay. You will then just see the re-sync connections and the message will include the speed and noise margin details at the time. Assuming you keep the hub on all the time then it will have stored the connection messages in its internal log, even though your PC is switched off.

 

Not sure what these messages of yours mean: I don't remember seeing this type of message in my log when I was having problems. The hub will tell you what IP address you have and you can check if that's the same in the message, or whether the IP address in the message is the BT server at the Exchange.

[Dagworth]

This is the log of all events from when I last reset the hub which was prior to the BT engineers visit at 10:40 on the 18th of June. I've knocked out references to IP addresses other than the BT server and my own address within the home network.

17:55:36 22 Jun LOGIN User admin logged in on [HTTP] (from 192.168.1.66)

17:55:26 22 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

17:26:18 22 Jun SNTP Synchronised to server: 213.123.26.170

17:20:34 22 Jun LOGIN User admin logged in on [HTTP] (from 192.168.1.66)

17:20:21 22 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

16:26:18 22 Jun SNTP Synchronised again to server: 213.123.20.170

15:26:18 22 Jun SNTP Synchronised to server: 213.123.20.170

14:26:18 22 Jun SNTP Synchronised to server: 213.123.26.170

13:26:18 22 Jun SNTP Synchronised to server: 213.123.20.170

12:26:17 22 Jun SNTP Synchronised to server: 213.123.26.170

11:44:37 22 Jun CONFIGURATION saved by TR69

11:44:12 22 Jun [CWMP] Connection Request NOT ALLOWED.

11:37:30 22 Jun LOGIN User admin logged in on [HTTP] (from 192.168.1.66)

11:37:19 22 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

11:36:01 22 Jun FIREWALL event (1 of 1): deleted rules

11:36:01 22 Jun xDSL linestate up (ITU-T G.992.1; downstream: 1920 kbit/s, upstream: 448 kbit/s; output Power Down: 17.1 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 14.0 dB, Up: 9.2 dB)

11:35:41 22 Jun FIREWALL event (1 of 1): created rules

11:35:41 22 Jun xDSL linestate down

11:26:17 22 Jun SNTP Synchronised to server: 213.123.20.170

10:26:16 22 Jun SNTP Synchronised again to server: 213.123.26.170

09:26:16 22 Jun SNTP Synchronised to server: 213.123.26.170

08:26:16 22 Jun SNTP Synchronised again to server: 213.123.20.170

07:26:16 22 Jun SNTP Synchronised again to server: 213.123.20.170

06:26:16 22 Jun SNTP Synchronised to server: 213.123.20.170

05:26:15 22 Jun SNTP Synchronised to server: 213.123.26.170

04:26:15 22 Jun SNTP Roundtrip exceeds limits

04:26:12 22 Jun SNTP Invalid response from server 213.123.26.170

03:26:03 22 Jun SNTP Synchronised to server: 213.123.26.170

02:26:03 22 Jun SNTP Synchronised to server: 213.123.20.170

02:20:10 22 Jun CONFIGURATION saved by TR69

01:26:02 22 Jun SNTP Synchronised to server: 213.123.26.170

00:26:00 22 Jun SNTP Roundtrip exceeds limits

00:25:57 22 Jun SNTP Invalid response from server 213.123.26.170

00:08:48 22 Jun LOGIN User admin logged in on [HTTP] (from 192.168.1.66)

00:08:37 22 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

00:03:03 22 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

00:03:03 22 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

00:03:01 22 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

23:25:49 21 Jun SNTP Synchronised to server: 213.123.26.170

22:25:49 21 Jun SNTP Synchronised to server: 213.123.20.170

21:25:49 21 Jun SNTP Synchronised again to server: 213.123.26.170

20:25:49 21 Jun SNTP Synchronised again to server: 213.123.26.170

19:25:49 21 Jun SNTP Synchronised again to server: 213.123.26.170

18:25:48 21 Jun SNTP Synchronised to server: 213.123.26.170

17:25:48 21 Jun SNTP Synchronised to server: 213.123.20.170

16:25:48 21 Jun SNTP Synchronised again to server: 213.123.26.170

15:25:48 21 Jun SNTP Synchronised again to server: 213.123.26.170

14:25:48 21 Jun SNTP Synchronised again to server: 213.123.26.170

13:25:47 21 Jun SNTP Synchronised again to server: 213.123.26.170

12:25:47 21 Jun SNTP Synchronised again to server: 213.123.26.170

12:08:02 21 Jun CONFIGURATION saved by TR69

12:07:36 21 Jun [CWMP] Connection Request NOT ALLOWED.

11:25:47 21 Jun SNTP Synchronised to server: 213.123.26.170

10:25:47 21 Jun SNTP Synchronised to server: 213.123.20.170

09:25:47 21 Jun SNTP Synchronised again to server: 213.123.26.170

08:25:47 21 Jun SNTP Synchronised again to server: 213.123.26.170

07:25:46 21 Jun SNTP Synchronised to server: 213.123.26.170

06:25:46 21 Jun SNTP Synchronised to server: 213.123.20.170

05:25:46 21 Jun SNTP Synchronised again to server: 213.123.26.170

04:25:46 21 Jun SNTP Synchronised again to server: 213.123.26.170

03:25:46 21 Jun SNTP Synchronised again to server: 213.123.26.170

02:25:46 21 Jun SNTP Synchronised to server: 213.123.26.170

02:20:10 21 Jun CONFIGURATION saved by TR69

01:25:45 21 Jun SNTP Synchronised to server: 213.123.20.170

00:25:45 21 Jun SNTP Synchronised to server: 213.123.26.170

23:25:45 20 Jun SNTP Synchronised again to server: 213.123.20.170

22:25:45 20 Jun SNTP Synchronised to server: 213.123.20.170

21:25:45 20 Jun SNTP Synchronised again to server: 213.123.26.170

20:25:44 20 Jun SNTP Synchronised to server: 213.123.26.170

19:25:44 20 Jun SNTP Synchronised to server: 213.123.20.170

18:25:44 20 Jun SNTP Synchronised again to server: 213.123.26.170

17:25:44 20 Jun SNTP Synchronised again to server: 213.123.26.170

16:57:02 20 Jun FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: xx.xx.xx.xx Dst ip: xx.xx.xx.xx Type: Destination Unreachable Code: Host Unreacheable

16:25:44 20 Jun SNTP Synchronised again to server: 213.123.26.170

15:25:44 20 Jun SNTP Synchronised again to server: 213.123.26.170

14:25:43 20 Jun SNTP Synchronised again to server: 213.123.26.170

13:25:43 20 Jun SNTP Synchronised again to server: 213.123.26.170

12:25:43 20 Jun SNTP Synchronised to server: 213.123.26.170

11:25:43 20 Jun SNTP Synchronised to server: 213.123.20.170

10:25:43 20 Jun SNTP Synchronised again to server: 213.123.26.170

09:25:42 20 Jun SNTP Synchronised again to server: 213.123.26.170

08:25:42 20 Jun SNTP Synchronised again to server: 213.123.26.170

07:25:42 20 Jun SNTP Synchronised to server: 213.123.26.170

06:25:42 20 Jun SNTP Synchronised to server: 213.123.20.170

05:25:42 20 Jun SNTP Synchronised again to server: 213.123.26.170

04:25:42 20 Jun SNTP Synchronised again to server: 213.123.26.170

04:16:10 20 Jun FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: xx.xx.xx.xx Dst ip: xx.xx.xx.xx Type: Destination Unreachable Code: Port Unreacheable

04:06:18 20 Jun FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: xx.xx.xx.xx Dst ip: xx.xx.xx.xx Type: Destination Unreachable Code: Port Unreacheable

03:25:41 20 Jun SNTP Synchronised again to server: 213.123.26.170

02:54:06 20 Jun CONFIGURATION saved by TR69

02:53:40 20 Jun FIREWALL event (1 of 1): deleted rules

02:53:39 20 Jun PPP link up (Internet) [xx.xx.xx.xx]

02:53:39 20 Jun PPP CHAP Chap receive success : authentication ok

02:53:39 20 Jun PPP CHAP Receive challenge (rhost = ERX15.Reading3)

02:53:34 20 Jun xDSL linestate up (ITU-T G.992.1; downstream: 160 kbit/s, upstream: 448 kbit/s; output Power Down: 11.6 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 9.1 dB)

02:53:02 20 Jun xDSL linestate down

02:52:46 20 Jun xDSL linestate down

02:52:14 20 Jun xDSL linestate down

02:51:42 20 Jun xDSL linestate down

02:51:27 20 Jun xDSL linestate down

02:50:55 20 Jun xDSL linestate down

02:50:23 20 Jun xDSL linestate down

02:50:08 20 Jun xDSL linestate down

02:49:36 20 Jun xDSL linestate down

02:49:05 20 Jun xDSL linestate down

02:48:50 20 Jun xDSL linestate down

02:48:18 20 Jun xDSL linestate down

02:47:46 20 Jun xDSL linestate down

02:47:30 20 Jun xDSL linestate down

02:46:58 20 Jun xDSL linestate down

02:46:26 20 Jun xDSL linestate down

02:46:11 20 Jun xDSL linestate down

02:45:39 20 Jun xDSL linestate down

02:45:07 20 Jun xDSL linestate down

02:44:52 20 Jun xDSL linestate down

02:44:20 20 Jun xDSL linestate down

02:43:48 20 Jun xDSL linestate down

02:43:33 20 Jun xDSL linestate down

02:43:02 20 Jun xDSL linestate down

02:42:30 20 Jun xDSL linestate down

02:42:14 20 Jun xDSL linestate down

02:41:43 20 Jun xDSL linestate down

02:41:11 20 Jun xDSL linestate down

02:40:56 20 Jun xDSL linestate down

02:40:24 20 Jun xDSL linestate down

02:39:52 20 Jun xDSL linestate down

02:39:37 20 Jun xDSL linestate down

02:39:05 20 Jun xDSL linestate down

02:38:33 20 Jun xDSL linestate down

02:38:18 20 Jun xDSL linestate down

02:37:46 20 Jun xDSL linestate down

02:37:15 20 Jun xDSL linestate down

02:36:59 20 Jun xDSL linestate down

02:36:27 20 Jun xDSL linestate down

02:35:55 20 Jun xDSL linestate down

02:35:40 20 Jun xDSL linestate down

02:35:08 20 Jun xDSL linestate down

02:34:37 20 Jun xDSL linestate down

02:34:33 20 Jun PPP link down (Internet) [xx.xx.xx.xx]

02:34:20 20 Jun xDSL linestate down

02:33:50 20 Jun FIREWALL event (1 of 1): created rules

02:33:49 20 Jun xDSL linestate down

02:25:41 20 Jun SNTP Synchronised to server: 213.123.26.170

02:20:09 20 Jun CONFIGURATION saved by TR69

02:08:05 20 Jun FIREWALL event (1 of 2): deleted rules

02:08:05 20 Jun xDSL linestate up (ITU-T G.992.1; downstream: 384 kbit/s, upstream: 448 kbit/s; output Power Down: 14.2 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 9.1 dB)

02:07:36 20 Jun FIREWALL event (1 of 2): created rules

02:07:36 20 Jun xDSL linestate down

02:02:44 20 Jun CONFIGURATION saved by TR69

02:02:13 20 Jun PPP link up (Internet) [xx.xx.xx.xx]

02:02:13 20 Jun PPP CHAP Chap receive success : authentication ok

02:02:13 20 Jun PPP CHAP Receive challenge (rhost = ERX15.Reading3)

02:02:00 20 Jun PPP link down (Internet) [xx.xx.xx.xx]

02:01:54 20 Jun FIREWALL event (1 of 1): deleted rules

02:01:53 20 Jun xDSL linestate up (ITU-T G.992.1; downstream: 352 kbit/s, upstream: 448 kbit/s; output Power Down: 13.8 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 9.0 dB)

02:01:21 20 Jun FIREWALL event (1 of 1): created rules

02:01:20 20 Jun xDSL linestate down

01:25:41 20 Jun SNTP Synchronised to server: 213.123.20.170

01:09:20 20 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

01:09:19 20 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

01:09:17 20 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

01:05:00 20 Jun FIREWALL event (1 of 2): deleted rules

01:05:00 20 Jun xDSL linestate up (ITU-T G.992.1; downstream: 416 kbit/s, upstream: 448 kbit/s; output Power Down: 14.6 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 9.1 dB)

01:04:41 20 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

01:04:40 20 Jun FIREWALL event (1 of 2): created rules

01:04:40 20 Jun xDSL linestate down

00:25:41 20 Jun SNTP Synchronised again to server: 213.123.26.170

23:25:41 19 Jun SNTP Synchronised again to server: 213.123.26.170

22:25:41 19 Jun SNTP Synchronised again to server: 213.123.26.170

22:13:18 19 Jun LOGIN User admin logged in on [HTTP] (from 192.168.1.66)

22:12:55 19 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

21:25:40 19 Jun SNTP Synchronised again to server: 213.123.26.170

20:25:40 19 Jun SNTP Synchronised again to server: 213.123.26.170

19:26:51 19 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

19:26:50 19 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

19:26:48 19 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

19:25:40 19 Jun SNTP Synchronised to server: 213.123.26.170

18:25:40 19 Jun SNTP Synchronised to server: 213.123.20.170

17:25:40 19 Jun SNTP Synchronised again to server: 213.123.26.170

16:25:40 19 Jun SNTP Synchronised again to server: 213.123.26.170

15:25:40 19 Jun SNTP Synchronised again to server: 213.123.26.170

14:25:40 19 Jun SNTP Synchronised to server: 213.123.26.170

13:25:39 19 Jun SNTP Roundtrip exceeds limits

12:25:33 19 Jun SNTP Roundtrip exceeds limits

11:25:31 19 Jun SNTP Synchronised again to server: 213.123.26.170

11:18:18 19 Jun CONFIGURATION saved by TR69

11:17:53 19 Jun [CWMP] Connection Request NOT ALLOWED.

10:25:30 19 Jun SNTP Synchronised to server: 213.123.26.170

09:25:30 19 Jun SNTP Synchronised to server: 213.123.20.170

08:25:30 19 Jun SNTP Synchronised to server: 213.123.26.170

07:49:43 19 Jun CONFIGURATION saved by TR69

07:49:13 19 Jun PPP link up (Internet) [xx.xx.xx.xx]

07:49:13 19 Jun PPP CHAP Chap receive success : authentication ok

07:49:12 19 Jun PPP CHAP Receive challenge (rhost = ERX15.Reading3)

07:48:59 19 Jun PPP link down (Internet) [xx.xx.xx.xx]

07:48:57 19 Jun FIREWALL event (1 of 1): deleted rules

07:48:57 19 Jun xDSL linestate up (ITU-T G.992.1; downstream: 928 kbit/s, upstream: 448 kbit/s; output Power Down: 16.2 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 14.0 dB, Up: 9.1 dB)

07:48:24 19 Jun FIREWALL event (1 of 1): created rules

07:48:24 19 Jun xDSL linestate down

07:25:30 19 Jun SNTP Synchronised to server: 213.123.20.170

06:25:30 19 Jun SNTP Synchronised again to server: 213.123.26.170

05:31:06 19 Jun FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: xx.xx.xx.xx Dst ip: xx.xx.xx.xx Type: Destination Unreachable Code: Port Unreacheable

05:25:30 19 Jun SNTP Synchronised again to server: 213.123.26.170

04:25:30 19 Jun SNTP Synchronised again to server: 213.123.26.170

04:19:58 19 Jun FIREWALL event (1 of 1): deleted rules

04:19:57 19 Jun xDSL linestate up (ITU-T G.992.1; downstream: 864 kbit/s, upstream: 448 kbit/s; output Power Down: 16.1 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 7.3 dB)

04:19:30 19 Jun FIREWALL event (1 of 1): created rules

04:19:29 19 Jun xDSL linestate down

03:25:29 19 Jun SNTP Synchronised again to server: 213.123.26.170

02:25:29 19 Jun SNTP Synchronised to server: 213.123.26.170

02:20:18 19 Jun CONFIGURATION saved by TR69

01:25:26 19 Jun SNTP Roundtrip exceeds limits

00:36:04 19 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

00:36:04 19 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

00:36:02 19 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

00:35:29 19 Jun FIREWALL event (1 of 1): deleted rules

00:35:29 19 Jun xDSL linestate up (ITU-T G.992.1; downstream: 1600 kbit/s, upstream: 448 kbit/s; output Power Down: 16.6 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 6.1 dB)

00:34:52 19 Jun FIREWALL event (1 of 1): created rules

00:34:52 19 Jun xDSL linestate down

00:25:24 19 Jun SNTP Synchronised to server: 213.123.20.170

23:25:24 18 Jun SNTP Synchronised to server: 213.123.26.170

22:34:00 18 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

22:33:59 18 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

22:33:57 18 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

22:25:19 18 Jun SNTP Roundtrip exceeds limits

22:25:18 18 Jun SNTP Invalid response from server 213.123.26.170

21:25:11 18 Jun SNTP Synchronised again to server: 213.123.26.170

20:25:11 18 Jun SNTP Synchronised again to server: 213.123.26.170

19:31:30 18 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

19:31:30 18 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

19:31:28 18 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

19:25:11 18 Jun SNTP Synchronised to server: 213.123.26.170

18:25:11 18 Jun SNTP Synchronised to server: 213.123.20.170

17:39:28 18 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

17:39:28 18 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

17:39:26 18 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

17:25:10 18 Jun SNTP Synchronised to server: 213.123.26.170

16:25:10 18 Jun SNTP Synchronised again to server: 213.123.20.170

15:25:10 18 Jun SNTP Synchronised to server: 213.123.20.170

14:25:10 18 Jun SNTP Synchronised to server: 213.123.26.170

13:46:29 18 Jun FIREWALL event (1 of 1): deleted rules

13:46:29 18 Jun xDSL linestate up (ITU-T G.992.1; downstream: 2368 kbit/s, upstream: 448 kbit/s; output Power Down: 17.3 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 6.4 dB)

13:46:16 18 Jun FIREWALL event (1 of 1): created rules

13:46:16 18 Jun xDSL linestate down

13:25:10 18 Jun SNTP Synchronised to server: 213.123.20.170

13:15:33 18 Jun CONFIGURATION saved by TR69

13:14:51 18 Jun [CWMP] Connection Request NOT ALLOWED.

12:53:22 18 Jun FIREWALL event (1 of 1): deleted rules

12:53:22 18 Jun PPP link up (Internet) [xx.xx.xx.xx]

12:53:22 18 Jun PPP CHAP Chap receive success : authentication ok

12:53:22 18 Jun PPP CHAP Receive challenge (rhost = ERX15.Reading3)

12:53:03 18 Jun xDSL linestate up (ITU-T G.992.1; downstream: 2016 kbit/s, upstream: 448 kbit/s; output Power Down: 17.1 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 14.0 dB, Up: 9.3 dB)

12:52:37 18 Jun PPP link down (Internet) [xx.xx.xx.xx]

12:52:14 18 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

12:51:52 18 Jun FIREWALL event (1 of 1): created rules

12:51:52 18 Jun xDSL linestate down

12:25:10 18 Jun SNTP Synchronised to server: 213.123.26.170

11:29:34 18 Jun CONFIGURATION saved by TR69

11:28:47 18 Jun FIREWALL event (1 of 1): deleted rules

11:28:47 18 Jun PPP link up (Internet) [xx.xx.xx.xx]

11:28:47 18 Jun PPP CHAP Chap receive success : authentication ok

11:28:46 18 Jun PPP CHAP Receive challenge (rhost = ERX15.Reading3)

11:28:37 18 Jun xDSL linestate up (ITU-T G.992.1; downstream: 2016 kbit/s, upstream: 448 kbit/s; output Power Down: 17.1 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 15.0 dB, Up: 9.4 dB)

11:25:09 18 Jun SNTP Unable to contact server: xx.xx.xx.xx

10:41:39 18 Jun PPP link down (Internet) [xx.xx.xx.xx]

10:40:56 18 Jun FIREWALL event (1 of 1): created rules

10:40:56 18 Jun xDSL linestate down

10:24:24 18 Jun SNTP Synchronised to server: 213.123.20.170

09:24:24 18 Jun SNTP Synchronised again to server: 213.123.26.170

08:24:23 18 Jun SNTP Synchronised again to server: 213.123.26.170

07:24:23 18 Jun SNTP Synchronised again to server: 213.123.26.170

06:24:23 18 Jun SNTP Synchronised again to server: 213.123.26.170

05:24:23 18 Jun SNTP Synchronised again to server: 213.123.26.170

04:24:23 18 Jun SNTP Synchronised again to server: 213.123.26.170

03:24:23 18 Jun SNTP Synchronised again to server: 213.123.26.170

02:24:22 18 Jun SNTP Synchronised to server: 213.123.26.170

02:20:08 18 Jun CONFIGURATION saved by TR69

01:24:22 18 Jun SNTP Synchronised to server: 213.123.20.170

00:24:22 18 Jun SNTP Synchronised again to server: 213.123.26.170

23:51:12 17 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

23:51:12 17 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

23:51:10 17 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

23:24:22 17 Jun SNTP Synchronised to server: 213.123.26.170

22:24:22 17 Jun SNTP Synchronised again to server: 213.123.20.170

21:24:22 17 Jun SNTP Synchronised to server: 213.123.20.170

20:24:21 17 Jun SNTP Synchronised again to server: 213.123.26.170

19:24:21 17 Jun SNTP Synchronised to server: 213.123.26.170

18:24:21 17 Jun SNTP Synchronised to server: 213.123.20.170

17:24:21 17 Jun SNTP Synchronised to server: 213.123.26.170

16:24:21 17 Jun SNTP Synchronised to server: 213.123.20.170

15:24:20 17 Jun SNTP Synchronised again to server: 213.123.26.170

14:24:20 17 Jun SNTP Synchronised to server: 213.123.26.170

13:24:20 17 Jun SNTP Synchronised to server: 213.123.20.170

12:24:20 17 Jun SNTP Synchronised to server: 213.123.26.170

11:24:20 17 Jun SNTP Synchronised to server: 213.123.20.170

10:24:20 17 Jun SNTP Synchronised again to server: 213.123.26.170

09:24:19 17 Jun SNTP Synchronised again to server: 213.123.26.170

08:24:19 17 Jun SNTP Synchronised again to server: 213.123.26.170

07:24:19 17 Jun SNTP Synchronised to server: 213.123.26.170

06:24:19 17 Jun SNTP Synchronised again to server: 213.123.20.170

05:24:19 17 Jun SNTP Synchronised to server: 213.123.20.170

04:24:19 17 Jun SNTP Synchronised again to server: 213.123.26.170

03:24:18 17 Jun SNTP Synchronised to server: 213.123.26.170

02:46:19 17 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

02:46:19 17 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

02:46:17 17 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

02:44:23 17 Jun FIREWALL event (1 of 7): deleted rules

02:44:23 17 Jun xDSL linestate up (ITU-T G.992.1; downstream: 256 kbit/s, upstream: 448 kbit/s; output Power Down: 12.8 dBm, Up: 11.9 dBm; line Attenuation Down: 63.5 dB, Up: 31.5 dB; snr Margin Down: 14.0 dB, Up: 9.6 dB)

02:44:04 17 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

02:44:03 17 Jun LOGIN User Basic logged in on [HTTP] (from 192.168.1.66)

02:43:55 17 Jun FIREWALL event (1 of 29): created rules

02:43:55 17 Jun xDSL linestate down

02:24:18 17 Jun SNTP Synchronised to server: 213.123.20.170

02:20:13 17 Jun CONFIGURATION saved by TR69

01:24:18 17 Jun SNTP Synchronised again to server: 213.123.26.170

00:24:18 17 Jun SNTP Synchronised again to server: 213.123.26.170

23:34:56 16 Jun UPnP action 'DeletePortMapping' from ip=192.168.1.66 (Success)

23:34:56 16 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

23:34:53 16 Jun UPnP action 'AddPortMapping' from ip=192.168.1.66 (Success)

23:24:18 16 Jun SNTP Synchronised again to server: 213.123.26.170

22:24:18 16 Jun SNTP Synchronised again to server: 213.123.26.170

21:24:17 16 Jun SNTP Synchronised to server: 213.123.26.170

20:24:14 16 Jun SNTP Roundtrip exceeds limits

20:24:11 16 Jun SNTP Invalid response from server 213.123.26.170

19:24:03 16 Jun SNTP Synchronised to server: 213.123.26.170

18:24:00 16 Jun SNTP Roundtrip exceeds limits

18:23:58 16 Jun SNTP Invalid response from server 213.123.26.170

17:38:58 16 Jun IDS scan parser : tcp port scan: xx.xx.xx.xx scanned at least 10 ports at xx.xx.xx.xx. (1 of 1) :xx.xx.xx.xx xx.xx.xx.xx 0040 TCP 80->57020 [...R..] seq 3219223401 win 0

17:23:49 16 Jun SNTP Synchronised to server: 213.123.26.170

16:23:49 16 Jun SNTP Synchronised again to server: 213.123.20.170

15:23:49 16 Jun SNTP Synchronised again to server: 213.123.20.170

14:37:43 16 Jun CONFIGURATION saved by TR69

14:37:18 16 Jun [CWMP] Connection Request NOT ALLOWED.

14:23:49 16 Jun SNTP Synchronised to server: 213.123.20.170

13:23:49 16 Jun SNTP Synchronised again to server: 213.123.26.170

12:23:49 16 Jun SNTP Synchronised again to server: 213.123.26.170

11:23:49 16 Jun SNTP Synchronised again to server: 213.123.26.170

10:23:48 16 Jun SNTP Synchronised again to server: 213.123.26.170

09:23:48 16 Jun SNTP Synchronised again to server: 213.123.26.170

08:23:48 16 Jun SNTP Synchronised to server: 213.123.26.170

07:23:48 16 Jun SNTP Synchronised to server: 213.123.20.170

06:23:48 16 Jun SNTP Synchronised again to server: 213.123.26.170

05:23:48 16 Jun SNTP Synchronised again to server: 213.123.26.170

04:23:48 16 Jun SNTP Synchronised again to server: 213.123.26.170

03:23:47 16 Jun SNTP Synchronised again to server: 213.123.26.170

02:23:47 16 Jun SNTP Synchronised to server: 213.123.26.170

02:23:47 16 Jun SNTP Systemtime update: time setting 01:04:04 > new time setting: 02:23:47

 

 

 

 

 

 

[eastwestdivide]

On the noise issue: we have two phone lines coming in, of which only one has broadband on it. When the non-broadband line failed, the BT engineer found a tiny gap in the insulation outside (their side of the box, so we didn't have to pay). Once that was fixed, the broadband speed increased on the line that hadn't failed.

Just worth a mention to show that interference/noise can come from unexpected sources.

[Lady_Ava_Hay]

Keep an eye out for BT Infinity becoming available in your area - that's fibre to the cabinet.

 

I was part of the trial so I've had 20 mb for 12 months. A colleague living in a village up the road has just got it - jumped from 400 kb to 19 mb

 

Regards,

 

Dave

 

This sort of fibre optic connection was vetoed when the cable was originally laid. The reason given is that if someone was to interfere with the fibre optic cable and look down the end of it they would be permanently blinded.

 

Don't be too quick to have this connection. Such bandwidth is a two way street and the utilities companies are able to hook up your meters and read them at will and cut you off as well plus they could install a webcam in your tele and spy on you 24/7.

[RFS]

You've definitely got some kind of noise issue on the line. At 02.34 on June 20th you lost connection altogether for nearly 40 minutes, and when it did connect it was only able to manage 160 kbps. Since it seems to be fluctuating wildly between this and, at one point, 2368 kbps, I'd get BT back to explain.

 

My line is stable now but 12 months ago it wasn't. BT changed the line from the house to the pole in the road outside, then the line from that to the street cabinet 1/2 mile up the road and finally from the street cabinet to the exchange. Took a while to get there but it's worth persevering.

[Dagworth]

You've definitely got some kind of noise issue on the line. At 02.34 on June 20th you lost connection altogether for nearly 40 minutes, and when it did connect it was only able to manage 160 kbps. Since it seems to be fluctuating wildly between this and, at one point, 2368 kbps, I'd get BT back to explain.

 

My line is stable now but 12 months ago it wasn't. BT changed the line from the house to the pole in the road outside, then the line from that to the street cabinet 1/2 mile up the road and finally from the street cabinet to the exchange. Took a while to get there but it's worth persevering.

I've got BT coming back AGAIN in the morning... 4th time lucky? Once again thanks so much for your help.

 

Andi