bin3
Senior Member
- Joined
- Jun 22, 2005
- Messages
- 976
- Reaction score
- 15
I am one of those poor fools that fell for MyWireless: I just had to have anything that was not Telkom. Sadly, after a year of struggling, as a power user there is just no way I can recommend MyWireless to anybody. It's fine for your granny or maybe your kid brother; but if you want to do anything except browsing, - learn morse code ...
This is just my own, personal, biased opinion, enforced by struggling through a year of MyHopeless ...
My question to the community is this :
Why do I get 0% packet loss to my tower, but consistently get > 20% packet loss to any international site as soon as SenTech is under load ?
As far as I can calculate SenTech can provide better bandwidth by buying an ADSL connection for each tower; I just don't understand why ...
Pinging www.sentech.co.za ...
Pinging www.sentech.co.za [66.18.65.124] with 32 bytes of data:
Reply from 66.18.65.124: bytes=32 time=78ms TTL=250
Reply from 66.18.65.124: bytes=32 time=375ms TTL=250
Reply from 66.18.65.124: bytes=32 time=187ms TTL=250
Reply from 66.18.65.124: bytes=32 time=187ms TTL=250
Reply from 66.18.65.124: bytes=32 time=203ms TTL=250
Reply from 66.18.65.124: bytes=32 time=203ms TTL=250
Ping statistics for 66.18.65.124:
Packets: Sent = 41, Received = 41, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 594ms, Average = 205ms
Control-C
---------------------------------------------------------
Pinging www.google.co.za in the same time interval ...
C:\>ping -t www.google.com
Pinging www.l.google.com [216.239.59.103] with 32 bytes of data:
Reply from 216.239.59.103: bytes=32 time=813ms TTL=241
Reply from 216.239.59.103: bytes=32 time=438ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Reply from 216.239.59.103: bytes=32 time=719ms TTL=241
Request timed out.
Reply from 216.239.59.103: bytes=32 time=500ms TTL=241
Reply from 216.239.59.103: bytes=32 time=953ms TTL=241
Reply from 216.239.59.103: bytes=32 time=578ms TTL=241
Reply from 216.239.59.103: bytes=32 time=547ms TTL=241
Request timed out.
Reply from 216.239.59.103: bytes=32 time=547ms TTL=241
Request timed out.
Request timed out.
Reply from 216.239.59.103: bytes=32 time=609ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.103: bytes=32 time=531ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Reply from 216.239.59.103: bytes=32 time=532ms TTL=241
Reply from 216.239.59.103: bytes=32 time=563ms TTL=241
Ping statistics for 216.239.59.103:
Packets: Sent = 29, Received = 22, Lost = 7 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 438ms, Maximum = 953ms, Average = 451ms
Control-C
------------------------------------------------------------
So - My end conclusion is this : I am paying SuckTech X amount of money each month but they are throwing away every 4th - 5th packet I send as soon as they get any type of load. This is after they succesfully accepted the packet, i.e. 0% packet loss to my tower, 25% packet loss AFTER IT ENTERS THEIR INFRASTRUCTURE.
If they can't even manage the transit in their own infrastructure, how on earth will they manage any other type of load ...
--------------------------------------------------------------
Sadly still on Sentech until some techie toggles a switch and plugs a cable ...
This is just my own, personal, biased opinion, enforced by struggling through a year of MyHopeless ...
My question to the community is this :
Why do I get 0% packet loss to my tower, but consistently get > 20% packet loss to any international site as soon as SenTech is under load ?
As far as I can calculate SenTech can provide better bandwidth by buying an ADSL connection for each tower; I just don't understand why ...
Pinging www.sentech.co.za ...
Pinging www.sentech.co.za [66.18.65.124] with 32 bytes of data:
Reply from 66.18.65.124: bytes=32 time=78ms TTL=250
Reply from 66.18.65.124: bytes=32 time=375ms TTL=250
Reply from 66.18.65.124: bytes=32 time=187ms TTL=250
Reply from 66.18.65.124: bytes=32 time=187ms TTL=250
Reply from 66.18.65.124: bytes=32 time=203ms TTL=250
Reply from 66.18.65.124: bytes=32 time=203ms TTL=250
Ping statistics for 66.18.65.124:
Packets: Sent = 41, Received = 41, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 594ms, Average = 205ms
Control-C
---------------------------------------------------------
Pinging www.google.co.za in the same time interval ...
C:\>ping -t www.google.com
Pinging www.l.google.com [216.239.59.103] with 32 bytes of data:
Reply from 216.239.59.103: bytes=32 time=813ms TTL=241
Reply from 216.239.59.103: bytes=32 time=438ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Reply from 216.239.59.103: bytes=32 time=719ms TTL=241
Request timed out.
Reply from 216.239.59.103: bytes=32 time=500ms TTL=241
Reply from 216.239.59.103: bytes=32 time=953ms TTL=241
Reply from 216.239.59.103: bytes=32 time=578ms TTL=241
Reply from 216.239.59.103: bytes=32 time=547ms TTL=241
Request timed out.
Reply from 216.239.59.103: bytes=32 time=547ms TTL=241
Request timed out.
Request timed out.
Reply from 216.239.59.103: bytes=32 time=609ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Request timed out.
Request timed out.
Request timed out.
Reply from 216.239.59.103: bytes=32 time=531ms TTL=241
Reply from 216.239.59.103: bytes=32 time=594ms TTL=241
Reply from 216.239.59.103: bytes=32 time=532ms TTL=241
Reply from 216.239.59.103: bytes=32 time=563ms TTL=241
Ping statistics for 216.239.59.103:
Packets: Sent = 29, Received = 22, Lost = 7 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 438ms, Maximum = 953ms, Average = 451ms
Control-C
------------------------------------------------------------
So - My end conclusion is this : I am paying SuckTech X amount of money each month but they are throwing away every 4th - 5th packet I send as soon as they get any type of load. This is after they succesfully accepted the packet, i.e. 0% packet loss to my tower, 25% packet loss AFTER IT ENTERS THEIR INFRASTRUCTURE.
If they can't even manage the transit in their own infrastructure, how on earth will they manage any other type of load ...
--------------------------------------------------------------
Sadly still on Sentech until some techie toggles a switch and plugs a cable ...