About 33,500 results
Open links in new tab
  1. Why need Ack flag if we already have ack number in TCP

    Mar 19, 2022 · The ACK flag indicates that the Acknowledgment Number field is significant, ie. containing a meaningful value. When a socket connection has already been established that is …

  2. Why do I see a RST, ACK packet instead of a RST packet?

    Why do you think there should be a RST segment before RST/ACK? Maybe you could provide an example of such a packet trace?

  3. Wireshark filter for specific SYN packet which never received a SYN/ACK

    Nov 17, 2023 · Is there a way in wireshark to find out a single SYN that does not get answered by SYN/ACK?

  4. NACK vs. ACK? When to use one over the other one?

    Jan 12, 2016 · 24 Personally I don't even feel that there is a need for ACK. It's faster if we just send NACK (n) for the lost packets instead of sending an ACK for each received packet. So when/which …

  5. Why is TCP acknowledging all the time?

    Jan 7, 2018 · I understand seq/ack is used to provide a reliable connection service. But it seems that during TCP data transmission the ACK bit is ALWAYS set, as demonstrated in the following picture. …

  6. Window Size and ACK Number - Network Engineering Stack Exchange

    Copy-pasting from my lecturer's slides: • Receiver indicates the window size is 3000 • Transfer goes ahead • Acknowledge every 3000 bytes • Receiver increases window size to 4000 • 4000 bytes ...

  7. tcp - what's the acknowledgement number after retransmitting the ...

    Aug 17, 2020 · The very first ACK is correct. The acknowledgement number is the next expected segment number, and it acknowledges everything prior to that segment number, so the diagram is …

  8. TCP Duplicate Acknowledgement - Network Engineering Stack Exchange

    Dec 10, 2023 · Then the receiver will sending an duplicate ACK to sender, so whenever sender receive 3 duplicate ACK then the sender will retransmit the loss segment. But in this case where segment …

  9. TCP ACK confusion - Network Engineering Stack Exchange

    Apr 8, 2021 · The receiver can also selectively ACK (SACK) 51-100 to avoid a retransmission of successfully received segments. Without selective ACK, the sender retransmits 50-100. Note that …

  10. TCP and Go-Back-N - Network Engineering Stack Exchange

    1.TCP :cumulative ack for the last correctively received, in-order seg 2.cumulative and correctly received but out-of-order segs are not individually acked ⇒ TCP sender need only maintain SendBase and …