netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Octavian Purdila <opurdila@ixiacom.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: netdev@vger.kernel.org
Subject: Re: ports beeing reused too fast
Date: Sat, 9 May 2009 16:11:19 +0300	[thread overview]
Message-ID: <200905091611.20321.opurdila@ixiacom.com> (raw)
In-Reply-To: <4A052991.5040009@cosmosbay.com>

On Saturday 09 May 2009 09:58:25 Eric Dumazet wrote:

> > I've looked over the  code and it looks right, so maybe net_random() is
> > not random enough? Or maybe there are side effects because of the %
> > port_range?
>
> Random is random :)
> Probability a port can be reused pretty fast is not nul.
>

Thinking again about it... you are right :)

> So yes, behavior you discovered is expected, when we switched port
> selection from a sequential one (not very secure btw) to a random one.
>
> Any strong reason why a firewall would drop a SYN because ports were used
> in a previous session ?

We don't know why the firewall (Cisco FWSM) is dropping the packets, may be a 
bug, limitation or miss-configuration. We are trying to track this down with 
the firewall vendor.

> Previous mode can be restored by application itself, using a bind() before
> connect(), if this application knows it has a very high rate of connections
> from a particular host to a particular host. (source ports range being
> small anyway, so your firewall could complain again)

Do you mean bind() with port != 0 ? Because I am already using bind() before 
connect().

Thanks,
tavi


  reply	other threads:[~2009-05-09 13:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-08 20:11 ports beeing reused too fast Octavian Purdila
2009-05-09  6:58 ` Eric Dumazet
2009-05-09 13:11   ` Octavian Purdila [this message]
2009-05-09 15:17     ` Eric Dumazet
2009-05-09 16:16       ` Eric Dumazet
2009-05-09 19:31       ` Bill Fink
2009-05-09 19:41         ` Octavian Purdila
2009-05-09 22:45         ` Stephen Hemminger
2009-05-12 12:32           ` Octavian Purdila
2009-05-12 15:11             ` Stephen Hemminger
2009-05-12 15:52               ` Octavian Purdila
2009-05-14 20:29                 ` Stephen Hemminger

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=200905091611.20321.opurdila@ixiacom.com \
    --to=opurdila@ixiacom.com \
    --cc=dada1@cosmosbay.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 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).