Download speed up during 'open questions', down again when closed
Hello Kevin! What are the crossed out lines for? 
Good morning. It's 24 hours later again. I was too tired to bother last night.
Oh. So things are still a bit up in the air then? I do have to say, that as the layman here, the error numbers don't mean an awful lot to me. I can relate to, say, a car that does 17mpg being one helluva lot less economical than one that does 50mpg, while from my own experiences I know that 18T rigid lorries do an average of about 14mpg of diesel and that's pretty good compared to a loaded artic!
Anyway, unfortunately the Technicolor log only currently goes back to half past four in the afternoon yesterday (15th April). As for Sunday night around 19:06, I cannot specifically remember what I was doing then but there is a good chance that I was online on my laptop. I can't remember any specific issues though. My attention may have been diverted by something else though (TV, text message etc). Kevin, I can't even see where you've got an event from 19.06 on Sunday from, from the data I've supplied!
That's how good I am at this 
Looking at the event log, if I log in I often get multiple Firewall icmp checks and events that say SNTP synchronised to server - sometimes with the word 'again' inserted.
I'll copy and paste the most recent log if that's any help.
Info Apr 16 09:07:55 LOGIN User admin logged in on
Error Apr 16 08:55:35 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 111.252.41.81 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 08:55:14 LOGIN User admin logged in on
Error Apr 16 08:48:39 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 31.45.13.34 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Communication Administratively Prohibited
Info Apr 16 08:38:07 LOGIN User admin logged in on
Info Apr 16 08:29:40 SNTP Synchronised again to server: 212.159.13.50
Error Apr 16 08:21:30 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 14.118.99.219 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 08:13:53 CONFIGURATION mbus igd sync successfull
Info Apr 16 08:13:50 CONFIGURATION mbus atomic sync successful
Info Apr 16 07:29:40 SNTP Synchronised to server: 212.159.13.50
Error Apr 16 07:13:59 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 70.244.182.175 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Error Apr 16 07:04:18 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 124.130.31.233 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Error Apr 16 06:36:46 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 187.91.162.155 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 06:29:39 SNTP Synchronised to server: 212.159.13.49
Info Apr 16 05:29:39 SNTP Synchronised again to server: 212.159.13.50
Error Apr 16 04:57:01 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 172.248.217.4 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 04:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 16 03:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 16 02:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 16 01:29:39 SNTP Synchronised to server: 212.159.13.49
Info Apr 16 00:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 15 23:29:39 SNTP Synchronised to server: 212.159.6.9
Info Apr 15 23:04:35 CONFIGURATION mbus igd sync successfull
Info Apr 15 23:04:31 CONFIGURATION mbus atomic sync successful
Error Apr 15 22:31:50 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 1.176.240.96 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 15 22:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 15 21:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 15 20:59:11 CONFIGURATION mbus igd sync successfull
Info Apr 15 20:59:07 CONFIGURATION mbus atomic sync successful
Info Apr 15 20:29:39 SNTP Synchronised to server: 212.159.6.9
Info Apr 15 19:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 15 18:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 15 17:29:39 SNTP Synchronised to server: 212.159.6.9
Error Apr 15 16:39:00 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 212.129.27.67 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Net Unreacheable
I am now starting to worry a bit about what I'm going to say next - although it has got to be remembered that from my point of view, my broadband is performing better than I've ever known, router switched on and off or not (now I'm not using an extension lead that I didn't know wasn't appropriate). About 7 or 8 years ago I had UPVC doors and windows fitted. I seem to remember something about the phone line getting slightly damaged when the old wooden front door frame was taken out; I think the original installation had the cable passing through a drilled hole in the wooden door frame. Now the cable comes into the house under the UPVC door step down in one corner, near the grey BT box outside. Whatever damage was done, the UPVC fitters 'made good' and I've never worried about it since my telephone works fine. Is it conceivable the errors you can see that are of concern could be something to do with that? And if that is the case, does that mean I'd have to pay for a BT engineer to sort it out? By all normal measurements (meaning I can't hear anything amiss doing a 'quiet line' test) there doesn't seem to be justification for suspecting a faulty line.
Oh. So things are still a bit up in the air then? I do have to say, that as the layman here, the error numbers don't mean an awful lot to me. I can relate to, say, a car that does 17mpg being one helluva lot less economical than one that does 50mpg, while from my own experiences I know that 18T rigid lorries do an average of about 14mpg of diesel and that's pretty good compared to a loaded artic!
Anyway, unfortunately the Technicolor log only currently goes back to half past four in the afternoon yesterday (15th April). As for Sunday night around 19:06, I cannot specifically remember what I was doing then but there is a good chance that I was online on my laptop. I can't remember any specific issues though. My attention may have been diverted by something else though (TV, text message etc). Kevin, I can't even see where you've got an event from 19.06 on Sunday from, from the data I've supplied!
That's how good I am at this Looking at the event log, if I log in I often get multiple Firewall icmp checks and events that say SNTP synchronised to server - sometimes with the word 'again' inserted.
I'll copy and paste the most recent log if that's any help.
Info Apr 16 09:07:55 LOGIN User admin logged in on
Error Apr 16 08:55:35 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 111.252.41.81 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 08:55:14 LOGIN User admin logged in on
Error Apr 16 08:48:39 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 31.45.13.34 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Communication Administratively Prohibited
Info Apr 16 08:38:07 LOGIN User admin logged in on
Info Apr 16 08:29:40 SNTP Synchronised again to server: 212.159.13.50
Error Apr 16 08:21:30 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 14.118.99.219 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 08:13:53 CONFIGURATION mbus igd sync successfull
Info Apr 16 08:13:50 CONFIGURATION mbus atomic sync successful
Info Apr 16 07:29:40 SNTP Synchronised to server: 212.159.13.50
Error Apr 16 07:13:59 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 70.244.182.175 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Error Apr 16 07:04:18 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 124.130.31.233 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Error Apr 16 06:36:46 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 187.91.162.155 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 06:29:39 SNTP Synchronised to server: 212.159.13.49
Info Apr 16 05:29:39 SNTP Synchronised again to server: 212.159.13.50
Error Apr 16 04:57:01 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 172.248.217.4 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 16 04:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 16 03:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 16 02:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 16 01:29:39 SNTP Synchronised to server: 212.159.13.49
Info Apr 16 00:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 15 23:29:39 SNTP Synchronised to server: 212.159.6.9
Info Apr 15 23:04:35 CONFIGURATION mbus igd sync successfull
Info Apr 15 23:04:31 CONFIGURATION mbus atomic sync successful
Error Apr 15 22:31:50 FIREWALL icmp check (1 of 1): Protocol: ICMP Src ip: 1.176.240.96 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Port Unreacheable
Info Apr 15 22:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 15 21:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 15 20:59:11 CONFIGURATION mbus igd sync successfull
Info Apr 15 20:59:07 CONFIGURATION mbus atomic sync successful
Info Apr 15 20:29:39 SNTP Synchronised to server: 212.159.6.9
Info Apr 15 19:29:39 SNTP Synchronised again to server: 212.159.13.50
Info Apr 15 18:29:39 SNTP Synchronised to server: 212.159.13.50
Info Apr 15 17:29:39 SNTP Synchronised to server: 212.159.6.9
Error Apr 15 16:39:00 FIREWALL icmp check (1 of 2): Protocol: ICMP Src ip: 212.129.27.67 Dst ip: 87.113.211.72 Type: Destination Unreachable Code: Net Unreacheable
I am now starting to worry a bit about what I'm going to say next - although it has got to be remembered that from my point of view, my broadband is performing better than I've ever known, router switched on and off or not (now I'm not using an extension lead that I didn't know wasn't appropriate). About 7 or 8 years ago I had UPVC doors and windows fitted. I seem to remember something about the phone line getting slightly damaged when the old wooden front door frame was taken out; I think the original installation had the cable passing through a drilled hole in the wooden door frame. Now the cable comes into the house under the UPVC door step down in one corner, near the grey BT box outside. Whatever damage was done, the UPVC fitters 'made good' and I've never worried about it since my telephone works fine. Is it conceivable the errors you can see that are of concern could be something to do with that? And if that is the case, does that mean I'd have to pay for a BT engineer to sort it out? By all normal measurements (meaning I can't hear anything amiss doing a 'quiet line' test) there doesn't seem to be justification for suspecting a faulty line.
Quote from: Townman ............FEC are errors which can be corrected by the router (due to characteristics of interleaving) WITHOUT the need for the data to be retransmitted by the remote end.
I thought
Quote Forward error correction (FEC) is a method of obtaining error control in data transmission in which the source (transmitter) sends redundant data and the destination (receiver) recognizes only the portion of the data that contains no apparent errors.
rather than just the implication that the Modem just corrects errors
@mickthefitter
Whilst those errors are a bit higher than one would like to see, as Matthew posted the DS MTBE was 1122 and I've seen lines worse than that giving acceptable performance, so I wouldn't worry about it unless your performance deteriorates. The Copper Line Test wasn't showing issues and if your Quiet Line Test is showing no problem, don't worry. Post again if you experience problems, in the meantime I'll drop you a PM.
I'm having more comebacks here than Ol' Blue Eyes
Some photos that I've uploaded of my router position, the cable to it, and the wiring inside the Telecom box outside my front door, to answer some questions I've had in a PM. Seeing as I cannot easily upload photos in a PM!
The mains lead to the router now comes from the other room, under the carpets, and passes under the BT master socket. The original router DSL lead is also buried under the carpet after it leaves the microfilter, and comes out again at the back of the bookcase (okay, a DVD and VHS case in reality) and goes up to the router on top of it. The existing, 1988 installed 'twisted pairs' phone cable is what is seen atop the skirting, from the front door, back of the phone table, under the stairs, to the BT master socket. Prior to problem solving on this thread, the router was on the phone table near the front door, fed from the master socket by a domestic phone extension cable that is still in place cos that too, is under the carpet. But before this even, my router used to be upstairs in a spare bedroom, also connected by a domestic phone extension!
Mick.
Some photos that I've uploaded of my router position, the cable to it, and the wiring inside the Telecom box outside my front door, to answer some questions I've had in a PM. Seeing as I cannot easily upload photos in a PM!
The mains lead to the router now comes from the other room, under the carpets, and passes under the BT master socket. The original router DSL lead is also buried under the carpet after it leaves the microfilter, and comes out again at the back of the bookcase (okay, a DVD and VHS case in reality) and goes up to the router on top of it. The existing, 1988 installed 'twisted pairs' phone cable is what is seen atop the skirting, from the front door, back of the phone table, under the stairs, to the BT master socket. Prior to problem solving on this thread, the router was on the phone table near the front door, fed from the master socket by a domestic phone extension cable that is still in place cos that too, is under the carpet. But before this even, my router used to be upstairs in a spare bedroom, also connected by a domestic phone extension!
Mick.
I can see why you don't want to redecorate Mick
So if I've understood this correctly, in picture "router 003.jpg" that's the doorway to the left of where the cable "disappears".
(Would I be right in assuming that the glass visible on the left of the picture is a side window next to the door?)
Am I also correct in assuming that the internal wall we see in the picture that the cable runs along, is perpendicular to the outside wall on which the grey box is mounted that we see in picture "router 002.jpg" and in which we can see the doorway to the right?
I can see it would require a bit of careful thought on the best way to replace and route a replacement cable from outside to even just inside. The cracked insulation which you have taped up and the rather corroded connections in the grey box will undoubtedly give a significant problem at some point in the future.
So if I've understood this correctly, in picture "router 003.jpg" that's the doorway to the left of where the cable "disappears".
(Would I be right in assuming that the glass visible on the left of the picture is a side window next to the door?)
Am I also correct in assuming that the internal wall we see in the picture that the cable runs along, is perpendicular to the outside wall on which the grey box is mounted that we see in picture "router 002.jpg" and in which we can see the doorway to the right?
I can see it would require a bit of careful thought on the best way to replace and route a replacement cable from outside to even just inside. The cracked insulation which you have taped up and the rather corroded connections in the grey box will undoubtedly give a significant problem at some point in the future.
Quote from: Anotherone The cracked insulation which you have taped up and the rather corroded connections in the grey box will undoubtedly give a significant problem at some point in the future.
Hmm...I suppose in most people's houses, the place where the telephone line comes into the house isn't top of the list of things to check and maintain. I think it only becomes an issue when the telephone - or increasingly broadband - doesn't work. Of course if people want, and can afford the latest whizzo fibre optic systems, I guess it all gets changed to something modern anyway!
Hmm, right, the map of my house...yes, the cable near the glass is near the front door, and that is a frosted pane next to the front door, and I would describe the cable as 'appearing', since that is where it emerges in the house 'tother side of that taped bit coming out of the box of spiders.
That first run of cable across the skirting, where it goes behind the phone table, is the wall where the Telecom box is on the outside. The top of the Telecom box is about level with the top of the skirting board inside the house, and it would be to the left of the power socket where my phone and answering machine are plugged in, as we look at the power socket in the house.
The phone cable is pinned to the top of the skirting board until it reaches the bottom step of the stairs, then it dives under the carpet, burrows around the bottom step, then shoots back up out of the Axminster (not really) on the inboard edge of the stair post, resuming its path, trying to be discreet, pinned along panel joints and skirting board tops, till it gets to my master socket.
My infamous Argos telephone extension lead follows the same course in the other direction, except entirely buried by carpet, with a fair old excess length coiled up under my phone table. I installed that...hmm...probably late 1993.
I won't even bother trying to describe the route that the second extension lead to the upstairs follows - it is tortuous. Plus (make sure you are sitting down :D) when I first got broadband - O2, you'll be pleased to know - and my spare bedroom was a computer room (the desk now rather redundant but it holds my printer, scanner and some model cars) I used another splitter and ran yet another extension lead back from the telephone in the main bedroom, back under the landing carpet into the spare room! How could it possibly work?!! It did! Well enough to keep me happy anyway, until the Smart LG TV came along. The wi fi signal to that was - well, not as bad as you might imagine, but it had off days when I couldn't get it to work well. Then I brought the router down to the phone table - by which time I'd been on Plusnet for a while (over 12 months) and that, as they say, is more or less where I came in Thanks for the compliment about the decorating. It was re-done last September. Not before time though.
I think basically I've just got to judge the need to do any reworking of the copper wires on performance. If I'm satisfied with the performance I've got, both on the phone and the broadband, then there's little need to go stirring things up. It's funny really, because one of the issues I had with my last technical job (there were many) was that frequently I felt the urge to do a better job on maintaining production lines than time pressures and spares availability would allow. One of my frustrations was knowing that bodged repairs would go again in a few weeks time, and I'd have to do the whole thing again, probably to the same standard. I am thinking that perhaps with the view inside my Telecom box, and one or two other issues that came up, the same desire to see things at their optimum is applicable to people who know about broadband? Wires and signals aren't my area. To me, right now, it 'works' and that's good enough
PERPENDICULAR! Yeah, I get you now! Where the cable 'disappears' (nay, appears) is simply the bit of wall two bricks thick that my door frame is set into, so yes, 90 degrees to the outside, then turn to run parallel to the outside wall and get to my phone's 13 amp socket.
Clear as mud? No wonder I can't drive a lorry without a TomTom
Clear as mud? No wonder I can't drive a lorry without a TomTom