WBC - successful connections

Started by Rik, May 31, 2009, 11:59:52

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rik

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

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

PuncH

#126
Hopefully I'm not tempting fate by posting on here  :-\

Moved on to ADSL2+ Friday 11th/Saturday 12th June.

I'm currently synced at 19690 with a line profile of 15000 and a throughput of 11500-15000 which I'm pretty happy with. Noise margin has gone up a bit from the initial 6.1db to 8.9db.

Netgear DG834G V4 firmware version 5.01.09

EAFOX Exhange, Ipswich.

Linestats:

ADSL Link                Downstream   Upstream
Connection Speed    19690 kbps    1232 kbps
Line Attenuation      16.0 db         6.8 db
Noise Margin           8.9 db          5.4 db



Rik

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

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

Simon

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

El Bunto

Hello all,

I appear to have been successfully migrated to WBC sometime around 10:00 on
15th June.

Netgear DG834 v4 firmware V5.01.14
Copper path is 1200 metres from Newtownards exchange.

Not terribly impressive line stats compared to what the online estimators were
predicting:

Connection Speed     7785 kbps     888 kbps
Line Attenuation                28.5 db    12.9 db
Noise Margin                11.9 db    10.6 db

Prior to the migration:

Connection Speed        5856 kbps       448 kbps
Line Attenuation             26.0 db         12.5 db
Noise Margin                   12.1 db         23.0 db

Ta,

El Bunto

El Bunto

Replying to myself, speedtest.net shows that my throughput has fallen from 5.20 to 3.34 mbps.

Before

After

Bah!  Well at least I still get the extra download allowance...

El Bunto

Simon

We have found the BT speed tester to be the most reliable.  Could you do one of those, and post the results?
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

rireed3

Someone's got congestion today:  ???


Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 19532 kbps(DOWN-STREAM),  1216 kbps(UP-STREAM)
    IP profile for your line is - 17000 kbps
    Actual IP throughput achieved during the test was - 4629 kbps

If you wish to discuss these results please contact your ISP.

If you are experiencing problems with specific applications, servers or websites please contact your ISP for

assistance.

Your test has completed please close this window to exit the performance tester.

 
same time 15/06/2009 1421

C:\Documents and Settings\blah>tracert www.idnet.net

Tracing route to www.idnet.net [xxx.xxx.xxx.xxx]
over a maximum of 30 hops:

  1    39 ms    99 ms    99 ms  dsldevice.lan [xxx.xxx.xxx.xxx] (Speedtouch artifact, always 99 on the first tracert

ping)
  2    15 ms    14 ms    15 ms  telehouse-gw4-lo2.idnet.net [212.69.63.99]
  3    15 ms    15 ms    14 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    15 ms    15 ms    14 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    16 ms    15 ms    16 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    15 ms    15 ms    16 ms  www.idnet.net [212.69.36.10]

Trace complete.

C:\Documents and Settings\blah>ping -a idnet.net

Pinging idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=15ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59
Reply from 212.69.36.10: bytes=32 time=14ms TTL=59

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum =  15ms, Average =  14ms

--------------- end data

I had bad results also on DSLZone and speedtest.net (their London server showed 32 ms ping, unlike above.

Richard

El Bunto

Quote from: Simon on Jun 15, 2009, 13:52:48
We have found the BT speed tester to be the most reliable.  Could you do one of those, and post the results?

Wilco, it is erroring-out as busy right now but I'll give it another go shortly. 

Richard's results are amazing; my traffic results are about the same as usual:

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 60 byte packets

1  192.168.254.254 (192.168.254.254)                              5.649 ms      5.790 ms      5.759 ms
telehouse-gw4-lo2.idnet.net (212.69.63.99)               45.672 ms   46.610 ms     47.533 ms
telehouse-gw3-g0-1-400.idnet.net (212.69.63.243)  48.675 ms    49.416 ms    50.082 ms
redbus-gw2-g0-1-331.idnet.net (212.69.63.5)          249.001 ms  251.755 ms  251.750 ms
redbus-gw1-fa2-0-300.idnet.net (212.69.63.225)      54.703 ms    54.794 ms     55.646 ms[/font][/font][/font]
* * *

PING idnet.net (212.69.36.10) 56(84) bytes of data.
rtt min/avg/max/mdev = 40.889/41.694/42.373/0.563 ms

Can I swap with Richard?! :)

El Bunto


tomharrison

That's quite a high ping time considering you're on WBC. This is what I get on a standard ADSL line (no interleaving):

QuoteTracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    27 ms    25 ms    30 ms  telehouse-gw2-lo2.idnet.net [212.69.63.55]
  3    25 ms    26 ms    25 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]

  4    25 ms    30 ms    25 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    24 ms    25 ms    24 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    26 ms    26 ms    25 ms  www.idnet.net [212.69.36.10]

Trace complete.

Exchange congestion maybe?
Tom
IDNet Home Max

Rik

That would be my first thought, Tom, followed by a node issue.
Rik
--------------------

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

El Bunto

Quote from: Rik on Jun 15, 2009, 15:36:18
That would be my first thought, Tom, followed by a node issue.

As far as I recall, Newtownards connects via the Glasgow node.  I suppose there is a delay because the packets have to get the ferry across the Irish Sea... 

Pings have always been very poor even prior to WBC though as a non-gamer it didn't really cause me any issues.  But Richard's results were an eye-opener!

Thanks guys

Rik

That extra link will certainly be adding to your ping, unfortunately. :(
Rik
--------------------

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

El Bunto

Quote from: Simon on Jun 15, 2009, 13:52:48
We have found the BT speed tester to be the most reliable.  Could you do one of those, and post the results?

The Speed Test awakens:

Test1 comprises of Best Effort Test:  -provides background information.
    Your DSL connection rate: 7785 kbps(DOWN-STREAM),  888 kbps(UP-STREAM)
    IP profile for your line is - 6500 kbps
    Actual IP throughput achieved during the test was - 6000 kbps

Hurrah!  Must have been congestion earlier today; maybe some bits were stuck in a bend.

Thanks

Sebby


Simon

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

El Bunto

Quote from: El Bunto on Jun 15, 2009, 21:46:07
Hurrah!  Must have been congestion earlier today; maybe some bits were stuck in a bend.

Hmm, spoke too soon - back to slow this morning.  Latency is horrendous, taking about 20
seconds to even get a response from a site. 

Last night around 21:00 everything was blazingly quick, with instant responses.

Perhaps this is an aspect of WBC; reduced daytime performance and better in the evening, to
shape daytime traffic for businesses?  I don't have enough data yet but will keep an eye on
things over the next week.

Simon

I don't think it would hurt to give IDNet all call about this.  :)
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#143
I was switched  at 10:37 this morning. Router is a 2700, dual SSID, firmware 5.29.107.12. Downtime was three minutes.

Prior to the shift, my figures were (down/up) attenuation: 57.9/31.5, noise margin: 9/19, sync speed: 3776/448
After, attenuation: 63/32.7, noise margin: 9/5.6, sync speed: 4137/795

Pings have not changed, averaging 23ms, speed tests are the same downstream, about 790 upstream, hopefully I'll get one profile step downstream and gain 500k. The BT speed tester is busy for the moment.

MSAN is a Texas Instruments.


Edit: what a difference a decimal point makes. :)
Rik
--------------------

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

Simon

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

Steve

 :fingers: I believe the rise in downstream attenuation is a feature of ADSL2+ as compared with ADSL2 and ADSL
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#146
It looks like the BT tester may take a few days to grant access to the new connection, but here's a couple of others to be going on with:



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

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

drummer

My switch was at 09:15 this morning.  Router is Netgear DG834G v4, firmware v5.01.01.

Previous sync was 8128kbps down/448kbps down, attenuation 26db down/14db up, NM 7db down/24db up.

Sync is now 15956kbps down/1135kbps up, attenuation 28db down/12.5db up, NM 6.3db down 5.6 up.

Pings are 8ms and the Namesco speedtester shows my throughput as 7000kbps down/ 962kbps up.

BT speedtester has been busy all morning so no profile to report but if things stay as they are, it'll probably still be 7150.

MSAN used to be Alcatel but today it's not displaying any vendor ID.

Hey ho.
To stay is death but to flee is life.

Rik

Pretty good result, Drummer.  :thumb: I have a theory that the BT tester may not be recognising the new connections immediately, despite the busy message. Time will tell. :)

I'm still jealous, of course.  ;D
Rik
--------------------

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

lozcart

Switched this morning.  Router is Belkin F5D7633-4, firmware 1.00.25.

Previous sync was 7392kbps down/448kbps up, attenuation 47db down/29.5db up, NM 6.1db down/24db up.

Sync is now 7237kbps down/762kbps up, attenuation 51.5db down/27.7db up, NM 6.1db down 5.3 up.

Pings are 31ms

Sorry don't know MSAN ID