Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Pings

  • 05-01-2003 12:01am
    #1
    Kevok
    Registered Users, Registered Users 2 Posts: 696 ✭✭✭


    Whats a good program to use that accurately measures ping times. I tend to notice that the Windows one rounds the values up or down to the nearest 5.


Comments

  • #2
    Runfree
    Closed Accounts Posts: 1,144 ✭✭✭Runfree


    Did you use the one in MS-Dos???? This is what I got from pinging Boards.ie :)

    C:\WINDOWS>ping www.boards.ie

    Pinging www.boards.ie [195.218.115.65] with 32 bytes of data:

    Reply from 195.218.115.65: bytes=32 time=45ms TTL=51
    Reply from 195.218.115.65: bytes=32 time=45ms TTL=51
    Reply from 195.218.115.65: bytes=32 time=50ms TTL=51
    Reply from 195.218.115.65: bytes=32 time=44ms TTL=51

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

    C:\WINDOWS>

    hehe.


  • #3
    red_ice
    Registered Users, Registered Users 2 Posts: 4,946 ✭✭✭red_ice


    start -> run

    ping -t www.boards.ie


    The '-t' will make the list of ping times infinite instead of just ping www.boards.ie which will just out 5.

    reD


  • #4
    leeroybrown
    Closed Accounts Posts: 7,562 ✭✭✭leeroybrown


    PING www.boards.ie (195.218.115.65): 56 data bytes
    64 bytes from 195.218.115.65: icmp_seq=0 ttl=48 time=37.1 ms
    64 bytes from 195.218.115.65: icmp_seq=1 ttl=48 time=36.8 ms
    64 bytes from 195.218.115.65: icmp_seq=2 ttl=48 time=38.0 ms
    64 bytes from 195.218.115.65: icmp_seq=3 ttl=48 time=37.1 ms
    64 bytes from 195.218.115.65: icmp_seq=4 ttl=48 time=37.9 ms
    64 bytes from 195.218.115.65: icmp_seq=5 ttl=48 time=38.2 ms
    64 bytes from 195.218.115.65: icmp_seq=6 ttl=48 time=39.9 ms
    64 bytes from 195.218.115.65: icmp_seq=7 ttl=48 time=40.5 ms
    64 bytes from 195.218.115.65: icmp_seq=8 ttl=48 time=38.2 ms
    64 bytes from 195.218.115.65: icmp_seq=9 ttl=48 time=41.9 ms
    64 bytes from 195.218.115.65: icmp_seq=10 ttl=48 time=39.7 ms
    64 bytes from 195.218.115.65: icmp_seq=11 ttl=48 time=37.1 ms
    64 bytes from 195.218.115.65: icmp_seq=12 ttl=48 time=37.4 ms
    64 bytes from 195.218.115.65: icmp_seq=13 ttl=48 time=41.0 ms
    64 bytes from 195.218.115.65: icmp_seq=14 ttl=48 time=39.1 ms

    --- www.boards.ie ping statistics ---
    15 packets transmitted, 15 packets received, 0% packet loss
    round-trip min/avg/max = 36.8/38.6/41.9 ms

    The joys of Linux ;)


  • #5
    Kevok
    Registered Users, Registered Users 2 Posts: 696 ✭✭✭Kevok 


    Pinging clarity.jolt.co.uk [195.149.21.11] with 32 bytes o

Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=10ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245
Reply from 195.149.21.11: bytes=32 time=20ms TTL=245

Ping statistics for 195.149.21.11:
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum =  20ms, Average =  19ms
    See seems a bit odd.


  • #6
    Chaos-Engine
    Closed Accounts Posts: 772 ✭✭✭Chaos-Engine


    Reply from 195.218.115.65: bytes=32 time=125ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=109ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=109ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=110ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=125ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=125ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=110ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=110ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=110ms TTL=52
    Reply from 195.218.115.65: bytes=32 time=125ms TTL=52

    Ping statistics for 195.218.115.65:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 109ms, Maximum = 125ms, Average = 115ms
    ^C

    This is my current dial up.... Got a Line Of Sight test today and it looks way way nicer :D


  • Advertisement
  • #7
    quozl
    Registered Users, Registered Users 2 Posts: 3,308 ✭✭✭quozl


    These are the ping times of the first hop on my irishbroadband 1mbit connect

    64 bytes from 62.221.16.65: icmp_seq=0 ttl=255 time=44.1 ms
    64 bytes from 62.221.16.65: icmp_seq=2 ttl=255 time=12.9 ms
    64 bytes from 62.221.16.65: icmp_seq=3 ttl=255 time=30.1 ms
    64 bytes from 62.221.16.65: icmp_seq=4 ttl=255 time=9.3 ms
    64 bytes from 62.221.16.65: icmp_seq=5 ttl=255 time=151.1 ms
    64 bytes from 62.221.16.65: icmp_seq=6 ttl=255 time=8.2 ms
    64 bytes from 62.221.16.65: icmp_seq=7 ttl=255 time=36.1 ms
    64 bytes from 62.221.16.65: icmp_seq=8 ttl=255 time=8.8 ms
    64 bytes from 62.221.16.65: icmp_seq=9 ttl=255 time=48.8 ms
    64 bytes from 62.221.16.65: icmp_seq=10 ttl=255 time=8.9 ms
    64 bytes from 62.221.16.65: icmp_seq=11 ttl=255 time=7.8 ms
    64 bytes from 62.221.16.65: icmp_seq=12 ttl=255 time=16.1 ms
    64 bytes from 62.221.16.65: icmp_seq=13 ttl=255 time=26.0 ms
    64 bytes from 62.221.16.65: icmp_seq=14 ttl=255 time=7.3 ms
    64 bytes from 62.221.16.65: icmp_seq=15 ttl=255 time=7.1 ms
    64 bytes from 62.221.16.65: icmp_seq=16 ttl=255 time=8.6 ms
    64 bytes from 62.221.16.65: icmp_seq=17 ttl=255 time=15.1 ms
    64 bytes from 62.221.16.65: icmp_seq=18 ttl=255 time=258.9 ms
    64 bytes from 62.221.16.65: icmp_seq=19 ttl=255 time=7.8 ms
    64 bytes from 62.221.16.65: icmp_seq=20 ttl=255 time=8.4 ms
    64 bytes from 62.221.16.65: icmp_seq=23 ttl=255 time=119.6 ms
    64 bytes from 62.221.16.65: icmp_seq=25 ttl=255 time=9.1 ms
    64 bytes from 62.221.16.65: icmp_seq=26 ttl=255 time=11.3 ms
    64 bytes from 62.221.16.65: icmp_seq=27 ttl=255 time=39.6 ms
    64 bytes from 62.221.16.65: icmp_seq=28 ttl=255 time=89.6 ms
    64 bytes from 62.221.16.65: icmp_seq=29 ttl=255 time=8.5 ms

    Just going from my house, to my default gateway. Ranges from 7ms to 250 (to worse). I'm not downloading or doing anything else with the connect. I've got similiar results with 3 different pcs - linux, win98, win2k connected directly. Sometimes it only spikes from 7 to 80ms, sometimes it goes to 400+.

    Good connect for downloads, worse than my ISDN for gaming. But at least there are no phone call charges.

    This is from the RTE tower, so it's not on 802.11b. I'd be interested in seeing other peoples pings on the RTE tower in particular.

    Greg


  • #8
    Kevok
    Registered Users, Registered Users 2 Posts: 696 ✭✭✭Kevok


    Mine above are to the Sandyford tower. Give IBB a ring and ask if there's anything that can be done.


  • #9
    Pepe LeFrits
    Users Awaiting Email Confirmation Posts: 15,001 ✭✭✭✭Pepe LeFrits


    Originally posted by quozl
    These are the ping times of the first hop on my irishbroadband 1mbit connect

    64 bytes from 62.221.16.65: icmp_seq=0 ttl=255 time=44.1 ms
    64 bytes from 62.221.16.65: icmp_seq=2 ttl=255 time=12.9 ms
    64 bytes from 62.221.16.65: icmp_seq=3 ttl=255 time=30.1 ms
    64 bytes from 62.221.16.65: icmp_seq=4 ttl=255 time=9.3 ms
    64 bytes from 62.221.16.65: icmp_seq=5 ttl=255 time=151.1 ms
    64 bytes from 62.221.16.65: icmp_seq=6 ttl=255 time=8.2 ms
    64 bytes from 62.221.16.65: icmp_seq=7 ttl=255 time=36.1 ms
    64 bytes from 62.221.16.65: icmp_seq=8 ttl=255 time=8.8 ms
    64 bytes from 62.221.16.65: icmp_seq=9 ttl=255 time=48.8 ms
    64 bytes from 62.221.16.65: icmp_seq=10 ttl=255 time=8.9 ms
    64 bytes from 62.221.16.65: icmp_seq=11 ttl=255 time=7.8 ms
    64 bytes from 62.221.16.65: icmp_seq=12 ttl=255 time=16.1 ms
    64 bytes from 62.221.16.65: icmp_seq=13 ttl=255 time=26.0 ms
    64 bytes from 62.221.16.65: icmp_seq=14 ttl=255 time=7.3 ms
    64 bytes from 62.221.16.65: icmp_seq=15 ttl=255 time=7.1 ms
    64 bytes from 62.221.16.65: icmp_seq=16 ttl=255 time=8.6 ms
    64 bytes from 62.221.16.65: icmp_seq=17 ttl=255 time=15.1 ms
    64 bytes from 62.221.16.65: icmp_seq=18 ttl=255 time=258.9 ms
    64 bytes from 62.221.16.65: icmp_seq=19 ttl=255 time=7.8 ms
    64 bytes from 62.221.16.65: icmp_seq=20 ttl=255 time=8.4 ms
    64 bytes from 62.221.16.65: icmp_seq=23 ttl=255 time=119.6 ms
    64 bytes from 62.221.16.65: icmp_seq=25 ttl=255 time=9.1 ms
    64 bytes from 62.221.16.65: icmp_seq=26 ttl=255 time=11.3 ms
    64 bytes from 62.221.16.65: icmp_seq=27 ttl=255 time=39.6 ms
    64 bytes from 62.221.16.65: icmp_seq=28 ttl=255 time=89.6 ms
    64 bytes from 62.221.16.65: icmp_seq=29 ttl=255 time=8.5 ms

    Just going from my house, to my default gateway. Ranges from 7ms to 250 (to worse). I'm not downloading or doing anything else with the connect. I've got similiar results with 3 different pcs - linux, win98, win2k connected directly. Sometimes it only spikes from 7 to 80ms, sometimes it goes to 400+.

    Good connect for downloads, worse than my ISDN for gaming. But at least there are no phone call charges.

    This is from the RTE tower, so it's not on 802.11b. I'd be interested in seeing other peoples pings on the RTE tower in particular.

    Greg

    oh crap, you gotta be kidding me. isnt mr flibble on IBB off donnybrook aswell ?


  • #10
    Kevok
    Registered Users, Registered Users 2 Posts: 696 ✭✭✭Kevok


    Ok out of curiosity i decided to ping HIS gateway from my computer.

    Tracert first to show the hops.
    Tracing route to 62.221.16.65 over a maximum of 30 hops

  1   <10 ms    10 ms   <10 ms  62.221.16.1
  2   <10 ms   <10 ms    10 ms  62.221.16.65

Trace complete.

    And now a list of pings.
    Pinging 62.221.16.65 with 32 bytes of data:

Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=11ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253
Reply from 62.221.16.65: bytes=32 time<10ms TTL=253
Reply from 62.221.16.65: bytes=32 time=10ms TTL=253

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

    Could you PM me your IP and i'll ping you from my comp.


  • #11
    Jak
    Registered Users, Registered Users 2 Posts: 1,643 ✭✭✭Jak


    10ms avg to your gateway Quozl. With a background download.

    Average 13ms to games2 under same conditions right now.

    On IBB down in Sandymount from RTE tower.

    Longer test showed one small spike over 40 packets.

    JAK.


  • Advertisement
  • #12
    quozl
    Registered Users, Registered Users 2 Posts: 3,308 ✭✭✭quozl


    they're coming out next week to try and fix it :)
    Greg


  • #13
    Pepe LeFrits
    Users Awaiting Email Confirmation Posts: 15,001 ✭✭✭✭Pepe LeFrits


    Reply from 62.221.16.65: bytes=32 time=70ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=61ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=70ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=50ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=80ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=110ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=70ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=40ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=50ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=100ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=131ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=40ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=50ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=20ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=30ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=50ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=10ms TTL=255
    Reply from 62.221.16.65: bytes=32 time=80ms TTL=255


    My pings on IBB to the default gateway. Pretty damn poor :/


  • #14
    KdjaCL
    Closed Accounts Posts: 20,346 ✭✭✭✭KdjaCL


    tracert 159.153.178.73

    Tracing route to 159.153.178.73 over a maximum of 30 hops

    1 51 ms 52 ms 52 ms k100-1.bas1.dbn.dublin.eircom.net [159.134.100.1
    ]
    2 50 ms 53 ms 50 ms fe0-1.edge1.dbn.dublin.eircom.net [159.134.155.8
    9]
    3 51 ms 52 ms 50 ms pos2-0.btr1.cra.dublin.eircom.net [159.134.155.1
    37]
    4 55 ms 63 ms 55 ms atm1-0-39.peering1.inex.dublin.eircom.net [159.1
    34.191.126]
    5 55 ms 56 ms 55 ms fe0-0-brian.DUB.router.COLT.NET [193.1.208.204]

    6 67 ms 62 ms 64 ms s5-super-grover.LON.router.COLT.NET [212.74.64.1
    81]
    7 63 ms 68 ms 66 ms pos2-0.marge.ctf.UK.COLT.NET [212.74.64.30]
    8 67 ms 67 ms 69 ms p2-0.core-1.pct.lon.UK.COLT.NET [195.110.65.174]

    9 72 ms 72 ms 91 ms p0-0.core-2.pct.lon.UK.COLT.NET [212.161.120.254
    ]
    10 71 ms 72 ms 70 ms v20-acc5-r1.PCT.UK.COLT.NET [212.161.120.74]
    11 70 ms 67 ms 68 ms 213.86.45.221
    12 70 ms 71 ms 72 ms 159.153.176.11
    13 73 ms 70 ms 79 ms 159.153.178.73

    Trace complete.

    Hmm

    kdjac


  • #15
    Tom
    Registered Users, Registered Users 2 Posts: 267 ✭✭Tom


    NTL 512 mbps

    Pinging www.boards.ie [217.114.166.147] with 32 bytes of data:

    Reply from 217.114.166.147: bytes=32 time=40ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=39ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=42ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=39ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=40ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=42ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=40ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=43ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=41ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=41ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=40ms TTL=48
    Reply from 217.114.166.147: bytes=32 time=38ms TTL=48

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


  • #16
    tom-thebox
    Closed Accounts Posts: 1,412 ✭✭✭tom-thebox


    Lets hope boards hasnt got psad monitoring the server, poor devores and regis inbox will over flowing at this point.

    Regards


Advertisement