netdev
[Top] [All Lists]

Re: Deadlock problem with TCP v6?

To: Michael Richardson <mcr@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Deadlock problem with TCP v6?
From: Pekka Savola <pekkas@xxxxxxxxxx>
Date: Wed, 13 Mar 2002 09:45:15 +0200 (EET)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <200203130001.g2D01ip00466@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Tue, 12 Mar 2002, Michael Richardson wrote:
> >>>>> "Pekka" == Pekka Savola <pekkas@xxxxxxxxxx> writes:
>     Pekka> There appears to be some weird problem with TCP over IPv6 with 
> 2.4.18.  
>     Pekka> At least with RHL72 kernel (2.4.9-xx), this does not happen.
> 
>     Pekka> The topology is such:
> 
>     Pekka> 2001:708:10:10:250:4ff:fe6a:db55 - Linux client
>     Pekka> 2001:708:10:f::c1a6:45 - FreeBSD 4.5 TCP relay (using IPv6-to-IPv4 
> relay)
> 
>     Pekka> The test is done with basically 'lynx 
> [http://[2001:708:10:f::c1a6:45]', 
>     Pekka> the same also happens if telnetting to port 80 and issuing 'GET / 
>     Pekka> HTTP/1.0'
> 
>     Pekka> The problem is that FreeBSD never seems to be able to send the 
> data it
>     Pekka> receives from IPv4 to the Linux client: netstat -an shows the data 
> is kept
>     Pekka> in SendQ of the connection, which is CLOSING state.  Linux client 
> never
>     Pekka> sees the data.
> 
>   You mean you are hitting the FreeBSD box directly, so what has 6to4 got to
> do with it?

Well, to be exact, "IPv6-to-IPv4" not "6to4" (RFC3056). 

Yes, I'm connecting to the FreeBSD box directly.  I said the above just 
for completeness, as it _might_ also be a bug in faithd/faith.

I guess until some ideas surface, I'll forward this to KAME lists, and see 
if they have any ideas.

-- 
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


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