My FTTC

Started by zappaDPJ, Sep 18, 2010, 15:19:42

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

For reference in case I need it later, a couple of Jackson Pollocks... I mean two graphs from the last 48 hours. On the plus side the connection is now completely dead which is a damn sight better than being in a situation where it works some of the time and every time it's tested by support  :mad:


zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

It's interesting (poor word choice) that when you moved to adsl2+ that it all went pear shaped and now the same again with fibre,how can it be so frustrating.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Either I'm very unlucky or there has to be something wrong with the cable between my faceplate and the fibre cabinet Steve. To be honest it's becoming an issue I am getting angry about. I had many, many years at another location where I never had a single dropped connection except for one planned outage at the exchange which dropped the line for 30 minutes. That ended three years ago when Pipex became Tiscali. Since then Internet connectivity has become such a thorn in my side I'm seriously thinking about looking for PAYE employment. I've lost far too much income in the last three years trying to work from home.

As a matter of interest, I've just read Lance's service announcement...

QuoteAs part of our network optimisation program, we are moving a transit connection from one core router to another today to further optimise our routing. We don't expect to be any disruptions to broadband connections but there maybe a brief period of routing inconsistencies whilst the new routes propagate.

Might that account for why I'm being routed to a BT wholesale message? I honestly hope not, I'd rather my FTTC connection was just dead in the water.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

The routing inconsistencies has been updated to resolved
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

Which rather unfortunately has fixed the issue I was having earlier on  :sigh:

Oh well, thanks for the update Steve. I'll see what happens when the test router arrives.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

How was the adsl2+ resolved in the end.
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Quote from: zappaDPJ on Sep 21, 2010, 12:20:14
Anyway aside from that IDNet are able to see for the first time from their end that I'm continually disconnecting and they are sending me a test router to try.



Test router or test modem??!?


zappaDPJ

Modem :blush: Sorry, I was up all night wresting work in between my dodgy connection.

Quote from: Steve on Sep 21, 2010, 15:09:39
How was the adsl2+ resolved in the end.

It wasn't resolved Steve. BT BRAS pushed the line down to the minimum sync (256K) so all IDNet could do was to give me a capped service. Unfortunately that didn't work either so I stopped using the line. When I decided to go for the fibre connection it was thought that the problem would be eliminated but for whatever reason it's clearly still an issue unless as I said before I've just been very unlucky and it's a different problem.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

If the problem is related, Zap, it's just a few metres of copper involved now.  :dunno:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

So is the Vdsl on the same line that adsl2+ failed to work on?
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

kev445

Do you have any internal wiring?

If you do, remove the lower half of your master socket, this should disconnect only the internal wiring.
Do you still experience the disconnections?

Some people don't even realise they have extension wiring (sockets ripped out while decorating), so it is worth checking (their will be cables attached to the removable lower half).

Kev

zappaDPJ

I have nothing but the master socket. No extensions of any sort but thanks for the suggestion :)
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

kev445

#64
Quote from: zappaDPJ on Sep 22, 2010, 15:26:32
I have nothing but the master socket. No extensions of any sort but thanks for the suggestion :)

You mentioned you had a second line, does this follow the exact same route (within your property)?

At a guess, when they changed the line pair, it was from the cabinet to the exchange (which no longer carries any ADSL / VDSL signal).

zappaDPJ

#65
I have two cables coming from a telegraph pole both of which which drop down and go straight into two master sockets.

[EDIT] That caught me out. I didn't realise that the embedded tbb line quality monitor was dynamic. I was just looking at the second image posted above thinking I don't remember it being quite that bad and noticed it's current. Quite freaky that.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

Big ThinkBroadband is watching you. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Bill

Quote from: zappaDPJ on Sep 22, 2010, 16:24:49I didn't realise that the embedded tbb line quality monitor was dynamic. I was just looking at the second image posted above thinking I don't remember it being quite that bad and noticed it's current. Quite freaky that.

The "Share live graph" will do exactly that...

The "snapshot" one is supposed to stay live until midnight, then stop updating... if that's the one you used then maybe it's broke again.

Safest to use "previous days" even if you then select today's date. That seems to stop updating at midnight.
Bill
BQMs-  IPv4  IPv6

zappaDPJ

Thanks for the info Bill  :thumb:
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Did you receive the replacement modem Zapper?

zappaDPJ

I got sent a router in the end as it's thought for some reason my previous one was causing the disconnects. Although this one seems a lot less sensitive, if you check the bottom ttb monitor above you can see I'm still having a few issues. (It's dynamic so it shows the current state of play).
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

zappaDPJ

The router log appears to coincide with the ttb monitor as far as I can tell.

[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 10:36:15
[Internet disconnected] Friday, Sep 24,2010 10:34:56
[Internet idle-timeout] Friday, Sep 24,2010 10:34:56
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 09:56:41
[Internet disconnected] Friday, Sep 24,2010 09:53:15
[Internet idle-timeout] Friday, Sep 24,2010 09:53:15
[Admin login] from source 192.168.1.2, Friday, Sep 24,2010 09:35:24
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 09:26:16
[Internet disconnected] Friday, Sep 24,2010 09:23:37
[Internet idle-timeout] Friday, Sep 24,2010 09:23:37
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 09:07:03
[Internet disconnected] Friday, Sep 24,2010 09:03:39
[Internet idle-timeout] Friday, Sep 24,2010 09:03:39
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 08:57:16
[Internet disconnected] Friday, Sep 24,2010 08:53:20
[Internet idle-timeout] Friday, Sep 24,2010 08:53:20
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 08:44:49
[Internet disconnected] Friday, Sep 24,2010 08:43:14
[Internet idle-timeout] Friday, Sep 24,2010 08:43:14
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 08:35:30
[Internet disconnected] Friday, Sep 24,2010 08:33:38
[Internet idle-timeout] Friday, Sep 24,2010 08:33:38
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 08:27:26
[Internet disconnected] Friday, Sep 24,2010 08:25:49
[Internet idle-timeout] Friday, Sep 24,2010 08:25:49
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 07:27:24
[DHCP IP: (192.168.1.2)] to MAC address 00:1E:8C:3A:71:8B, Friday, Sep 24,2010 07:26:51
[Internet disconnected] Friday, Sep 24,2010 05:27:48
[Internet idle-timeout] Friday, Sep 24,2010 05:27:48
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 05:22:49
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 05:22:41
[Internet disconnected] Friday, Sep 24,2010 05:01:55
[Internet idle-timeout] Friday, Sep 24,2010 05:01:55
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 04:56:50
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 04:56:10
[Internet disconnected] Friday, Sep 24,2010 04:32:27
[Internet idle-timeout] Friday, Sep 24,2010 04:32:27
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 04:27:24
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 04:27:03
[Internet disconnected] Friday, Sep 24,2010 04:08:19
[Internet idle-timeout] Friday, Sep 24,2010 04:08:19
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 04:03:15
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 04:02:52
[Internet disconnected] Friday, Sep 24,2010 03:49:11
[Internet idle-timeout] Friday, Sep 24,2010 03:49:11
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 03:44:02
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 03:43:36
[Internet disconnected] Friday, Sep 24,2010 03:34:55
[Internet idle-timeout] Friday, Sep 24,2010 03:34:55
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 03:29:52
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 03:29:25
[Internet disconnected] Friday, Sep 24,2010 03:06:41
[Internet idle-timeout] Friday, Sep 24,2010 03:06:41
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 03:01:41
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 03:01:29
[Internet disconnected] Friday, Sep 24,2010 02:38:45
[Internet idle-timeout] Friday, Sep 24,2010 02:38:45
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 02:33:44
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 02:33:32
[Internet disconnected] Friday, Sep 24,2010 02:10:47
[Internet idle-timeout] Friday, Sep 24,2010 02:10:46
[Internet connected] IP address: 91.135.7.215, Friday, Sep 24,2010 02:05:38
[DHCP IP: (192.168.1.4)] to MAC address 7C:C5:37:3D:C7:5A, Friday, Sep 24,2010 02:05:26
[Internet disconnected] Friday, Sep 24,2010 01:46:44
[Internet idle-timeout] Friday, Sep 24,2010 01:46:44
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Holodene

Which router did they send to you?

Bill

#73
Quote from: zappaDPJ on Sep 24, 2010, 20:14:38
The router log appears to coincide with the ttb monitor as far as I can tell.

Are the times in the log GMT or BST? If they're GMT then the log and the trace tie up better.

I note that the DHCP log entries disappear about when I suspect you put the new router in... it's a pity you can't get the reason for the disconnect from the router. Along with the line stats...

I suspect (and it's no more than that) that the new router is OK and that the disconnects in the log may be due to the modem retraining (via DLM) now the frequent disconnects have stopped. From about midday onwards it's quite acceptable, mine was a lot worse than that for a while!

Can you run a BT speedtest to see what your IP profile is? I try to run one every day or so, just to keep an eye on it.

It'll need a day or two, but I'd say it looks hopeful :fingers: :fingers: :fingers: :fingers:

(Buy I still have reservations about your getting-very-hot modem)



Edit- dammit, just after I posted that a big red spike appeared :mad:
Bill
BQMs-  IPv4  IPv6

zappaDPJ

Quote from: Holodene on Sep 24, 2010, 21:10:58
Which router did they send to you?

It's another WGR614.

Quote from: Bill on Sep 24, 2010, 21:27:13
Are the times in the log GMT or BST? If they're GMT then the log and the trace tie up better.

They are an hour out, so GMT.

I note that the DHCP log entries disappear about when I suspect you put the new router in... it's a pity you can't get the reason for the disconnect from the router. Along with the line stats...

I get a huge number of those which seem to increase when more devices connect to the network. My daughter's laptop seems to be the worst culprit but I've no idea what causes them.

I suspect (and it's no more than that) that the new router is OK and that the disconnects in the log may be due to the modem retraining (via DLM) now the frequent disconnects have stopped. From about midday onwards it's quite acceptable, mine was a lot worse than that for a while!

Can you run a BT speedtest to see what your IP profile is? I try to run one every day or so, just to keep an eye on it.

I'll run one if I can after this post :)

It'll need a day or two, but I'd say it looks hopeful :fingers: :fingers: :fingers: :fingers:

(Buy I still have reservations about your getting-very-hot modem)

I've solved that. I changed the PSU, moved it away from the alcove it was sitting in and have it sat vertically. The combination of all that has it running at about the same temperature as a Sky box which I'm a lot more happy about.

Edit- dammit, just after I posted that a big red spike appeared :mad:

What you are seeing there is me turning off my PC. Strange, isn't it? If anyone can think of any reason why that's occurring I'd be very interested.
zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.