![]() Pipe Capacity is then a measurement of volume. A measurement of how many packets we can fit in this pipe is the Pipe Capacity or the Bandwidth Delay Product - PC = R * RTT, where R is the smallest bandwidth. The RTT estimate we just got from the handshake gives us an estimate of the length of this network path. This means that this capture file is taken at the receiver, and to see why that's not ideal, we'll have to go back to school.īetween the sender and the receiver there is one part of the network path that is the smallest, which limits the bandwidth. Note that the time between SYN/ACK and ACK (frames 38 and 39) is much lower than between SYN and SYN/ACK (37 and 38). It's about 9.3 ms, which matches your findings. Don't see anything weird regarding SACK.Īn estimate of the unloaded RTT is the time between the SYN packet and the first ACK (frame 39). Same thing in in the SYN/ACK (frame 38), SACK and Windows scaling. Hold on, we'll get there.Ĭhecking the SYN packet (frame 37) we see SACK and Window Scaling in the TCP Options. Looks really bad, right? Well, it's not that bad. Scrolling down a bit after opening this file in Wireshark we see some frames in different color. I realize that this answer is simplified, and not as explicit as I'd like it to be, so if you have questions about a step, please ask! This leads me to believe that there is a problem with the metro ethernet circuit, even though they continue to say nothing is wrong and everything tests ok. The packet capture looks the same doing it this way. So I've also tried connecting to laptops directly into the service providers equipment at both sites, and putting them on the same subnet. Since it is a metro ethernet circuit, no router is required. The packet capture with it installed had the same results. ![]() Since this started, I've replaced the sonicwall with an 1800 cisco router. ![]() TX packets:149148 errors:0 dropped:0 overruns:0 carrier:0 RX packets:244994 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Here is a traceroute from my system to the server (ping times are usually steady under 10ms): ifconfig eth0Įth0 Link encap:Ethernet HWaddr 00:e0:b8:c8:0c:7e Here is a screenshot from wireshark, and here is the entire capture. The two sites are connected by one sonicwall router, so the sites are only one hop away. It can be initiated unidirectionally and applied to the Destination Zone only, or bidirectionally and applied to both Zones.I'm getting excessive TCP Dup ACK and TCP Fast Retransmission on our network when I transfer files over the MetroEthernet link. Apply the Zone protection profile to one zone or both, depending on if asymmetric traffic is required. Note: If traffic spans two Security Zones, the Zone Protection Profile keys the Destination zone.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |