Packet loss

#1

tech at bigpond want me to test packet loss.

how do i do this

#2

Ugh just started having some net problems recently with occasional lag spikes in cod4 etc so i decided to do a ping test and all i got was constant “Request Timed Out” messages, and a summary of 100% Packet Loss

You think this is a modem/router issue or ISP?

#3

They may just be doing maintenance on the exchange if your net completely dropped out. If a restart of your modem did nothing, then I’d say it is ISP related. I have very rarely seen anybody have net problems due to their own hardware.

#4

Ah ok, thanx Nipper. I just did a ping test to this website and got 8ms with 0%packet loss O_o

Maybe I was only getting the timeouts due to me pinging the telstra dns?

I thought it was kind of strange considering i still had full connectivity, just a timeout of cod4/vent/xfire and then a bad ping for about 15 minutes

EDIT: Did a few more ping tests to various websites, any telstra related websites return only timeouts and 100% packetloss, whereas other websites are 0% packetloss but varying pings

#5

Yeah, bit hard to diagnose but if it remains good, don’t waste any more time chasing the problem.

Just keep an eye on what time you generally get net problems if they do start becoming more frequent. If you can spot a pattern it may be similar to my problem which I have displayed in this thread.

Also, your best bet for testing packet loss would be the primary dns of your ISP. I think this may change based on the state you live in based on ISP.

#6

That’s interesting. Best to test it again at a later time, may very well be Telstra doing some work on their end. I wouldn’t worry about it too much at this stage.

You can do a “tracert” instead of a ping test to see where the packets are getting dropped.

#7

when you are sitting on the pc doing nothing, should you be sending and receiving packets?

Mine does?!

#8

i do also send and receive packets while im just at idle… so it wouldnt be unusual for yours to be as well.

#9

unless your is fuked also…lol

#10

mine is a mac they work perfectly

most of the time

#11

It’s normal to be sending and receiving a small number of packets, so small that it is negligable whether it uses any of your quota.

If it is continuously sending and receiving considerable amounts at idle, then there is an application that is clearly using it up. It could be a P2P program, windows update, antivirus updates etc…

#12

I nearly smashed my PC monday night, fuking cant even watch a you tube video, sure as shit cant play when you 400+ ping.

I am home today and had a bash…42 ping, ened up after an hour with something like 70 kills 20 deaths and that was fuking around getting my medals for guns. Really enjoyed and and forgot what it was like to play a normal fuking game.

Have a Telstra Field tech calling me sometime today and hopefully he can do something (like take the fuking neighbors adsl of my line :mad2:)

Its gotten so bad that the congestion issue no longer effects me from 6-9pm, but from around 5-10 and on weekends now as well.

#13

LMAO, It’s like reading my own thoughts.

You’ll most likely have the same experience as me.

A Telstra tech has been to my place before, he straight away agreed with me that there was a big problem. He called the call centre to tell them, and they didn’t let him get a word in. FFS, the technician is TELLING them there is a problem, why argue with your own technicians? Doesn’t make any sense to me.

It’s sad because as far as I am concerned, the only complaint people have about Telstra is related to the offshore call centres.

The tech that came to my place, my next door neighbours house and the house beside that and the house beside that and… I think you get the idea. Even though the technician was practically arguing over the phone talking saying that there was a problem that was not related in anyway to my hardware devices, they still haven’t given the go ahead to fix the problem. The funniest thing is, the technician I am talking about lives around the corner from me as also has the exact same problems as he is on the exact same RIM.

Anyway, wishing you to have more luck than me. You should have more connections in the organisation than me, haha.

#14

LMFAO

They did something and my speed is stable as at 4.40pm. Lets see how it handles the after work traffic…my prediction

it will still be shit and ill have to go through the whole thing again tomorrow

on a brighter note, Telstra just got fined 18 MILLION Dollars for locking competitors out of slots at local exchanges…

bit of Karma there for you Telstra

#15

useless…as expected and in your situation. Confirmed congestion…cant do shit about it until the exchange is upgraded…see ya in 2013

tech said they might replace the card at the exchange but it could be next week or 6 months
:mad2:

incidentally just did a download of a file…started at 1500kbps and went to 189 in a few seconds…

#16

Yep, it’s a joke but we’ve got nowhere else to go. Bugger using wireless as it is too expensive.

#17

i full well intend to get my adsl at 20% of the going rate after ive finished. Im not paying for this shit. Im happy to pay a potion to do my downloads over night in non peak times but i aint paying to sit on dial up in peak times

#18

basically just the same pingtest that you did before via cmd, test to the primary telstra DNS.

Do 100 or so requests (so type “-n 100” on the end of the ip being tested)

At the end of it, it will give a summary including the percentage of packet loss.

#19

Here’s an example

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:UsersADAM_MAIN>ping 192.231.203.132 -n 15

Pinging 192.231.203.132 with 32 bytes of data:
Reply from 192.231.203.132: bytes=32 time=558ms TTL=61
Reply from 192.231.203.132: bytes=32 time=481ms TTL=61
Reply from 192.231.203.132: bytes=32 time=489ms TTL=61
Reply from 192.231.203.132: bytes=32 time=487ms TTL=61
Reply from 192.231.203.132: bytes=32 time=478ms TTL=61
Reply from 192.231.203.132: bytes=32 time=432ms TTL=61
Reply from 192.231.203.132: bytes=32 time=500ms TTL=61
Reply from 192.231.203.132: bytes=32 time=484ms TTL=61
Reply from 192.231.203.132: bytes=32 time=484ms TTL=61
Reply from 192.231.203.132: bytes=32 time=406ms TTL=61
Reply from 192.231.203.132: bytes=32 time=397ms TTL=61
Reply from 192.231.203.132: bytes=32 time=450ms TTL=61
Reply from 192.231.203.132: bytes=32 time=474ms TTL=61
Reply from 192.231.203.132: bytes=32 time=478ms TTL=61
Reply from 192.231.203.132: bytes=32 time=510ms TTL=61

[COLOR=Gray]Ping statistics for 192.231.203.132:
Packets: Sent = 15, Received = 15,[COLOR=Red] Lost = 0 (0% loss)[/COLOR],
Approximate round trip times in milli-seconds:
Minimum = 397ms, Maximum = 558ms, Average = 473ms[/COLOR]

C:UsersADAM_MAIN>

#20

whos s that, why is the time so high???