Hi...
On Wed, Feb 20, 2008 at 3:44 PM, Hayim <[EMAIL PROTECTED]> wrote:
> Don't understand.
>
> This trace is from an HTTP server, where a file is being sent from the
> server to a client.
Ah sorry, I thought you were showing the trace from your own raw socket program.
> After the "GET" comm
On Wed, 2008-02-20 at 15:34 +0700, Mulyadi Santosa wrote:
> Hi...
>
> The interesting thing about the tcpdump's trace is seems like the
> sending (or receiving) side keep ACK-ing same packet/sequence number.
> Maybe something isn't done correctly?
Don't understand.
This trace is from an HTTP se
Hi...
The interesting thing about the tcpdump's trace is seems like the
sending (or receiving) side keep ACK-ing same packet/sequence number.
Maybe something isn't done correctly?
regards,
Mulyadi.
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to [EMAIL PROTEC
On Wed, 2008-02-20 at 10:32 +0700, Mulyadi Santosa wrote:
> Hi Hayim...
>
>
> On Feb 20, 2008 2:28 AM, Hayim Shaul <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > Here's what I see in the tcpdump. In this scenario I had sent three packets,
>
> Can you retry using tcpdump -S so we see absolute sequen
(1448) ack 1 win
1608
From: Karl Tatgenhorst [mailto:[EMAIL PROTECTED]
Sent: Tue 19/2/2008 8:43 PM
To: Hayim Shaul
Cc: kernelnewbies@nl.linux.org
Subject: Re: duplicated packets
Hayim,
With your tcpdump output are you sure that it is two of the same
Hayim,
With your tcpdump output are you sure that it is two of the same
packet (same sequence number etc...) It could be that it (the stack)
is expecting a reply or getting a NAK and resending the packet. If
that is the case I believe that the seq numbers should be the same.
Karl
On 2/19/08,
