How to ...

Started by Simon_idnet, Sep 20, 2006, 21:43:12

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1 2 All
User actions

Simon_idnet

Sep 20, 2006, 21:43:12
... cut and paste from a Command Prompt window.

If anyone would like to send in their ping stats we would very much appreciate the info.

If you don't know how to, then please follow these steps:

Click on the Start button, choose Run, type "cmd" and click on "OK".

In the black window that now opens type "ping www.idnet.net"

When that's finished, click on the little icon in the top-left corner of the window and choose "Edit" then "Select All" and then hit the Enter key.

Now, start a Reply to this post and hit the Control key and the letter "V" together = CTRL+V

Cheers
Simon

MoHux

#1
Sep 20, 2006, 21:51:46
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

Reply from 212.69.36.10: bytes=32 time=18ms TTL=61
Reply from 212.69.36.10: bytes=32 time=18ms TTL=61
Reply from 212.69.36.10: bytes=32 time=19ms TTL=61
Reply from 212.69.36.10: bytes=32 time=17ms TTL=61

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

HTH
"It's better to say nothing and be thought an idiot - than to open your mouth and remove all doubt."

jimc

#2
Sep 21, 2006, 19:39:09
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=70ms TTL=60
Reply from 212.69.36.10: bytes=32 time=71ms TTL=60
Reply from 212.69.36.10: bytes=32 time=70ms TTL=60
Reply from 212.69.36.10: bytes=32 time=69ms TTL=60

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

Adam

#3
Sep 21, 2006, 20:45:32
Just an idea here, I imagine it would be easier and nicer for everyone if discussion is left out of this thread, so unless the thread starter (simon) thinks best otherwise please only reply with ping replies as requested by simon.

On a lighter note, please do feel free to start a thread to discuss ping replies posted here.

Adam
Adam

B52

#4
Sep 21, 2006, 21:08:21
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=68ms TTL=60
Reply from 212.69.36.10: bytes=32 time=39ms TTL=60
Reply from 212.69.36.10: bytes=32 time=40ms TTL=60
Reply from 212.69.36.10: bytes=32 time=39ms TTL=60

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

\>

William

#5
Sep 21, 2006, 21:33:09
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\NOLA>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=18ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60

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

C:\Documents and Settings\NOLA>

Bill

#6
Sep 22, 2006, 00:18:17
C:\WINDOWS>ping www.idnet.net

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=14ms TTL=60
Reply from 212.69.36.10: bytes=32 time=15ms TTL=60
Reply from 212.69.36.10: bytes=32 time=14ms TTL=60

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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
and just for the ducks of it:

C:\WINDOWS>tracert idnet.net

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

  1     2 ms     1 ms   <10 ms  192.168.1.1
  2    13 ms    14 ms    14 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    13 ms    14 ms    15 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4    24 ms    14 ms    15 ms  redbus-gw.idnet.net [212.69.63.1]
  5    14 ms    17 ms    13 ms  idnet.net [212.69.36.10]

Trace complete.
Bill
BQMs-  IPv4  IPv6

Adam

#7
Sep 22, 2006, 02:34:13
Quote
PING www.idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=60 time=56.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=60 time=56.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=60 time=54.3 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=60 time=54.6 ms

--- www.idnet.net ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3009ms
rtt min/avg/max/mdev = 54.355/55.380/56.481/0.927 ms

Adam
Adam

jimc

#8
Sep 22, 2006, 09:02:53
I am re-submitting as their is such a large improvment this morning.
hope thats all right

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=32ms TTL=60
Reply from 212.69.36.10: bytes=32 time=33ms TTL=60

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

stevelondon

#9
Sep 22, 2006, 13:43:11 Last Edit: Sep 22, 2006, 13:45:07 by stevelondon
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

>ping www.idnet.net

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

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

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

Xbandito

#10
Sep 25, 2006, 17:30:55
Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=49ms TTL=60
Reply from 212.69.36.10: bytes=32 time=45ms TTL=60
Reply from 212.69.36.10: bytes=32 time=46ms TTL=60
Reply from 212.69.36.10: bytes=32 time=44ms TTL=60

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

MoHux

#11
Sep 25, 2006, 17:42:39
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

Reply from 212.69.36.10: bytes=32 time=18ms TTL=61
Reply from 212.69.36.10: bytes=32 time=22ms TTL=61
Reply from 212.69.36.10: bytes=32 time=17ms TTL=61
Reply from 212.69.36.10: bytes=32 time=20ms TTL=61

Ping statistics for 212.69.36.10:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 22ms, Average = 19ms
"It's better to say nothing and be thought an idiot - than to open your mouth and remove all doubt."

sobranie

#12
Sep 25, 2006, 21:18:10
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\wiggy>ping www.idnet.net

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

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

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

C:\Documents and Settings\wiggy>

globby

#13
Sep 25, 2006, 21:37:47
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


C:\Documents and Settings\Bill Fence>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=24ms TTL=61
Reply from 212.69.36.10: bytes=32 time=19ms TTL=61
Reply from 212.69.36.10: bytes=32 time=20ms TTL=61
Reply from 212.69.36.10: bytes=32 time=19ms TTL=61

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

C:\Documents and Settings\Bill Fence>

CatMangler

#14
Sep 26, 2006, 14:43:10 Last Edit: Sep 26, 2006, 14:46:08 by CatMangler
C:\Documents and Settings\Administrator>ping idnet.co.uk -t

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

Reply from 212.69.36.10: bytes=32 time=127ms TTL=60
Reply from 212.69.36.10: bytes=32 time=139ms TTL=60
Reply from 212.69.36.10: bytes=32 time=139ms TTL=60
Request timed out.
Reply from 212.69.36.10: bytes=32 time=150ms TTL=60
Reply from 212.69.36.10: bytes=32 time=134ms TTL=60
Reply from 212.69.36.10: bytes=32 time=125ms TTL=60
Reply from 212.69.36.10: bytes=32 time=141ms TTL=60
Reply from 212.69.36.10: bytes=32 time=118ms TTL=60
Reply from 212.69.36.10: bytes=32 time=149ms TTL=60
Reply from 212.69.36.10: bytes=32 time=137ms TTL=60
Reply from 212.69.36.10: bytes=32 time=133ms TTL=60
Reply from 212.69.36.10: bytes=32 time=150ms TTL=60
Reply from 212.69.36.10: bytes=32 time=135ms TTL=60
Reply from 212.69.36.10: bytes=32 time=111ms TTL=60
Reply from 212.69.36.10: bytes=32 time=115ms TTL=60
Reply from 212.69.36.10: bytes=32 time=142ms TTL=60
Reply from 212.69.36.10: bytes=32 time=113ms TTL=60
Reply from 212.69.36.10: bytes=32 time=120ms TTL=60
Reply from 212.69.36.10: bytes=32 time=150ms TTL=60
Reply from 212.69.36.10: bytes=32 time=106ms TTL=60
Reply from 212.69.36.10: bytes=32 time=137ms TTL=60
Reply from 212.69.36.10: bytes=32 time=146ms TTL=60
Reply from 212.69.36.10: bytes=32 time=79ms TTL=60
Reply from 212.69.36.10: bytes=32 time=81ms TTL=60
Reply from 212.69.36.10: bytes=32 time=115ms TTL=60
Reply from 212.69.36.10: bytes=32 time=136ms TTL=60
Reply from 212.69.36.10: bytes=32 time=123ms TTL=60
Reply from 212.69.36.10: bytes=32 time=114ms TTL=60
Reply from 212.69.36.10: bytes=32 time=136ms TTL=60
Reply from 212.69.36.10: bytes=32 time=101ms TTL=60
Reply from 212.69.36.10: bytes=32 time=89ms TTL=60
Reply from 212.69.36.10: bytes=32 time=140ms TTL=60
Reply from 212.69.36.10: bytes=32 time=127ms TTL=60
Reply from 212.69.36.10: bytes=32 time=133ms TTL=60
Reply from 212.69.36.10: bytes=32 time=103ms TTL=60
Reply from 212.69.36.10: bytes=32 time=149ms TTL=60
Reply from 212.69.36.10: bytes=32 time=140ms TTL=60
Reply from 212.69.36.10: bytes=32 time=140ms TTL=60
Reply from 212.69.36.10: bytes=32 time=141ms TTL=60

Ping statistics for 212.69.36.10:
    Packets: Sent = 40, Received = 39, Lost = 1 (2% loss),
Approximate round trip times in milli-seconds:
    Minimum = 79ms, Maximum = 150ms, Average = 127ms

Tracing route to idnet.co.uk [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.253
  2   130 ms   125 ms   131 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3   133 ms   129 ms   126 ms  telehouse-gw-bb.idnet.net [212.69.63.9]
  4   136 ms   135 ms   139 ms  212.69.63.5
  5   147 ms   140 ms   135 ms  www.idnet.net [212.69.36.10]

Trace complete.

Thats pretty cr*p!

mrapoc

#15
Sep 26, 2006, 18:06:24
QuotePinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=23ms TTL=60
Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60

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

I think im fixed  ;D

maxping

#16
Sep 26, 2006, 18:30:24
Quote from: CatMangler on Sep 26, 2006, 14:43:10

    Minimum = 79ms, Maximum = 150ms, Average = 127ms



Thats pretty cr*p!

Did you try turning the router off for 30 mins then trying again?

maxping

#17
Sep 26, 2006, 18:40:37
Heres my graphs from the 18 th and today,it looks like mine may be fixed as the green line is staying fairly stable and low. (on todays graph - scroll down)

If i had been here today to ping would it have shown decent results going by the second graph as when i pinged on the 18th (top graph) they were 150 ms MINIMUM  :(




Todays result.




Scott

#18
Sep 26, 2006, 21:30:38

C:\> ping idnet.co.uk -t

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

Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=28ms TTL=60
Reply from 212.69.36.10: bytes=32 time=29ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60
Reply from 212.69.36.10: bytes=32 time=27ms TTL=60
Reply from 212.69.36.10: bytes=32 time=30ms TTL=60
Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=31ms TTL=60
Reply from 212.69.36.10: bytes=32 time=26ms TTL=60


All good from here on a long long bit o' wire !!!
Member of the IDNet Mafia
How to Spot and Deal with Trolls

Danni

#19
Sep 27, 2006, 17:03:25
Mine are a little up, but don't seem to be affecting anything :)

Quotedanni@Luciana:~$ ping idnet.net
PING idnet.net (212.69.36.10) 56(84) bytes of data.
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=1 ttl=60 time=66.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=2 ttl=60 time=60.9 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=3 ttl=60 time=64.8 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=4 ttl=60 time=62.2 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=5 ttl=60 time=59.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=6 ttl=60 time=71.4 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=7 ttl=60 time=61.6 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=8 ttl=60 time=61.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=9 ttl=60 time=63.0 ms
64 bytes from www.idnet.net (212.69.36.10): icmp_seq=10 ttl=60 time=59.6 ms

--- idnet.net ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9041ms
rtt min/avg/max/mdev = 59.483/63.086/71.461/3.492 ms 

And the traceroute (I stopped after the 8th hop because it shouldn't take more than that)
Quote
danni@Luciana:~$ traceroute idnet.net
traceroute to idnet.net (212.69.36.10), 30 hops max, 40 byte packets
1  192.168.2.1 (192.168.2.1)  0.745 ms  0.825 ms  0.553 ms
2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  58.079 ms *  57.012 ms
3  * * telehouse-gw-bb.idnet.net (212.69.63.9)  102.713 ms
4  212.69.63.5 (212.69.63.5)  56.458 ms  61.225 ms  60.361 ms
5  * * *
6  * * *
7  * * *
8  * * *
IDNet Customer (ex-partner's name): 6th January 2006 - 23rd March 2007
IDNet broadband Customer (my name): 11th June 2008 - 21st April 2010

Now with Be for internets, IDNet for phone.

Rik

#20
Nov 08, 2006, 15:25:41
In case anyone is still collecting (only just notice this):

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

Reply from 212.69.36.10: bytes=32 time=24ms TTL=60
Reply from 212.69.36.10: bytes=32 time=22ms TTL=60
Reply from 212.69.36.10: bytes=32 time=23ms TTL=60
Reply from 212.69.36.10: bytes=32 time=20ms TTL=60

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

I have interleaving on.
Rik
--------------------

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

Nerval

#21
Nov 08, 2006, 15:35:37
Well mine's up and down like I don't know what.
Not that I'm a gamer.

Today it's
>ping www.idnet.net

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

Reply from 212.69.36.10: bytes=32 time=60ms TTL=60
Reply from 212.69.36.10: bytes=32 time=188ms TTL=60
Reply from 212.69.36.10: bytes=32 time=112ms TTL=60
Reply from 212.69.36.10: bytes=32 time=169ms TTL=60

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

And I don't know if I have interleaving on or not.

Rik

#22
Nov 08, 2006, 15:39:33
Quote from: Nerval on Nov 08, 2006, 15:35:37
Well mine's up and down like I don't know what.

Well, the polite phrase is usually a fiddler's elbow... ;)

Does your router not report fast path?
Rik
--------------------

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

Nerval

#23
Nov 08, 2006, 15:42:45
No
I think I heard a rumour that it could be done but not via the web interface.
Must look on Google when I've got a minute.

Rik

#24
Nov 08, 2006, 15:56:04
You need to set up a telnet connection (I should have read your sig):

http://192.168.0.1/setup.cgi?todo=debug

It should report debug enable.

In a command prompt, type:

cat /proc/avalanche/avsar_modem_stats

From memory, up near the top you fill see fast path and interleaved paths. Where the errors are tells you whether you have interleaving on or not.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.
Print
Go Up Pages1 2 All
User actions