Patience, grasshopper

I was on the phone for about 30 minutes with a technician tonight trying to diagnose my cable modem issue. Surprisingly the guy was actually helpful and I didn't get any of the 'have you tried closing some of your applications' bullshit that you usually get from Tier 1.

For the nerd-curious, this is what we tried:

1) 3 x Ping 172.19.105.16 -n 30 -l 1472 dhcp server

Ping statistics for 172.19.105.16:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 81ms, Average = 42ms

Ping statistics for 172.19.105.16:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 80ms, Average = 46ms

Ping statistics for 172.19.105.16:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 66ms, Average = 40ms

--> 0 loss, looks good


2) netstat -s -p udp

UDP Statistics for IPv4

Datagrams Received = 1459
No Ports = 258
Receive Errors = 0
Datagrams Sent = 1479

--> no udp (gaming protocol) loss, looks good

3) ping 198.133.219.25 -n 30 san jose

Ping statistics for 198.133.219.25:
Packets: Sent = 30, Received = 29, Lost = 1 (3% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 133ms, Average = 111ms

Ping statistics for 198.133.219.25:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 99ms, Maximum = 181ms, Average = 116ms

--> 0 loss, looks good

4) ipconfig /release
power off modem
update config file on modem
boot it back up again
--> no difference

Technician's notes:
--> high flop count on modem
--> high p3 counts
--> signals seem generally excellent

Possible modem error > They have scheduled a technician to come out and try to diagnose further. In the meantime, I'll get back to knitting my scarf. Do have fun while you're fragging each other for me, won't you? Beeeches.