Traffic Capture: Difference between revisions

← Older edit

Traffic Capture (view source)

Revision as of 00:06, 15 March 2017

177 bytes added , 15 March 2017

m

clean up, typos fixed: ie, → i.e.,, etc → etc. , eg → e.g. (2)

Reedy

editor

699

edits

Revision as of 20:20, 9 December 2015 (view source) AA-Andrew (talk \| contribs) m (→‎Information) ← Older edit		Latest revision as of 00:06, 15 March 2017 (view source) Reedy (talk \| contribs) m (clean up, typos fixed: ie, → i.e.,, etc → etc. , eg → e.g. (2))
(2 intermediate revisions by one other user not shown)
<indicator name="Diagnostics">[[File:menu-spanner.svg\|link=:Category:~~Diagnostic_Tools~~Diagnostic Tools\|30px\|Back up to the Diagnostics Category]]</indicator> ==Availability== [[File:clueless-line-diag-on-a-bt-line.png\|border]] This will perform a traffic capture of your line (or lines if you have more than one). You can then view the capture on the page or download a pcap file which can be viewed with other software - e.g. [https://www.wireshark.org/ Wireshark], this makes viewing and analyzing the traffic easier. Only the headers are captured, not the content. The Fields are: Length/size of the packet Session ID Protocol, ege.g. IP, IPv6 etc. Length/Size of the payload Source IP Address and port Destination IP Address and port *Packet type, ege.g. ICMP echo reply Free free to ask support staff ~~fot~~for help in understanding a traffic dump if you're having problems. - we don't save the dumps, so if you want to discuss your capture with staff, please copy/paste the dump and email it in. == Clues to look for == Using the traffic dump tool can be good to diagnose a slow connection. iei.e., if you have loads of traffic on your line, the line will become slow. Using the Traffic Dump tool you'll be able to see what the traffic is, and that may then help pin point the source of the traffic. ==Example==