It's started...

D-Dan · Dec 15, 2010, 13:14:05

Quote from: Technical Ben on Dec 14, 2010, 22:22:11
Thankfully you did not get this!
http://www.theregister.co.uk/2010/12/14/bt_infinity_slowdown/

(Not sure if it's worth an extra thread)
[edit]
Found a great comment!
"The technical fault caused a limited(*) number of customers to see their speeds reduced to 2Mbit/s at certain times.

(*) Limited may be unlimited"

I was experiencing this - and down to 2Mbs which miraculously jumped back to full speed at the stroke of midnight. After it was reported by The Register on Monday, the drops stopped (though not on Monday as BT claimed - it was Tuesday when the drop first didn't happen).

As they said, it's a remarkable coincidence that a technical fault should manifest itself at precisely the time BTs traffic shaping kicks in

Steve

Rik · Dec 15, 2010, 13:15:14

You're not insinuating anything are you, Steve?

D-Dan · Dec 15, 2010, 13:16:41

Surely insinuating it would require a degree of stealth in what I say.

I'm insinuating nothing at all. I'm saying it outright.

Steve

Rik · Dec 15, 2010, 13:19:26

Good for you.

Technical Ben · Dec 15, 2010, 13:28:08

Some were wondering if "30gb" was typed by mistake from "300gb". Would explain why some got the problems, and others did not. 30gb sounds a lot, but when you got Fibre, there is speed and incentive to use things up.

Bill · Jan 16, 2011, 15:29:18

Had another resync earlier today, I've been getting them every day or so since mid-December, but the profile has remained doggedly at ~30-31Mbps and the latency at ~20msec, ie looks like interleave is on.

After today's one the profile is up to >37Mbps (not quite full whack) and latency back to ~10msec, so it looks like I'm back on fastpath. It reinforces my feeling that the DLM does an occasional resync "on spec" to see if things have improved since last time.

(Ignore the first lot of red spikes, that was me trying to get IPv6 working)

Have to wait and see if it sticks, but if it does it would imply that Christmas lights might have been the problem and (more surprisingly) that BT might have finally got the DLM to a state where it's actually being useful...

Rik · Jan 16, 2011, 15:34:50

Come on, Bill, your last statement is preposterous,

Glad things have improved for you.

.Griff. · Jan 16, 2011, 15:39:36

Quote from: Bill on Jan 16, 2011, 15:29:18
Had another resync earlier today, I've been getting them every day or so since mid-December,

I'm so glad to hear you say that Bill as I thought it was only me!

Just like you say since mid-December I've resynced almost every day and some days more than once. My IP Profile also seems to go up and down, up and down, up and down as well.

Bill · Jan 16, 2011, 15:47:13

Quote from: Rik on Jan 16, 2011, 15:34:50
Come on, Bill, your last statement is preposterous,

It does seem totally unbelievable I must admit, but when was the last time you saw an MSAN-initiated resync give a 15% increase in speed and a halving of latency?

And by the way- I got IPv6 working, so the next question is obvious: when does this bbs get a v6 address?

Rik · Jan 16, 2011, 15:51:32

When IDNet give us one.

Bill · Jan 16, 2011, 16:04:08

Thought that might be the answer

Rik · Jan 16, 2011, 16:08:23

You know I wouldn't want to disappoint you, Bill.

Bill · Jan 16, 2011, 16:19:11

Somewhat off-topic... if I use one of the test sites (http://test-ipv6.com/) it tells me what my IPv6 address is on the WAN (internet) side, does this address come from IDNet or somewhere else?

Rik · Jan 16, 2011, 16:21:23

It must come from IDNet, Bill. I wonder if FTTC is being configured for IPv6 from the outset.

Bill · Jan 16, 2011, 16:35:59

It shouldn't be related to FTTC, if IPv6 doesn't work over copper there's going to be a lot of very cross people around

I'll have to keep an eye on it, atm I don't even know if it's static or dynamic.

Rik · Jan 16, 2011, 16:47:26

Same IP in all your messages, Bill.

Bill · Jan 16, 2011, 17:47:21

I'd expect that- unless it looks something like 2a02:68:1:0:213:72ff:fe39:1ae6 then it's my IDNet static IPv4 address.

(That IP belongs to tbb by the way, it's not mine)

Rik · Jan 16, 2011, 17:48:42

I wonder whether you speak IPv4 and IPv6 then?

Bill · Jan 16, 2011, 18:02:48

I think that's the case. There was some talk on tbb about A and AAAA (v4 and v6) records in the DNS, and the behaviour of the link depended which one was returned first and whether the initiating modem/router knew what to do with it.

I didn't really understand it, but I think that if I access a v4-only site it sees my v4 address, a v6-only site sees my v6 one, and if both are enabled then it will use whichever is first in the lookup table. Probably v4 at the moment, I gather IE has problems sorting the two out.

But I'll say it again- I don't really know

Rik · Jan 16, 2011, 18:03:32

That makes two of us, Bill. I'll try and find out more tomorrow.

Bill · Jan 16, 2011, 18:35:20

All I really want is not to have to worry or care whether a url I type in has a v4 or v6 address at the other end

But it would certainly be nice to have a broad idea of how it works, if only to give some idea of whether to kick it or scream for support if it starts to play silly sods

Just for info, I can connect to ipv6.google.com OK, but ping and traceroute both return "Unknown host"...

Rik · Jan 16, 2011, 18:37:40

I'll dig around, give me a nudge if I forget.

Rik · Jan 17, 2011, 10:41:33

As I understand it from support, Bill, their radius servers allocate a dynamic IPv6 address to those who can use it. That means you need a router which supports IPv6 plus the backhaul network. My hunch, and it's no more than that, is that FTTC is currently offering that, but not ADSL.

Bill · Jan 17, 2011, 11:14:39

Thanks Rik.

We need some brave soul with a v6-capable router but not on FTTC to try it out... and before long I suspect you may need an IPv6 support forum

Rik · Jan 17, 2011, 11:27:30

You may well be right. The end of the mighty 2700 is in sight.