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

Clearwire Pings and Traceroutes.... mmm....

  • 06-11-2005 10:16pm
    #1
    stakey
    Registered Users, Registered Users 2 Posts: 721 ✭✭✭


    To my clans site, www.clan-ascii.com

    1 143 ms 62 ms 45 ms 85.134.128.3
    2 230 ms 74 ms * fe-0-0-0_0.bdr001.dublin.clearwire.ie [85.134.25
    5.13]
    3 90 ms 66 ms 250 ms ge-5-0-0.403.ar1.dub1.gblx.net [67.17.211.53]
    4 52 ms 54 ms 66 ms so0-0-0-2488M.ar3.LON2.gblx.net [67.17.71.25]
    5 114 ms 37 ms 54 ms Easynet-LTD-LON.ge-5-0-2.402.ar2.LON3.gblx.net [
    67.17.212.94]
    6 229 ms 107 ms 96 ms ge2-0-1-0.br0.thlon.uk.easynet.net [217.204.60.8
    9]
    7 47 ms 108 ms 99 ms ge0-0-0-0.br0.tclon.uk.easynet.net [195.172.211.
    206]
    8 140 ms 221 ms 200 ms fe1-1-0.ar0.rblon.uk.easynet.net [217.204.60.51]

    9 159 ms 70 ms * fe4-1.ar0.r2lon.uk.easynet.net [212.134.12.70]
    10 429 ms 288 ms 187 ms fe-0-1-br.slipstream.ultraspeed.co.uk [62.149.32
    .130]
    11 490 ms 366 ms 330 ms fe-0-0-co.anti-matter.ultraspeed.co.uk [62.149.3
    2.132]
    12 87 ms 66 ms 78 ms server14.dedicateduk.com [62.149.36.42]



    Constant ping to www.boards.ie

    Reply from 82.195.136.250: bytes=32 time=98ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=85ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=123ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=209ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=121ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=35ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=106ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=141ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=158ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=68ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=172ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=204ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=94ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=46ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=135ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=151ms TTL=60
    Request timed out.
    Reply from 82.195.136.250: bytes=32 time=65ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=49ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=245ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=127ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=184ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=160ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=378ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=122ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=203ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=187ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=172ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=223ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=172ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=88ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=245ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=172ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=160ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=186ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=178ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=248ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=260ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=275ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=166ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=122ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=294ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=236ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=189ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=163ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=380ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=250ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=49ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=149ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=147ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=42ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=72ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=195ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=51ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=75ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=147ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=59ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=134ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=162ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=519ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=297ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=291ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=166ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=82ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=132ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=165ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=277ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=146ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=179ms TTL=60



    Nice eh?


Comments

  • #2
    sisyphus
    Closed Accounts Posts: 79 ✭✭sisyphus


    Traceroute to same site:

    Tracing route to clan-ascii.com [62.149.36.42]
    over a maximum of 30 hops:

    1 45 ms 24 ms 24 ms 85.134.128.3
    2 28 ms 24 ms 25 ms fe-0-0-0_0.bdr001.dublin.clearwire.ie [85.134.25
    5.13]
    3 32 ms 41 ms 24 ms ge-5-0-0.403.ar1.dub1.gblx.net [67.17.211.53]
    4 43 ms 41 ms 41 ms so0-0-0-2488M.ar3.LON2.gblx.net [67.17.71.25]
    5 45 ms 41 ms 41 ms Easynet-LTD-LON.ge-5-0-2.402.ar2.LON3.gblx.net [
    67.17.212.94]
    6 40 ms 37 ms 49 ms ge2-0-1-0.br0.thlon.uk.easynet.net [217.204.60.8
    9]
    7 48 ms 37 ms 41 ms ge0-0-0-0.br0.tclon.uk.easynet.net [195.172.211.
    206]
    8 270 ms 226 ms 221 ms fe1-1-0.ar0.rblon.uk.easynet.net [217.204.60.51]

    9 48 ms 41 ms 41 ms fe4-1.ar0.r2lon.uk.easynet.net [212.134.12.70]
    10 48 ms 41 ms 45 ms fe-0-1-br.slipstream.ultraspeed.co.uk [62.149.32
    .130]
    11 67 ms 45 ms 41 ms fe-0-0-co.matter.ultraspeed.co.uk [62.149.32.131
    ]
    12 61 ms 41 ms * server14.dedicateduk.com [62.149.36.42]
    13 61 ms 41 ms 50 ms server14.dedicateduk.com [62.149.36.42]

    Trace complete.
    Constant ping to boards.ie:

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

    Reply from 82.195.136.250: bytes=32 time=33ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=50ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=45ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=41ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=70ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=44ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=48ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=39ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=47ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=29ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=36ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=48ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=44ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=72ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=41ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=56ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=34ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=47ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=59ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=71ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=31ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=32ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=62ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=74ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=34ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=34ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=50ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=33ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=51ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=30ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=33ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=45ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=36ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=31ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=39ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=29ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=37ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=32ms TTL=60
    Reply from 82.195.136.250: bytes=32 time=60ms TTL=60

    Ping statistics for 82.195.136.250:
    Packets: Sent = 39, Received = 39, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 74ms, Average = 44ms


    I'm off the Fitzwilliam Square mast. Haven't had any major problems...


  • #3
    The Real B-man
    Moderators, Society & Culture Moderators Posts: 3,740 Mod ✭✭✭✭The Real B-man


    clearwire is basically ripwave totally ****e


  • #4
    BeardyGit
    Closed Accounts Posts: 3,946 ✭✭✭BeardyGit


    The Real B-man wrote:
    clearwire is basically ripwave totally ****e

    There it is. I've not idea what 'it' is, but there it is anyway. Helpful, don't you think? :rolleyes:

    Gil


  • #5
    sisyphus
    Closed Accounts Posts: 79 ✭✭sisyphus


    No it's not, it's based on entirely different technology. Uses WiMax versus RipWave's radio waves. I've had it now for almost 2 months and have nothing but praise for it. It's about the only thing (Bar IBB RipWave, which is outside the coverage area) I could get in my place, as my landlady is anal, and doesn't want me installing things in her lovely old house, so it had to be a no-line based connection. Have had absolutely no problems whatsoever with it thus far, and am still getting great speeds.
    I'm just hoping they don't go signing up a few hundred customer to connect to the same site I'm on, as my speeds will prolly drop off to ****e then!


  • #6
    eth0_
    Registered Users, Registered Users 2 Posts: 10,846 ✭✭✭✭eth0_


    The Real B-man wrote:
    clearwire is basically ripwave totally ****e


    You're a fool. What's the odds you don't even HAVE clearwire?

    I had ripwave for a week and they are INCOMPARABLE. Clearwire actually works well. Like all broadband services, there are going to be problems now and then. I've been very impresed with how Clearwire dealt with connection issues I had a month ago.

    Here are my pings (never seen packetloss before tonight) off the Harolds X base station:

    PING www.boards.ie (82.195.136.250): 56 data bytes
    64 bytes from 82.195.136.250: icmp_seq=0 ttl=59 time=48.452 ms
    64 bytes from 82.195.136.250: icmp_seq=1 ttl=59 time=64.932 ms
    64 bytes from 82.195.136.250: icmp_seq=2 ttl=59 time=41.460 ms
    64 bytes from 82.195.136.250: icmp_seq=3 ttl=59 time=54.039 ms
    64 bytes from 82.195.136.250: icmp_seq=4 ttl=59 time=40.924 ms
    64 bytes from 82.195.136.250: icmp_seq=5 ttl=59 time=42.056 ms
    64 bytes from 82.195.136.250: icmp_seq=6 ttl=59 time=53.700 ms
    64 bytes from 82.195.136.250: icmp_seq=7 ttl=59 time=65.831 ms
    64 bytes from 82.195.136.250: icmp_seq=8 ttl=59 time=44.361 ms
    64 bytes from 82.195.136.250: icmp_seq=9 ttl=59 time=57.016 ms
    64 bytes from 82.195.136.250: icmp_seq=10 ttl=59 time=93.697 ms
    64 bytes from 82.195.136.250: icmp_seq=11 ttl=59 time=39.040 ms
    64 bytes from 82.195.136.250: icmp_seq=13 ttl=59 time=38.613 ms
    64 bytes from 82.195.136.250: icmp_seq=14 ttl=59 time=50.995 ms
    64 bytes from 82.195.136.250: icmp_seq=15 ttl=59 time=38.194 ms
    64 bytes from 82.195.136.250: icmp_seq=16 ttl=59 time=92.319 ms
    64 bytes from 82.195.136.250: icmp_seq=17 ttl=59 time=41.928 ms
    64 bytes from 82.195.136.250: icmp_seq=18 ttl=59 time=41.704 ms
    64 bytes from 82.195.136.250: icmp_seq=19 ttl=59 time=37.302 ms
    64 bytes from 82.195.136.250: icmp_seq=20 ttl=59 time=37.154 ms
    64 bytes from 82.195.136.250: icmp_seq=21 ttl=59 time=37.148 ms
    64 bytes from 82.195.136.250: icmp_seq=22 ttl=59 time=53.606 ms
    ^C
    --- www.boards.ie ping statistics ---
    23 packets transmitted, 22 packets received, 4% packet loss
    round-trip min/avg/max/stddev = 37.148/50.658/93.697/15.847 ms

    traceroute to clan-ascii.com (62.149.36.42), 64 hops max, 40 byte packets
    1 192.168.2.1 (192.168.2.1) 2.337 ms 1.382 ms 1.270 ms
    2 85.134.128.3 (85.134.128.3) 68.833 ms 35.407 ms 133.137 ms
    3 fe-0-0-0_0.bdr001.dublin.clearwire.ie (85.134.255.13) 56.866 ms 38.329 ms 42.680 ms
    4 ge-5-0-0.403.ar1.dub1.gblx.net (67.17.211.53) 40.292 ms 31.436 ms 42.169 ms
    5 so0-0-0-2488m.ar3.lon2.gblx.net (67.17.71.25) 47.595 ms 58.727 ms 46.559 ms
    6 easynet-ltd-lon.ge-5-0-2.402.ar2.lon3.gblx.net (67.17.212.94) 48.731 ms 52.899 ms 44.522 ms
    7 ge2-0-1-0.br0.thlon.uk.easynet.net (217.204.60.89) 63.556 ms 83.889 ms 49.450 ms
    8 ge-3-3-0-0.br0.bllon.uk.easynet.net (82.108.6.125) 56.900 ms 56.887 ms 49.330 ms
    9 fe4-0.ar0.r2lon.uk.easynet.net (212.134.12.74) 98.603 ms 50.853 ms 97.023 ms
    10 fe-0-1-br.slipstream.ultraspeed.co.uk (62.149.32.130) 98.484 ms 52.358 ms 45.311 ms
    11 fe-0-0-co.matter.ultraspeed.co.uk (62.149.32.131) 48.661 ms 58.042 ms 56.342 ms
    12 * * *
    13 * *^C


  • Advertisement
  • #7
    Yggr of Asgard
    Registered Users, Registered Users 2 Posts: 5,259 ✭✭✭Yggr of Asgard


    I had some bad performance this afternoon but than I noticed that my MTU settings were kind of funny, so I adapted a MTU=1492 and now I have good surfing again.

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

    Reply from 82.195.136.250: bytes=32 time=30ms TTL=59
    Reply from 82.195.136.250: bytes=32 time=33ms TTL=59
    Reply from 82.195.136.250: bytes=32 time=28ms TTL=59
    Reply from 82.195.136.250: bytes=32 time=39ms TTL=59

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


  • #8
    Cake Fiend
    Registered Users, Registered Users 2 Posts: 5,335 ✭✭✭Cake Fiend


    Anyone got any reports of gaming or VOIP over Clearwire? My connection (business package) is pretty up and down, but I'm attributing that to the modem being on the ground floor until I can get it upstairs (/me shakes fist at passing trucks). I'm hoping to run a small network and a phone through it.


  • #9
    Yggr of Asgard
    Registered Users, Registered Users 2 Posts: 5,259 ✭✭✭Yggr of Asgard


    Sico wrote:
    Anyone got any reports of gaming or VOIP over Clearwire?

    In my house (wireless via Netgear) we have Skype running for hours a day and at the same time I do also broadtalk in or out and surf on my favorite websites. Even if I do a download at the same time the voice quality does not suffer.

    I told clearwire that my main priority is VPN to the office and VOIP (and also VOIP via the VPN to our office). They told me that they have changed my connection and "optimized" it for VOIP and VPN.

    Well I'm happy.

    I remember eircom. started talking on Skype and your webpage came over a 56 kb modem feelling - no more :)


Advertisement