1 edit | [Speed Problem] Slow speed problem. Wireshark pic attached I have been having speed troubles for a few months it seems, but have finally been able to run some test. I am on Elite dry loop and have never had any trouble getting a good 5MB+. I believe my snr and noise aren't all that great, but no problems in the 5 or so years I've have been running this speed.... until recently.
Looking at the faq for wireshark testing, is this a DSLAM issue?
5100b readout:
Rx Tx
140 Current Rate 6016 768
141 Previous Rate 0 0
142 DSL Max Rate - -
143 DSL Min Rate - -
144 Current ATTN DR 6016 -
145 Current SNRM 8.5 11.0
146 Current LATN - -
147 Current SATN 54.0 -
148 Current TP - 5.5
Anything I can check on my end? I tried straight in the outside network box and I have used both the Speedstream 5100 and 5100B with the same problem. Any help or suggestions here or is this for the ATT Direct forum? Or maybe a call to ATT?
Thanks for all the help!!
Cheers!
Bob
|
|
 wayjacPremium,MVM
join:2001-12-22
Indy | said by wishfull1:Looking at the faq for wireshark testing, is this a DSLAM issue? The stats show that the sync rates [line 140] are correct for the elite package
Line 145 is too low for the elite package
Line 147 is too high for the elite package
What were the numbers when connected at the outside network box |
|
 d_lBarsoomPremium,MVM
join:2002-12-08
Reno, NV
kudos:7 | reply to wishfull1
Are you having speed problems in the evenings? The Wireshark graph shows TCP transit delays that most likely occur on the backbone to the test site. These seem to happen during the busy daytime hours.
What do the techreadout lines 163 through 185 look like?
--
TCE Weather |
|
| Well wouldn't you know as soon as I make a post, I am back full speed. When I do a speed test thru speedtest or any other site, it varies between .5MB/s and 5MB thru out the day and evening. These Wireshark captures are using the download on the faq page.
Here is 160-193
15 Min 24 Hour Yesterday
160 Time Elapsed 608 86400 86400
161 Chan Received Blks 35927 35716170 30628445
162 Chan Transmitted Blks 35927 35716170 30628445
163 Chan Corrected Blks 0 27 27
164 Chan Uncorrected Blks 0 3638 2958
165 HEC Vcnt - - -
166 HEC Tcnt - - -
167 HEC Ucnt - - -
168 ICBE - - -
169 LCD 0 0 0
170 NCD 0 0 0
171 CVL 0 27 27
172 LCD Tx 0 0 0
173 NCD Tx 0 0 0
174 CVL Tx 0 6 6
175 LOF 0 0 0
176 LOS 0 0 0
177 LOSS - - -
178 LOL 0 0 0
179 LPR 0 0 0
180 ES 0 0 0
181 SESL 0 0 0
182 UASL 0 0 0
183 ECL 57 95196074 92176086
184 ECSL 0 0 0
185 ECL Tx 0 3638 2958
186 Inits 0 1 1
187 FastR 0 0 0
188 Failed FastR - - -
189 DSL Initialization Errors 0 0 0
190 DSL Initialization Timeouts 0 0 0
191 DSL Line Search Initializations 0 1 1
192 DSL Loss of Margin Failures 0 0 0
193 ISP Connection Establishment 0 1 1
Near same results when connect straight to network box outside.
Thanks,
Bob |
|
| 
 |
|
d_lBarsoomPremium,MVM
join:2002-12-08
Reno, NV
kudos:7 | reply to wishfull1
Well, your line's download CRC errors are minimal (line 171 CVL 0 27 27), so you don't have a slow down due to high CRC error rates. If you ever see high CVL counts and much higher counts a few minutes later, then you could suspect a high CRC error rate slowdown. CRC error rates of over 100/minute will begin to cause throughput slowing.
Right now congested transmission between you and speed test sites is a likely suspect. Similar to what you had to the OOL test site.
--
TCE Weather |
|
| Thanks for the reply. I guess I'll have to keep an eye on it. Although the thing I don't understand is how at my workplace I have 5x5 Business DSL and I can hit any of the speed test sites, day or night and get the same consistant number (always about 4.55). At home I get a different number everytime I run a test. Same server, different servers, they all range wildly.
Could it be something at the CO? Which is 1.6 miles by car away from my house BTW.
Thanks,
Bob |
|
d_lBarsoomPremium,MVM
join:2002-12-08
Reno, NV
kudos:7 | reply to wishfull1
The evening slowdowns that some people have when their gateways are congested (exhausted router slowdowns) show a different pattern on Wireshark graphs. If you had that distinctive pattern, we would know right away what your problem was.
You can run the Wireshark throughput test on non-flash speed tests. The procedure is similar to that described in the FAQ. All you have to do is identify a correct line to highlight before generating a throughput graph. It may take a little trial and error on your part to get the correct line highlighted.
Then if your graph looks like the original one you posted, you will know that the same type of transmission slowdowns as occurred between you and the OOL test site are occurring between you and your chosen speed test. Unfortunately if that is the case, I don't think there is anything you can do about it as this would be a network problem, but at least you would know what is wrong.
--
TCE Weather |
|
