Sarcasm is just one more service we offer. Want to clean this up, but wanted to get 'ideal' and 'real world' I'm seeing anywhere from 4%-7% retransmission down from 37%. I'm looking on the inside of aįirewall between a device that acts as a gateway for mobile devices

> What is it that you are troubleshooting? If you are using the latest version click the expert button on the bar in the lower left corner, probably yellow if you applied the filter and you can gather some. They are also on the status line at the bottom. But of course, in the real world, you will see some retransmissions due to smaller WAN pipes, queue starvation, etc. Alternatively if you just do the and go to Statics - Summary you can see the number of counted packets.

By using Wireshark, you can identify specific retransmission issues. > Ideally, there should be no retransmissions in a private network. Wireshark will help you capture network packets and display them at a granular. Some applications break with less than 0.5% retransmission rate, and others do fine with up to 3% packet loss (meaning packets will be retransmitted.) It also depends on whether your users are complaining or not.

I would suggest to use the Wireshark filter 1 & 0 to get only resets without ACK. However Windows and some OS us this flag together with ACK to mean a graceful disconnection and not a problem. > There really is no 'typical acceptable' number. When a connection is not ended correctly the TCP Reset flag is set to 1. >typical acceptable standard (% of packets transmitted)? high desert newspaper obituaries gobank document upload. >I've got a question with regard to TCP retransmission.

Wireshark retransmission