Idnet ping times of late a general question from a hopefully returning customer

MarkE · Apr 03, 2009, 14:08:31

Please if I have posted this in the wrong section,feel free to move it.

I left Idnet about 2 months ago? or thereabouts as at the time with the extra bandwidth Idnet had purchased,there was a lot of ping time problems for gamers,I have recently been emailed by
Multiplay adsl my current provider and they tell me I need to find a new Isp as they are shutting down their service as of April 20th.

Now my question to everyone here is,has the ping time problems been resolved? As I would like to renew my partnership with idnet (ooooh errr)

Rik · Apr 03, 2009, 15:31:48

I am seeing pings of 19-24ms to IDNet, with occasional higher spikes, Mark. Across a day, my average will be 22ms or thereabouts.

Steve · Apr 03, 2009, 15:41:00

No complaints lately on the forum,myself can't complain either
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=17.262 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=17.258 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=17.779 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=16.968 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=14.657 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=17.612 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=17.011 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=18.027 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=17.782 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=17.785 ms

--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 14.657/17.214/18.027/0.918 ms

MarkE · Apr 03, 2009, 15:47:49

Thanks for the replies guys,looking good

I guess I will put in an order shortly then.

Maverich · Apr 03, 2009, 16:50:29

Quote from: MarkE on Apr 03, 2009, 14:08:31
I left Idnet about 2 months ago? or thereabouts as at the time with the extra bandwidth Idnet had purchased,there was a lot of ping time problems for gamers,

Just thought i'd mention, only been with Idnet for a few days but I do a lot of online gaming, haven't had any problems what so ever!

Rik · Apr 03, 2009, 17:03:42

I've just done this ping:

ping www.idnet.net -n 10

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

Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59

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

jameshurrell · Apr 03, 2009, 17:11:40

Looking excellent for me:

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60

Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

Rik · Apr 03, 2009, 17:12:51

Showoff.

OK, so I have interleaving on.

Maverich · Apr 03, 2009, 17:16:25

I'm very jealous

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

Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms 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 = 35ms, Maximum = 39ms, Average = 36ms

Still better then previous Isp

Rik · Apr 03, 2009, 17:17:50

How far are you from London, Maverich?

Maverich · Apr 03, 2009, 17:20:29

Roughly 100 miles.

Rik · Apr 03, 2009, 17:21:08

About double my distance, so that will slow things a bit. Do you know if your line is interleaved?

Maverich · Apr 03, 2009, 17:22:36

I'm really not sure to tell you the truth, how easy is it to find out?

Rik · Apr 03, 2009, 17:23:35

It usually tells you in your router - what are you using, was it a Netgear?

Maverich · Apr 03, 2009, 17:24:43

Yeah its a Netgear I'm using, well remembered!

Rik · Apr 03, 2009, 17:29:58

OK, I just checked, you are interleaved, although it's set to auto, so the BT software has detected some instability or errors and used interleaving to stabilise the line. Support can get it turned off for you, just email them, but there's a risk that the line may become unstable and it will just revert to on. Have we taken you through the ring wire bit (sorry, but I ask so many times, I tend to forget...

).

Maverich · Apr 03, 2009, 17:35:08

No I haven't been taken through the ring wire but have heard about it. I hope it's straight forward enough

I did have quite a few problems on my line when connected with Sky as my noise margin kept dropping out so I was advised to keep rebooting the router until it maintained a higher margin. Could that of caused interleaving to be triggered?

Rik · Apr 03, 2009, 17:41:17

It could, and to be honest, it was bad advice. Do you have an NTE5 mastersocket, the type where the bottom part of the faceplate can be removed? How is the router connected, to the master socket, a hard-wired extension, or using a 'loose' extension lead?

Maverich · Apr 03, 2009, 17:45:47

No I dont have a NTE5 mastersocket in fact It isn't really feasible to use my mastersocket as this is located in a separate building which is located 1 door down to where I actually live (I live in a converted barn hence the odd place). The extensions are both hard wired.

Rik · Apr 03, 2009, 17:54:18

OK, can you get at the master? If so, unscrew the faceplate and gently pull out the wire from terminal 3, usually it's orange/white. You only want a connection on terminals 2 & 5, and they should be a pair, eg blue/white & white/blue. Repeat the exercise at each socket. We often see almost miraculous improvements in speed and stability with this technique. It won't stop your phones ringing, the microfilters generate the ring voltage.

Maverich · Apr 03, 2009, 17:56:03

Yes I can get at the socket. I'll try and give that a go now and post back with any findings. Thanks Rik.

Rik · Apr 03, 2009, 17:59:17

If there's anything on terminal 4, that can safely be removed, just roll up the wire(s) and put a bit of tape round them.

Maverich · Apr 03, 2009, 18:02:17

Ok just checked the master socket and on terminals 2 & 5 were connected. Should I checked the extensions as well?

Rik · Apr 03, 2009, 18:03:51

Yes. Even if the wire is only connected at one end, it acts as a giant antenna and drags noise into the system.

Maverich · Apr 03, 2009, 18:14:20

Ok I had two extensions and both of which had a wire in terminal 3, these have now been taken out. Whats the best way to check to see if this was havin an effect on the connection?

Rik · Apr 03, 2009, 18:15:59

Look at your noise margin. If the router didn't re-sync while you were working, has it gone up. If it did, has the sync speed increased?

Maverich · Apr 03, 2009, 18:17:51

Yes looks like the noise margin has gone up and also the sync speed has increased, only very slightly though.

Rik · Apr 03, 2009, 18:20:49

Re-boot the router tomorrow morning, noise is at its lowest then and you'll get the best sync speed. Check the NM immediately after reconnecting, it should be 6db, but might be 9db if the line software has been at work. If you let me know your sync, NM and downstream attenuation, I'll be able to take an educated guess about any further improvements. If the line remains stable over the weekend, then email support and ask them to have interleaving turned off.

Maverich · Apr 03, 2009, 18:26:32

Ok will do. Did you want me to post stats after the reboot tomorrow?

Rik · Apr 03, 2009, 18:27:30

Yes please.

Maverich · Apr 03, 2009, 18:29:03

Right i'll get that sorted for tomorrow then, thanks again Rik.

Sorry for hijacking your thread MarkE!

Rik · Apr 03, 2009, 18:33:23

NP, Mark will be back.

Maverich · Apr 04, 2009, 10:59:14

Morning, have rebooted rooter and these are the stats,

Connection Speed   6592 kbps   448 kbps
Line Attenuation   31.0 db   18.0 db
Noise Margin   12.0 db   21.0 db

Rik · Apr 04, 2009, 11:02:57

Morning.

If you can maintain sync for 14 days, your target NM will drop to 9db, giving you an extra 5-700k of sync speed. If it then is stable for a further 14 days, it will drop back to 6db, and give you a further 5-700k, iow you'll get near to a full speed from the line. I emphasise, though that 14 days stability - any disconnection during that time will start the clock anew - so don't unplug or re-boot the router.

Maverich · Apr 04, 2009, 11:21:33

Well that can't be bad at all!

Rik · Apr 04, 2009, 11:30:06

Maverich · Apr 05, 2009, 09:14:42

Good morning all!

My router stats seem to have changed again, any idea as to why?

Connection Speed   6240 kbps   448 kbps
Line Attenuation   31.0 db   18.0 db
Noise Margin   13.9 db   21.0 db

Sebby · Apr 05, 2009, 10:13:11

It looks like you've lost sync again, although things are roughly the same, which would suggest a surge of noise. I'd keep an eye on things for a few days and see how you go - there's probably not an awful lot you can do given the location of the master socket, but hopefully that won't matter anyway.

Rik · Apr 05, 2009, 10:13:29

You've had a re-sync, probably during the evening or overnight, so the router has re-connected at a lower speed. Now, in daylight, the noise levels have dropped so the reported noise margin is higher.

Maverich · Apr 05, 2009, 14:08:42

Fair enough. I'm going to stop looking at it for a while and come back to it in a week or so time. I'm happy with the speed i'm achieving at the moment

Rik · Apr 05, 2009, 15:30:37

Best to just enjoy it rather than keep checking, as long as it 'feels' OK.

MarkE · Apr 11, 2009, 21:47:29

Well im back with idnet,after my spell away with multiplay,seems my interleaving is on auto so will put in for having that removed,but to be fair ping times superb and seem back to normal and
top download consistency as well from idnet

Its nice to be back <3

Simon · Apr 11, 2009, 23:16:22

Mark.

MarkE · Apr 12, 2009, 04:18:59

Quote from: Simon on Apr 11, 2009, 23:16:22
Mark.

Thanks Simon,great to be back and to see Idnet running back to its silky smoothest

Rik · Apr 12, 2009, 10:02:16

They've been waiting to lull you into a false sense of security, Mark.

Simon · Apr 12, 2009, 10:28:00

Don't tempt fate, Rik!

Sebby · Apr 12, 2009, 14:03:36

Welcome back, Mark.

Maverich · Apr 12, 2009, 15:53:50

Welcome back Mark!! I'm not jealous of your speed test at all

p.s Everyone having a good Easter?

Rik · Apr 12, 2009, 15:55:30

So far.

Maverich · Apr 12, 2009, 15:59:39

Glad to hear it Rik

Rik · Apr 12, 2009, 16:01:13

Mind you, I've spent most of it in here.