From: Erik Hensema <erik@hensema.net>
To: bert hubert <ahu@ds9a.nl>
Cc: netdev@oss.sgi.com
Subject: Re: TCP/IPv6 broken in Linux 2.5.64?
Date: Thu, 20 Mar 2003 19:10:05 +0100 [thread overview]
Message-ID: <20030320181004.GA19970@hensema.net> (raw)
In-Reply-To: <20030320163107.GA28229@outpost.ds9a.nl>
On Thu, Mar 20, 2003 at 05:31:07PM +0100, bert hubert wrote:
> On Thu, Mar 20, 2003 at 06:49:49PM +0300, kuznet@ms2.inr.ac.ru wrote:
> > Hello!
> >
> > > irc servers, or an IPv6 zonetransfer. However, when I try to ssh from 2.5.65
> >
> > Try this. I have just found this lost patch, it is from 2.4 tree, but
> > it should fit to 2.5 as well.
>
> This has solved my problem 100%. The earlier mentioned hostA and hostB can
> now cheerfully connect to eachother. Everything else I try works too.
>
> So I suggest this be sent linus-wards. Thanks!
I can confirm that this fixed my IPv6 problems on 2.5.x.
--
Erik Hensema (erik@hensema.net)
prev parent reply other threads:[~2003-03-20 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 13:11 TCP/IPv6 broken in Linux 2.5.64? Erik Hensema
2003-03-18 13:54 ` Maciej Soltysiak
2003-03-18 16:25 ` bert hubert
2003-03-18 16:51 ` bert hubert
2003-03-20 15:49 ` kuznet
2003-03-20 16:31 ` bert hubert
2003-03-20 18:10 ` Erik Hensema [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030320181004.GA19970@hensema.net \
--to=erik@hensema.net \
--cc=ahu@ds9a.nl \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).