From: "H. Willstrand" <h.willstrand@gmail.com>
To: "M. Istehbab" <hariskhan@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: TCP connection failure in kernel 2.6.25
Date: Sun, 27 Apr 2008 18:56:02 +0200 [thread overview]
Message-ID: <1209315362.2934.55.camel@localhost.localdomain> (raw)
In-Reply-To: <c1410bfe0804262302p3f283f9k97a04ff11dd2779e@mail.gmail.com>
On Sun, 2008-04-27 at 11:02 +0500, M. Istehbab wrote:
> On Sun, Apr 27, 2008 at 1:27 AM, H. Willstrand <h.willstrand@gmail.com> wrote:
> > On Sat, 2008-04-26 at 17:16 +0500, M. Istehbab wrote:
> > > Yes, after a while (it can be a few seconds, minutes, or 1+ hour) the
> > > proxy server starts accepting connections again. I don't need to
> > > reboot the box when this happens.
> > >
> > > This happens randomely to anyone behind it. Then, after a while, it
> > > starts working again by itself.
> > >
> > Well, there are too many possibilities for failures... the Linux
> > distribution (RHEL 3 workstation) was built for 2.4.21 (around year
> > 2003) and you try 2.6.x
> >
> > Maybe you should stick to one of the later 2.4.x kernels or even better
> > upgrade the Linux distribution.
> >
> > Cheers,
> > H. Willstrand
>
>
> I didn't have problems with rhel ws3 or with the kernel it came with.
> I removed it in favour of debian a long time back, when debian/etch r0
> was released.
>
> I have been running debian etch r2 (4.0 r2) ever since, which comes
> with kernel (2.6.18-5-686). As you might notice from the mentioned
> kernel versions, I tried upgrading to kernels from lenny/debian and
> sid/debian hoping to find a solution. I tried from 2.3.13 - 2.6.25
> from both debian packages and vanilla sources (as they are called),
> but the problem persists. It started and is continuing on debian.
>
So, you have the same issue with all tested kernels
RHEL 3 works, Debian fails
This smells configuration failure, you better compare your working
configuration with the others.
// H.Willstrand
> I have 2 ISPs hooked into this box. One is CIR, the other is ADSL. The
> ADSL runs over pppoe. I don't know if the 2.4.x kernels support pppoe.
> The 2.6.x kernels do. I need to run 2 ISPs on this box seemlessly.
>
> The last rhel version I used was using kernel 2.6.9. I'm going to grab
> that and see if that helps.
>
> I need pppoe, iptables, vpn, scsi with raid support, smp, and a around
> 8000 file descriptors to run stable on this box.
>
> M. Istehbab
next prev parent reply other threads:[~2008-04-27 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 9:17 TCP connection failure in kernel 2.6.25 M. Istehbab
2008-04-26 10:18 ` H. Willstrand
2008-04-26 12:16 ` M. Istehbab
2008-04-26 20:27 ` H. Willstrand
2008-04-27 6:02 ` M. Istehbab
2008-04-27 16:56 ` H. Willstrand [this message]
2008-05-08 19:32 ` M. Istehbab
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=1209315362.2934.55.camel@localhost.localdomain \
--to=h.willstrand@gmail.com \
--cc=hariskhan@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.