Tuesday, February 9, 2010

DSL problems

I have been having a frustrating month with my ISP and their apparent inability to fix on going DSL problems. The only plus side to all of this is finding a new reply from linux's ping command. My connection is often so bad that a high level of packet corruption occurs. Its nice to know this can be easily seen. Its too bad you don't see this from Microsoft's ping.exe.



> ping 202.188.0.133
PING 202.188.0.133 (202.188.0.133) 56(84) bytes of data.
64 bytes from 202.188.0.133: icmp_seq=3 ttl=247 time=22.1 ms
64 bytes from 202.188.0.133: icmp_seq=4 ttl=247 time=18.4 ms
64 bytes from 202.188.0.133: icmp_seq=5 ttl=247 time=18.1 ms
64 bytes from 202.188.0.133: icmp_seq=6 ttl=247 time=43.2 ms
64 bytes from 202.188.0.133: icmp_seq=7 ttl=247 time=15.8 ms
64 bytes from 202.188.0.133: icmp_seq=8 ttl=247 time=18.5 ms
64 bytes from 202.188.0.133: icmp_seq=9 ttl=247 time=24.3 ms
64 bytes from 202.188.0.133: icmp_seq=10 ttl=247 time=20.1 ms
64 bytes from 202.188.0.133: icmp_seq=11 ttl=247 time=33.1 ms
64 bytes from 202.188.0.133: icmp_seq=12 ttl=247 time=35.6 ms
64 bytes from 202.188.0.133: icmp_seq=13 ttl=247 time=18.8 ms
64 bytes from 202.188.0.133: icmp_seq=14 ttl=247 time=17.3 ms
64 bytes from 202.188.0.133: icmp_seq=15 ttl=247 time=35.4 ms
64 bytes from 202.188.0.133: icmp_seq=16 ttl=247 time=64.2 ms
64 bytes from 202.188.0.133: icmp_seq=17 ttl=247 time=61.0 ms
64 bytes from 202.188.0.133: icmp_seq=19 ttl=247 time=25.2 ms
64 bytes from 202.188.0.133: icmp_seq=21 ttl=247 time=33.1 ms
64 bytes from 202.188.0.133: icmp_seq=22 ttl=247 time=24.4 ms
64 bytes from 202.188.0.133: icmp_seq=23 ttl=247 time=20.4 ms
wrong data byte #25 should be 0x19 but was 0x18
#16 10 11 12 13 14 15 16 17 18 18 1a 1b 1c 1d 1e 3f 20 21 22 23 24 25 26 27
28 29 2a 2b 2c 2f 2e 2f
#48 30 31 32 73 34 35 36 37
64 bytes from 202.188.0.133: icmp_seq=24 ttl=247 time=18.4 ms
64 bytes from 202.188.0.133: icmp_seq=25 ttl=247 time=30.2 ms
64 bytes from 202.188.0.133: icmp_seq=26 ttl=247 time=24.5 ms
64 bytes from 202.188.0.133: icmp_seq=27 ttl=247 time=41.2 ms
64 bytes from 202.188.0.133: icmp_seq=28 ttl=247 time=17.8 ms
64 bytes from 202.188.0.133: icmp_seq=29 ttl=247 time=20.8 ms
^C
--- 202.188.0.133 ping statistics ---
29 packets transmitted, 25 received, 13% packet loss, time 28110ms
rtt min/avg/max/mdev = 15.864/28.132/64.273/12.732 ms


Hopefully being shuffled around to 4 different technicians (not counting SLA nazi's and phone support) and finally having some cards replaced on the switch is getting somewhere, but from the lack of communication between the telco and their repair contractors it looks like it is time to try my luck with some 3G broadband. Since the problem only really happens between 8am and 8pm, I'm thinking it is heat and bad equipment related...but i'm just a customer, what would I know? Connection dropped 2 times while writing this.

No comments:

Post a Comment