Re: TCP connection fail




"Dan" <dan@xxxxxxxx> wrote in message
news:OcuVIl$MIHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
I have a TCP connection that fails after a few minuets of working. It
should continuously deliver video stream. When I watch with a sniffer I see
the following-
1. The Ack packets in the receiver point to a previous received packets
seq counter, instead of to the next packet.
2. The total amount of Ack packets is smaller than the received packets.

Can some help please?

Are you able to run the sniffer at both ends?

TCP is not required to ACK every packet, it can perform ACK combining or
coalescing.

Due to transmit window and RTT, it is expected that the transmitted sequence
number will always be ahead of the ACKed number.


Regards

Dan




.



Relevant Pages

  • Re: TCP connection fail
    ... a lot of connection problems with buggy McAfee for example. ... The Ack packets in the receiver point to a previous received packets ...
    (microsoft.public.win32.programmer.networks)
  • Re: [QUESTION] Kernelspace <-> Userspace communication during tcp stack code execution
    ... As you might imagine I have to alter the syn,synack and ack packets ... config files on the client/user host (for example a config file which ... I also need file access from within a netfilter kernel module and have ...
    (Linux-Kernel)
  • Re: FreeBSD Traffic Shaping?
    ... >> line and on the acknowledgement packets, ... > reserve bandwidth for them unless you tell it to. ... ack packets go to the other one. ... > much higher weight. ...
    (freebsd-questions)
  • Re: TCP connection fail
    ... When I watch with a sniffer I ... The Ack packets in the receiver point to a previous received packets ... The total amount of Ack packets is smaller than the received packets. ...
    (microsoft.public.win32.programmer.networks)
  • Re: ipfw and ipsec processing order for outgoing packets wrong
    ... > in it's own queue. ... > while the counters change but the ACK packets are not sent on it's own ... even inside my ipsec tunnels, ...
    (freebsd-current)

Loading