netdev
[Top] [All Lists]

Re: Deadlock problem with TCP v6?

To: Nivedita Singhvi <nivedita@xxxxxxxxxx>
Subject: Re: Deadlock problem with TCP v6?
From: Pekka Savola <pekkas@xxxxxxxxxx>
Date: Fri, 15 Mar 2002 12:49:57 +0200 (EET)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <OF3B5C69EB.7DE4713B-ON88256B7C.0057D500@xxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Thu, 14 Mar 2002, Nivedita Singhvi wrote:
> You dont say where you were running the trace.

Sorry, forgot.  One can see from the direction of tcpdumps that it was run 
on the Linux client though.

>       Freebsd almost immediately sends an ack back
>       for the 536 bytes, which means it got the
>       retransmitted data packet.
> 
>       I'm not sure why you see nothing more in the
>       trace here - you should see the http send from
>       the freebsd box.

Ok.. when trying to figure this out, I just installed a regular webserver 
on the FreeBSD TCP relay's port 8000, with really unexpected results:

1) linux-testbox$ lynx www.ipv6.csc.fi          [goes through the relay]
                  [no luck, ^C]
2) linux-testbox$ lynx http://[2001:708:0:1::624]:8000    [on the relay] 
                  [works without problems]
3) linux-testbox$ lynx www.ipv6.csc.fi  [now this works too!!!!!]

Tcpdump of linux (pstest.log) and relay (sixpack.log) are attached.

This seem to be a few fragments flying around, so I wonder if that has 
anything to do with this.

Any thoughts?

-- 
Pekka Savola                 "Tell me of difficulties surmounted,
Netcore Oy                   not those you stumble over and fall"
Systems. Networks. Security.  -- Robert Jordan: A Crown of Swords

Attachment: pstest.log
Description: Text document

Attachment: sixpack.log
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>