![]() HTTPS appears to be an new overhead problem with AT&T customers with recent Fiber Broadband network changes. HTTP packets travel this same route but the unsecured, unencrypted packets are not causing a slow down. Share Follow answered at 3:58 M N Islam Shihan 368 4 5 Add a comment 1 Yes. Of recent, this DPI, Monitoring activity has been impacting our HTTPS channel communications. Set following as a filter after you've started capturing the appropriate network interface: tcp.port 443 tcp.port 80 This will ensure display of data for only http & https connections that you can further inspect. Why could the reasons for this to happen with only HTTPS and not HTTP?ĪT&T is performing packet security analysis and DPI (Deep Packet Inspection) in their main network/data center. With escalated support, AT&T has asked that I get a WireShark capture to illustrate the problem. However, all other hosted domains on HTTPS are being disrupted and degraded. While there are still some delays, the packets do not timeout and reset. It appears AT&T has taken the two main domains I cited as examples showing the problem, and and 'white listed" them to improve the HTTPS performance. ![]() In the past month, AT&T has begun degrading, intentionally or unintentionally, the HTTPS channel causing packet disruptions, timeouts and resets with the browser. I need to do this for three sites on my network. Start Capturing and Log from SRC IP the HTTPS connection to host IP XYZ. What would the command be to capture filter or script or menu options or a reference to an online example? I need to basically say: I need to capture the traffic from my Win7 machine where I just installed WireShark v3 to HTTPS web sites hosted at small office network with AT&T Fiber Ethernet.
0 Comments
Leave a Reply. |