First impressions on ure mywireless

where are those reason.za.net pings? Come on it's for all the warcraft guys. A ping of 100 is decent enough for local warcraft.

georgestrydom, what modem did you have to get a ping of 140? I get a ping of 205, sometimes about 190 if im lucky

..- dot dot dash ;)
 
Perdition:

LoneGunman posted outbound traces (recently in this same thread) and Karnaugh posted inbound traceroutes (yonks ago during the beta-cycle).

--deckert
 
Well let's get some confirmation... LoneGunman please post a traceroute to www.camelot-europe.com

Perhaps ProAsm could also update us on this if he is reading this thread [;)]
 
For Freeek
Pinging reason.za.net [196.34.172.102] with 32 bytes of data:

Reply from 196.34.172.102: bytes=32 time=110ms TTL=59
Reply from 196.34.172.102: bytes=32 time=119ms TTL=59
Reply from 196.34.172.102: bytes=32 time=114ms TTL=59
Reply from 196.34.172.102: bytes=32 time=104ms TTL=59

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

-------and a repeat ping of same url

Pinging reason.za.net [196.34.172.102] with 32 bytes of data:

Reply from 196.34.172.102: bytes=32 time=112ms TTL=59
Reply from 196.34.172.102: bytes=32 time=123ms TTL=59
Reply from 196.34.172.102: bytes=32 time=115ms TTL=59
Reply from 196.34.172.102: bytes=32 time=124ms TTL=59

Ping statistics for 196.34.172.102:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 112ms, Maximum = 124ms, Average = 118ms
 
thanx LoneGunman. 120 hmmmm. I wonder if you have 256kbs or 512 package will pings improve?

I think im gonna get my hands on one of those not so legal wireless companies for a week or so. I will post results. Its 128k package. Can compare pings.

..- dot dot dash ;)
 
LoneGunman, the results on page 5 are ping results, a traceroute (using the tracert command) will show the route the ping packets take to get to the specified address.
 
Perdition..

Here's your traceroute - I get the same result as last night for someone else trying to trace the saix servers I think it was - it just runs outa road and the rest shows as timeouts..

C:\>tracert www.camelot-europe.com
Tracing route to www.camelot-europe.com [193.252.123.35]
over a maximum of 30 hops:

1 97 ms 76 ms 74 ms 66.18.65.105
2 105 ms 97 ms 136 ms gige-0-0-102.rtr-core4-stp.infosat.net [66.18.65
.110]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
etc etc etc - up to 30 hops..
So a tracert doesnt give as much info for some reason, as the pings..

hope this fulfills my contractual obligation :P
Next?
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by LoneGunman</i>
Here's your traceroute - I get the same result as last night for someone else trying to trace the saix servers I think it was - it just runs outa road and the rest shows as timeouts..
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

SAIX blocks some of this stuff.

Give this a try if you want:
http://www.hlembke.de/prod/3dtraceroute/
 
Yep it does thanks [;)] It would appear they are blocking trace requests so it's difficult to determine much information. If it is travelling entirely over fibre (essentially SAT-3) then pings should be a lot better than 430ms.
 
I'm back on but i'd just like to know lonegunman if its possible for you to send me as a zip file or something the mywireless cd cause i swopped my modem out and didn't get a new cd ;/ if so please can u mail me on [email protected] - my drivers/software causing my modem to cause pc to crash in xp and i'm trying to resolve the problem, it wasn't the modem and i tried formatting but only thing i haven't changed is from the software that i installed the system with in december
 
Staind - no problem re the cd - I can make an iso of it, which is safer than zipping contents, assuming you have a cd writer, so you just burn the image.. HOWEVER - the cd itself is 24 megs, and my mail server (and yours probably), wont handle a send of that size.. need a plan 'B'.. maybe if you've a pub ftp, can up the iso image to it..? (if you have or can set up an ftp - mail me private with l/p details and I'll do it no problem..
 
A lot of guys are talking about the distance from the transmitters, and the speed of radio waves; but you are all forgetting about an important fact. MyWireless uses Non-Line Of Sight (NLOS) technology; this means that you don’t receive one single radio wave; you receive multiple waves – refracted off walls, buildings and hills. This makes it much more difficult to calculate the effects of radio wave speeds vs ping times. If this post is a bit late in your argument – please ignore it!
 
staind and lone.... please try setup a direct connection between the 2 of u... like a ftp or something, and test the speeds you get, uploading and downloading directly to eachother. What are your locations, if u are on the same tower, i'd like to know if you can burst beyond your 128k limitation.
 
LoneGunman and others with MyWireless:

Please can you ping the following for me without using the connection for anything else:

63.240.192.246 (a router near the useast battle.net)
europe.battle.net
asia.battle.net

Maybe the ADSL guys could do it too for comparison's sake?

I wanna play World of Warcraft, so this will help my decision greatly. Thanks guys.
 
you cant ping useast. or us. - thats why i included:

63.240.192.246 (a router near the useast battle.net)
 
as requested:

C:\&gt;ping 63.240.192.246

Pinging 63.240.192.246 with 32 bytes of data:

Reply from 63.240.192.246: bytes=32 time=346ms TTL=50
Reply from 63.240.192.246: bytes=32 time=363ms TTL=50
Reply from 63.240.192.246: bytes=32 time=362ms TTL=50
Reply from 63.240.192.246: bytes=32 time=379ms TTL=50

Ping statistics for 63.240.192.246:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 346ms, Maximum = 379ms, Average = 362ms
-------------
C:\&gt;ping europe.battle.net

Pinging europe.battle.net [213.248.106.200] with 32 bytes of data:

Reply from 213.248.106.200: bytes=32 time=433ms TTL=111
Reply from 213.248.106.200: bytes=32 time=413ms TTL=111
Reply from 213.248.106.200: bytes=32 time=430ms TTL=111
Reply from 213.248.106.200: bytes=32 time=427ms TTL=111

Ping statistics for 213.248.106.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 413ms, Maximum = 433ms, Average = 425ms
----------
ping #1
C:\&gt;ping asia.battle.net

Pinging asia.battle.net [211.233.0.49] with 32 bytes of data:

Reply from 211.233.0.49: bytes=32 time=622ms TTL=110
Reply from 211.233.0.49: bytes=32 time=618ms TTL=110
Reply from 211.233.0.49: bytes=32 time=636ms TTL=110
Reply from 211.233.0.49: bytes=32 time=612ms TTL=110

Ping statistics for 211.233.0.49:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 612ms, Maximum = 636ms, Average = 622ms
and
ping #2
C:\&gt;ping asia.battle.net

Pinging asia.battle.net [211.233.0.53] with 32 bytes of data:

Reply from 211.233.0.53: bytes=32 time=623ms TTL=110
Reply from 211.233.0.53: bytes=32 time=619ms TTL=110
Reply from 211.233.0.53: bytes=32 time=614ms TTL=109
Reply from 211.233.0.53: bytes=32 time=611ms TTL=109

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

thereyago :)
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X