 bbplumber
join:2009-01-14 Mission Viejo, CA
| reply to sashwa Re: Digitel - High number of TX errors
ISP: Digitel Philippines (out of Bulacan) Modem: Prolink Hurricane 9200AR Using that as router + WRT-54g (issue appears whether router is there or not) VOIP applications: SKYPE, MagicJack, Ichat Experiences Stalls, freezes, etc when using safari or firefox, long delays when waiting to contact server.
When I do a traceroute from her PC, I see large latency to the first router, and a large amount of jitter.
traceroute to www.cnn.com (157.166.226.25), 64 hops max, 40 byte packets 1 www.cnn.com (157.166.226.25) 1.958 ms 1.878 ms 1.785 ms 2 dsldevice.domain.name (192.168.1.1) 3.191 ms 2.875 ms 3.013 ms 3 124.217.52.1 (124.217.52.1) 404.889 ms 718.402 ms 715.541 ms
traceroute to www.l.google.com (74.125.95.104), 64 hops max, 40 byte packets 1 iw-in-f104.google.com (74.125.95.104) 2.589 ms 1.841 ms 1.851 ms 2 dsldevice.domain.name (192.168.1.1) 3.348 ms 2.946 ms 2.820 ms 3 124.217.52.1 (124.217.52.1) 252.796 ms 71.483 ms 95.817 ms
When pinging, I don't seem to be experiencing any packet loss.
PING 124.217.52.1 (124.217.52.1): 56 data bytes 64 bytes from 124.217.52.1: icmp_seq=0 ttl=253 time=66.527 ms 64 bytes from 124.217.52.1: icmp_seq=1 ttl=253 time=261.887 ms 64 bytes from 124.217.52.1: icmp_seq=2 ttl=253 time=159.540 ms 64 bytes from 124.217.52.1: icmp_seq=3 ttl=253 time=627.747 ms 64 bytes from 124.217.52.1: icmp_seq=4 ttl=253 time=446.558 ms 64 bytes from 124.217.52.1: icmp_seq=5 ttl=253 time=391.545 ms 64 bytes from 124.217.52.1: icmp_seq=6 ttl=253 time=338.709 ms 64 bytes from 124.217.52.1: icmp_seq=7 ttl=253 time=209.700 ms 64 bytes from 124.217.52.1: icmp_seq=8 ttl=253 time=90.344 ms 64 bytes from 124.217.52.1: icmp_seq=9 ttl=253 time=52.011 ms 64 bytes from 124.217.52.1: icmp_seq=10 ttl=253 time=54.467 ms
Anyway, when looking at the stats on her modem, the large # of TX Errors. What's the cause of a TX error?
Interface Tx pkt Tx err Tx drop eth0 278474 0 0 8_35 167874 59355 0 1_39 1 0 0
Downstream Upstream SNR Margin (dB) 28.8 39.5 Attenuation (dB) 9.5 6.0 Output Power (dBm) -1.0 6.0 Attainable Rate (Kbps) 22120 116 Rate (Kbps) 128 64 K (number of bytes in DMT frame) 3 2 R (number of check bytes in RS code word) 14 0 S (RS code word size in DMT frame) 0.50 0.88 D (interleaver depth) 1 1 Delay (msec) 0.12 0.22 FEC 3 0 CRC 2 2 Total ES 2 3 Total SES 0 0 Total UAS 0 0
Again, that TX error is what worries me. My question though, is this the typical behavior when trying to send out too much traffic or is it indicitive of some other issue?
I know her B/W profile is a bit low on the upstream but it should be sufficient for ichat (40Kbps), Skype (24Kbps on the lowest codec) and when websurfing, there shouldn't be stalls on the downstream (I'm guessing upstream acks are getting delayed or dropped).
I've made the recommendation that she works with her ISP to upgrade her service. At my last communication she stated that the ISP wasn't letting her upgrade until she lived out her current contract.(I'll say that I'm amused that they don't want to take more money from her but, then again, I'm not surprised with the business practices.)
Anyway, any bit of help would be appreciated. Just want to make sure I'm not chasing a red herring here.
Thanks |