Sentech coming right ???

S

Sliver

Well-Known Member
Joined
Jul 25, 2003
Messages
125
Reaction score
0
Location
.
After the long network outage this evening i decided to do some basic testing, heres what i found :

Ping statistics for 196.35.72.14:
Packets: Sent = 136, Received = 136, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 626ms, Average = 129ms


Now either sentech have pulled a magic rabbit out of somebodies @rse or i am one of very few people sitting on the network at the moment. For mine and everyone elses sake i hope it is the first.

At least now i have seen what the network is capable of when it comes down to basic ping's and packet loss, hopefuly this is the day a lot of us have been waiting for.

Looking forward to better things

Sliver
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote">


Now either sentech have pulled a magic rabbit out of somebodies @rse or i am one of very few people sitting on the network at the moment. For mine and everyone elses sake i hope it is the first.

<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

It's the second[V]

MW128, Tower <b>60</b>(Northpark Plaza), Signal:16%,S-N-L: 7, BER: 45%
 
WoooHa! I can't recall the last time I saw anything like this.
Probably back in May.

Resolving host 'www.sentech.co.za'
Pinging [66.18.65.115] x 20 with 32 bytes of data

Reply from 66.18.65.115 : bytes=32 : time=138 ms
Reply from 66.18.65.115 : bytes=32 : time=115 ms
Reply from 66.18.65.115 : bytes=32 : time=117 ms
Reply from 66.18.65.115 : bytes=32 : time=97 ms
Reply from 66.18.65.115 : bytes=32 : time=114 ms
Reply from 66.18.65.115 : bytes=32 : time=116 ms
Reply from 66.18.65.115 : bytes=32 : time=117 ms
Reply from 66.18.65.115 : bytes=32 : time=98 ms
Reply from 66.18.65.115 : bytes=32 : time=115 ms
Reply from 66.18.65.115 : bytes=32 : time=97 ms
Reply from 66.18.65.115 : bytes=32 : time=114 ms
Reply from 66.18.65.115 : bytes=32 : time=115 ms
Reply from 66.18.65.115 : bytes=32 : time=116 ms
Reply from 66.18.65.115 : bytes=32 : time=118 ms
Reply from 66.18.65.115 : bytes=32 : time=119 ms
Reply from 66.18.65.115 : bytes=32 : time=120 ms
Reply from 66.18.65.115 : bytes=32 : time=121 ms
Reply from 66.18.65.115 : bytes=32 : time=122 ms
Reply from 66.18.65.115 : bytes=32 : time=108 ms
Min=97 : Max=301 : Ave=123 ms : Packetloss = 0%

<font size="1"><font color="black">Bay of Plenty :</font id="black"><font color="blue"> Signal 48% - SNL 17 - ber 71% :</font id="blue"><font color="green"> D-Link DI-604 - PPPoE :</font id="green"><font color="orange"> 8dBi Patch Antenna :</font id="orange"> Firmware 4.2.1.8</font id="size1">
 
Guys ... while I'd love to believe this is comming right I'm certain it's just low user to bandwidth ratio we're seeing ....

Give it till the morning - barring another outage of course.
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by regardtv</i>
<br />Guys ... while I'd love to believe this is comming right I'm certain it's just low user to bandwidth ratio we're seeing ....

Give it till the morning - barring another outage of course.
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

If you are right we at least now have proof of why we are all suffering extremely slack service.
 
Well Well Well, just did a rodent speed test-to find my bandwidth reading is 283.30kbps with my 256k package!!

-----------------------------------------------------------
Reality is boring for those who dont know ANYTHING about it.
 
Welcome back online everyone:

Resolving host 'www.sentech.co.za'
Pinging [66.18.65.115] x 10 with 32 bytes of data

Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : bytes=32 : time=208 ms
Reply from 66.18.65.115 : bytes=32 : time=117 ms
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : Timed out
Reply from 66.18.65.115 : bytes=32 : time=107 ms
Reply from 66.18.65.115 : bytes=32 : time=113 ms
Reply from 66.18.65.115 : bytes=32 : time=157 ms
Reply from 66.18.65.115 : bytes=32 : time=135 ms
Reply from 66.18.65.115 : bytes=32 : time=136 ms
Min=107 : Max=208 : Ave=139 ms : Packetloss = 30%
 
<blockquote id="quote"><font size="1" face="Verdana, Arial, Helvetica" id="quote">quote:<hr height="1" noshade id="quote"><i>Originally posted by Razer0</i>
<br />Well Well Well, just did a rodent speed test-to find my bandwidth reading is 283.30kbps with my 256k package!!
<hr height="1" noshade id="quote"></blockquote id="quote"></font id="quote">

My RoDent speed test gives

Not Found

The requested URL /meter.php was not found on this server.
Apache Server at rodent.za.net Port 80

but it gives a result in the url http://rodent.za.net/meter.php?kbps=47.7


_________________________________________________________________________
No more catenna, now its a custenna
 
--- www.is.co.za ping statistics ---
27152 packets transmitted, 26895 received, 0% packet loss, time 28494496ms
rtt min/avg/max/mdev = 60.310/134.759/2763.899/90.006 ms, pipe 3
 
PING www.sentech.co.za (66.18.65.115): 56 data bytes
64 bytes from 66.18.65.115: icmp_seq=0 ttl=249 time=115.495 ms
64 bytes from 66.18.65.115: icmp_seq=2 ttl=249 time=95.699 ms
64 bytes from 66.18.65.115: icmp_seq=3 ttl=249 time=96.363 ms
64 bytes from 66.18.65.115: icmp_seq=4 ttl=249 time=112.396 ms
64 bytes from 66.18.65.115: icmp_seq=5 ttl=249 time=92.500 ms
64 bytes from 66.18.65.115: icmp_seq=6 ttl=249 time=190.973 ms
64 bytes from 66.18.65.115: icmp_seq=7 ttl=249 time=91.026 ms
64 bytes from 66.18.65.115: icmp_seq=8 ttl=249 time=132.358 ms
64 bytes from 66.18.65.115: icmp_seq=9 ttl=249 time=136.705 ms
64 bytes from 66.18.65.115: icmp_seq=10 ttl=249 time=91.620 ms
--- www.sentech.co.za ping statistics ---
11 packets transmitted, 10 packets received, 9% packet loss
round-trip min/avg/max/stddev = 91.026/115.513/190.973/29.826 ms

not to bad but we dont use such little packets lets have another look ...

PING www.sentech.co.za (66.18.65.115): 504 data bytes
512 bytes from 66.18.65.115: icmp_seq=1 ttl=249 time=296.794 ms
512 bytes from 66.18.65.115: icmp_seq=4 ttl=249 time=235.979 ms
512 bytes from 66.18.65.115: icmp_seq=6 ttl=249 time=275.549 ms
512 bytes from 66.18.65.115: icmp_seq=7 ttl=249 time=298.367 ms
512 bytes from 66.18.65.115: icmp_seq=8 ttl=249 time=240.094 ms
512 bytes from 66.18.65.115: icmp_seq=11 ttl=249 time=357.347 ms
512 bytes from 66.18.65.115: icmp_seq=12 ttl=249 time=395.903 ms
512 bytes from 66.18.65.115: icmp_seq=13 ttl=249 time=320.330 ms
512 bytes from 66.18.65.115: icmp_seq=14 ttl=249 time=374.068 ms
512 bytes from 66.18.65.115: icmp_seq=15 ttl=249 time=233.951 ms
--- www.sentech.co.za ping statistics ---
16 packets transmitted, 10 packets received, 37% packet loss
round-trip min/avg/max/stddev = 233.951/302.838/395.903/55.647 ms
 
I get the feeling things are getting better. Whilst downloading from ftp.is.co.za at ± 12 kB/s, I get the following pings...

Ping statistics for 66.18.65.115:
Packets: Sent = 20, Received = 19, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 344ms, Average = 108ms

Something definately changed during the "power outage" last night.

Headend
Tower: Mintek (82 was 12) - Signal: 19% - Firmware: 4.2.1.8 - 128k - Smoothwall and PPPoE
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X