When it works, it's great...

DaveBuchanan1337

Well-Known Member
Joined
Feb 12, 2005
Messages
254
Reaction score
0
When it's broken, it's terrible.

But seriously, my service level has increased ten-fold over the past two weeks. Streaming radio @ 192kbps works crystal clear even while I have 3 other users surfing and downloading simultaneously!

Thanks, WBS

(My sentiments may not be an accurate representation of the feelings of other clients. IANAL.)
 
yeah but its not out of the woods yet, lets not forget the biggest issue hasn't been dealt with, that being the cap. If they can work out a way to make extra gibs affordable after i hit my cap in 3 hours, then they officially rock and can come to my place for sex anytime
 
Things seams to be taking shape


Ping statistics for 196.30.31.120:
Packets: Sent = 5873, Received = 5775, Lost = 98 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 697ms, Average = 85ms :)
 
Last edited:
native said:
Things seams to be taking shape


Ping statistics for 196.30.31.120:
Packets: Sent = 5873, Received = 5775, Lost = 98 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 697ms, Average = 85ms :)

I don't know hey... my Ping result is not so long as yours, but it's still enough data to give me a bad reading:

Ping statistics for 196.30.31.120:
Packets: Sent = 382, Received = 382, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 2363ms, Average = 235ms

Now I didn't have any packet loss... but a ping of average 235ms is BAD :(
I sure hope it's something on the network that'll be fixed... however, it's been bad for the past week now.
 
This is actually an example of a "good ping" for me, I wish I knew how to get SWE2 to ping x number of times via the web IP Tools interface.
Code:
[size=3]196.30.31.120 (iburst.co.za)

PING 196.30.31.120 (196.30.31.120) from 196.46.6x.y : 56(84) bytes of data.
64 bytes from 196.30.31.120: icmp_seq=1 ttl=126 time=171 ms
64 bytes from 196.30.31.120: icmp_seq=2 ttl=126 time=179 ms
64 bytes from 196.30.31.120: icmp_seq=3 ttl=126 time=238 ms
64 bytes from 196.30.31.120: icmp_seq=4 ttl=126 time=139 ms
64 bytes from 196.30.31.120: icmp_seq=5 ttl=126 time=120 ms

--- 196.30.31.120 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4038ms
[B]rtt min/avg/max/mdev = 120.291/169.833/238.386/40.457 ms[/B]


196.30.31.100 (Reverse lookup failed)

PING 196.30.31.100 (196.30.31.100) from 196.46.6x.y : 56(84) bytes of data.
64 bytes from 196.30.31.100: icmp_seq=1 ttl=255 time=87.3 ms
64 bytes from 196.30.31.100: icmp_seq=2 ttl=255 time=182 ms
64 bytes from 196.30.31.100: icmp_seq=3 ttl=255 time=277 ms
64 bytes from 196.30.31.100: icmp_seq=4 ttl=255 time=95.9 ms
64 bytes from 196.30.31.100: icmp_seq=5 ttl=255 time=452 ms

--- 196.30.31.100 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4043ms
[B]rtt min/avg/max/mdev = 87.391/219.236/452.539/135.459 ms[/B][/size]
Out of boredom, I've just done another quick ping, and it got duplicates...why...?
Code:
[size=3]196.30.31.100 (Reverse lookup failed)

PING 196.30.31.100 (196.30.31.100) from 196.46.6x.y : 56(84) bytes of data.
64 bytes from 196.30.31.100: icmp_seq=1 ttl=255 time=82.1 ms
64 bytes from 196.30.31.100: icmp_seq=2 ttl=255 time=131 ms
64 bytes from 196.30.31.100: icmp_seq=3 ttl=255 time=416 ms
64 bytes from 196.30.31.100: icmp_seq=3 ttl=255 time=1049 ms ([B]DUP![/B])
64 bytes from 196.30.31.100: icmp_seq=4 ttl=255 time=126 ms
64 bytes from 196.30.31.100: icmp_seq=5 ttl=255 time=122 ms

--- 196.30.31.100 ping statistics ---
5 packets transmitted, 5 received, [B]+1 duplicates[/B], 0% loss, time 4037ms
[B]rtt min/avg/max/mdev = 82.172/321.297/1049.751/344.166 ms[/B], [B][COLOR=DeepSkyBlue]pipe 2[/COLOR][/B]


196.30.31.120 (iburst.co.za)

PING 196.30.31.120 (196.30.31.120) from 196.46.6x.y : 56(84) bytes of data.
64 bytes from 196.30.31.120: icmp_seq=1 ttl=126 time=149 ms
64 bytes from 196.30.31.120: icmp_seq=2 ttl=126 time=93.4 ms
64 bytes from 196.30.31.120: icmp_seq=2 ttl=126 time=234 ms ([B]DUP![/B])
64 bytes from 196.30.31.120: icmp_seq=3 ttl=126 time=87.0 ms
64 bytes from 196.30.31.120: icmp_seq=4 ttl=126 time=129 ms
64 bytes from 196.30.31.120: icmp_seq=5 ttl=126 time=184 ms

--- 196.30.31.120 ping statistics ---
5 packets transmitted, 5 received, [B]+1 duplicates[/B], 0% loss, time 4044ms
[B]rtt min/avg/max/mdev = 87.075/146.517/234.780/51.432 ms[/B][/size]
Also, what does SWE2 mean there with pipe2? - perhaps more importantly what is it smoking in that 2nd pipe I wonder...:D
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X