Ping times Jan 28 onwards

[Rik]

Look at:

http://192.168.1.254/xslt?PAGE=J02&THISPAGE=J42&NEXTPAGE=J02

You want the DSL channel in the second block of data.

[David]

This last post was sent to my phishing manager Rik,turned red and an alarm sounded when I clicked on it 

Im thinking it was the link ?

[David]

Broadband Link – Summary
Connection Information
Broadband Connection:    Built in modem - ADSL
Current Status:    Fully Operational
DSL Connection Details    
Broadband Link
DSL Line (Wire Pair):    Line 1 (inner pair)
Protocol:    G.DMT Annex A
DSL Channel:    Interleaved
DSLAM:    Country: {0xB5} Vendor: {TSTC} Specific: {0x00}
ATM PVC Info:    0/38
ATM Encapsulation:    Routed LLC
ISP Details    
ISP Connection
Connection Type:    PPPoA
User Name:    
IP Address Range:    <IP address removed - Rik>
Subnet Mask:    255.255.255.255
Gateway:    212.69.63.55
Primary DNS:    212.69.40.3
Secondary DNS:    212.69.36.3
Host Name    
Domain Name:    
MTU:    1500
Spoof MAC Address:    

[David]

Taken phone number off Rik just noted it was on the page 

[Rik]

So was your IP address. The page you are looking for is Broadband link - Summary, at the top of the menu.

[David]

The page you are looking for is Broadband link - Summary, at the top of the menu.

That is all that comes up on summary page Rik.found stats etc 

[Rik]

The screen should look something like this, David.

[attachment deleted by admin]

[David]

Thats the page I posted Rik 

[Rik]

So it is, I must get my eyes tested. 

You have interleaving on, so it might be worth asking support to get it turned off.

[David]

I will send you an appointment 

Still it was a good tour around the router 

I will ask them 

[David]

Contacted support with luck it will be off tomorrow,allow 24 hours,so with BT I will allow a week,will I notice any difference ?

[Rik]

BT are usually quite fast on this one, David. Your ping times will probably drop by about 20ms when it's been done.

[David]

That sounds good what will it result in, I assume a more stable connection ?as I never play on-line gaming will the over all effect be that noticeable ?

[Rik]

I don't think you'll notice much, David. Only gamers and those using VOIP are really troubled by ping times. Interleaving can actually speed up throughout if the line is error prone, but if that is the case, the BT software will probably switch interleaving back on.

[David]

Another learning curve for me......Thanks Rik apprecited 

[snaggie]

 

Everytime I log on in recent days, my ping has been way too high.  Cannot possibly go on to my COD4 servers with pings like these:

PING 193.200.158.60 (193.200.158.60): 56 data bytes
64 bytes from 193.200.158.60: icmp_seq=0 ttl=122 time=190.0 ms
64 bytes from 193.200.158.60: icmp_seq=1 ttl=122 time=170.0 ms
64 bytes from 193.200.158.60: icmp_seq=2 ttl=122 time=145.0 ms
64 bytes from 193.200.158.60: icmp_seq=3 ttl=122 time=165.0 ms

--- 193.200.158.60 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 145.0/167.5/190.0 ms

Can anyone shed any light on how long this is going to go on?  I may have to look to going to another ISP, and I really don't want to do that!

[Glenn]

snaggie Have you tried rebooting your router? but for a definitive answer you will be best contacting the IDNet support team

[Rik]

All we can say is that IDNet are working on the problem as fast as possible. If you contact them, they can see whether you're on a congested pipe and, if necessary, move you to another. (The irony is that, since they added more capacity, they've suffered from congestion on some pipes while others remain empty.

[uxbod]

Everytime I log on in recent days, my ping has been way too high.  Cannot possibly go on to my COD4 servers with pings like these:

PING 193.200.158.60 (193.200.158.60): 56 data bytes
64 bytes from 193.200.158.60: icmp_seq=0 ttl=122 time=190.0 ms
64 bytes from 193.200.158.60: icmp_seq=1 ttl=122 time=170.0 ms
64 bytes from 193.200.158.60: icmp_seq=2 ttl=122 time=145.0 ms
64 bytes from 193.200.158.60: icmp_seq=3 ttl=122 time=165.0 ms

--- 193.200.158.60 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 145.0/167.5/190.0 ms

Can anyone shed any light on how long this is going to go on?  I may have to look to going to another ISP, and I really don't want to do that!

ping idnet.net and posts the results for that please.

[uxbod]

All we can say is that IDNet are working on the problem as fast as possible. If you contact them, they can see whether you're on a congested pipe and, if necessary, move you to another. (The irony is that, since they added more capacity, they've suffered from congestion on some pipes while others remain empty.

though dependent on where that server is it could just be slow due to a congested UK internet while the weather is bad.  Hence pinging idnet.net as that should be the shortest run across the IDNET network IMHO.  Current stats for that are :-

[Rik]

Mine are...

[attachment deleted by admin]

[Glenn]

Mine climbed to over 170ms at lunchtime, I only checked because I was getting data loss with pages not opening, I rebooted and they went back to the 25 - 30ms range.

[Rik]

What I don't understand is why the reboots sometimes work, Glenn. When I did on Friday, I re-connected to the same central, but things were better? 

[Glenn]

I have no idea, it's not something I know anything about, but this is interesting

[snaggie]

snaggie Have you tried rebooting your router? but for a definitive answer you will be best contacting the IDNet support team

Thanks.  Have rebooted my router, and got these results:

PING 193.200.158.60 (193.200.158.60): 56 data bytes
64 bytes from 193.200.158.60: icmp_seq=0 ttl=122 time=35.0 ms
64 bytes from 193.200.158.60: icmp_seq=1 ttl=122 time=35.0 ms
64 bytes from 193.200.158.60: icmp_seq=2 ttl=122 time=35.0 ms
64 bytes from 193.200.158.60: icmp_seq=3 ttl=122 time=35.0 ms

--- 193.200.158.60 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 35.0/35.0/35.0 ms

Just what it should be.  I haven't pinged IDNet yet as I do not know there IP (sorry).  Still don't understand why I should have to reboot the router ?