mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Longair <list-reader@ideaworks3d.com>
To: linux-kernel@vger.kernel.org
Cc: "Richard B. Johnson" <root@chaos.analogic.com>
Subject: Re: [2.2.18] outgoing connections getting stuck in SYN_SENT
Date: 24 Jan 2001 14:01:14 +0000	[thread overview]
Message-ID: <871ytt1239.fsf@starfruit.iwks.multi.local> (raw)
In-Reply-To: <14942.18985.174437.785751@starfruit.iwks.multi.local>
In-Reply-To: Mark Longair's message of "Fri, 12 Jan 2001 00:04:57 +0000 (GMT)"

Mark Longair <list-reader@ideaworks3d.com> writes:
[..]
> I'm having a problem where twice a day or so, any new tcp connection
> it gets stuck in SYN_SENT.  Eventually this situation rights itself,
> but obviously in the meantime many services (e.g. squid, X) are
> broken.  The machine does IP masquerdading with ipchains, and
> masqueraded connections through it seem to be unaffected.  The
> kernel version is 2.2.18, although the same happened with 2.2.17.
[..]

It turned out that this was caused by using autofw to forward a range
of ports (2300-2400 in this case.)  It seems that these ports aren't
reserved in any way, so eventually the server tries to use one as a
local port on an outgoing connection.

There was a previous reference to this on the list: 

  http://kernelnotes.org/lnxlists/linux-kernel/lk_9908_01/msg00573.html

I'm looking at finding fix for that.  Would this be an issue with the
new networking code in 2.4?

Thanks for the suggestions...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-24 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12  0:04 Mark Longair
2001-01-12  0:19 ` Richard B. Johnson
2001-01-12  0:49 ` Mark Longair
2001-01-12 13:24   ` Richard B. Johnson
2001-01-24 14:01 ` Mark Longair [this message]
2001-01-24 15:07   ` Martin Josefsson
2001-01-24 21:39   ` Eric Lammerts

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=871ytt1239.fsf@starfruit.iwks.multi.local \
    --to=list-reader@ideaworks3d.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®