mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "James Nichols" <jamesnichols3@gmail.com>
To: "Eric Dumazet" <dada1@cosmosbay.com>
Cc: "Jan Engelhardt" <jengelh@computergmbh.de>,
	linux-kernel@vger.kernel.org,
	"Linux Netdev List" <netdev@vger.kernel.org>
Subject: Re: After many hours all outbound connections get stuck in SYN_SENT
Date: Thu, 20 Dec 2007 11:08:45 -0500	[thread overview]
Message-ID: <83a51e120712200808m7fa63e9jc588124a6da5f740@mail.gmail.com> (raw)
In-Reply-To: <47695CEF.4090908@cosmosbay.com>

> I still dont understand.
>
> "tcpdump -p -n -s 1600 -c 10000" doesnt reveal User data at all.
>
> Without any exact data from you, I am afraid nobody can help.

Oh, I didn't see that you specified specific options.  I'll still have
to anonymize 2000+ IP addresses, but I think there is an open source
tool that will do this for you.



> >> 2) Are you sure you are not using connection tracking, and hit a limit on it ?
> >
> > I'm using ip_conntrack, but the limit I have for max entries is 65K.
> > The most I've seen in there are a couple thousand- that was one of the
> > first things I monitored very closely.
>
> Now please try without conn tracking module. I saw many failures in the past
> that were trigered by conntrack.
>
> Do you have some firewall rules, using some netfilter modules like hashlimit ?

I will have to look into this.

  parent reply	other threads:[~2007-12-20 16:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-14 20:39 James Nichols
2007-12-17 23:14 ` Jan Engelhardt
2007-12-18 15:34   ` James Nichols
2007-12-18 16:05     ` Jan Engelhardt
2007-12-18 16:45       ` James Nichols
2007-12-18 17:19         ` Jan Engelhardt
2007-12-18 18:09           ` James Nichols
2007-12-18 18:14             ` Jan Engelhardt
2007-12-18 18:21               ` James Nichols
2007-12-18 18:30                 ` Jan Engelhardt
2007-12-18 18:32                 ` Eric Dumazet
2007-12-18 19:44                   ` James Nichols
2007-12-18 20:37                     ` Eric Dumazet
2007-12-18 21:20                       ` Jan Engelhardt
2007-12-19 16:53                       ` James Nichols
2007-12-19 17:07                         ` Eric Dumazet
2007-12-19 17:43                           ` James Nichols
2007-12-19 17:58                             ` Jan Engelhardt
2007-12-19 18:12                               ` James Nichols
2007-12-20 14:41                               ` Glen Turner
2007-12-20 16:37                                 ` James Nichols
2007-12-20 21:05                                   ` Ilpo Järvinen
2007-12-21  6:06                                     ` Jan Engelhardt
2007-12-21  4:51                                   ` Glen Turner
2007-12-21 13:57                                     ` James Nichols
2007-12-19 18:03                             ` Eric Dumazet
2007-12-19 21:27                               ` Ilpo Järvinen
2007-12-20 16:08                               ` James Nichols [this message]
2007-12-20 20:44                                 ` Ilpo Järvinen
2007-12-20 20:49                                 ` Justin Banks
2007-12-18 19:45                   ` James Nichols
2007-12-18 20:28                     ` Chuck Ebbert

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=83a51e120712200808m7fa63e9jc588124a6da5f740@mail.gmail.com \
    --to=jamesnichols3@gmail.com \
    --cc=dada1@cosmosbay.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome